[JBoss JIRA] (TEIID-1834) Add suppot for a comparable binary type
by Steven Hawkins (Created) (JIRA)
Add suppot for a comparable binary type
---------------------------------------
Key: TEIID-1834
URL: https://issues.jboss.org/browse/TEIID-1834
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals.
See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (TEIID-1838) Change to source model connection through AdminApi using assignToModel() does not reflect in jdbc queries to that source model
by Ramesh Reddy (Created) (JIRA)
Change to source model connection through AdminApi using assignToModel() does not reflect in jdbc queries to that source model
------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1838
URL: https://issues.jboss.org/browse/TEIID-1838
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 7.5
Environment: Windows server 2008 R2, JBoss 5.1
Reporter: Farrukh Ihtisham
Assignee: Ramesh Reddy
Fix For: 7.6
When source model's connection is changed using following adminapi code;
AdminFactory adminFactory = AdminFactory.getInstance();
Admin admin = adminFactory.createAdmin("admin", "admin".toCharArray(), "mms://localhost:31443");
admin.assignToModel("Sample", 1, "SQLSourceA", "SQLSourceA", "sqlserver", "SQLSourceA_2");
Any jdbc query result would still be from the old data source. However when verified using following adminapi code;
VDB vdb = admin.getVDB("sample", 1);
Model m = vdb.getModel("SQLSourceA");
String jndiName = m.getSourceConnectionJndiName("SQLSourceA");
The jndiName shows that the connection is successfully updated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (TEIID-1680) issues with correlation and aggregation
by Steven Hawkins (JIRA)
issues with correlation and aggregation
---------------------------------------
Key: TEIID-1680
URL: https://issues.jboss.org/browse/TEIID-1680
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
subqueries used in the having/select clause of a query with grouping only understand correlated element symbols - not correlated grouping expressions or correlated aggregate values.
If a nested aggregate contains only outer references, then it should be treated as a correlated value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (TEIID-1715) Simplify ODBC buffers
by Steven Hawkins (JIRA)
Simplify ODBC buffers
---------------------
Key: TEIID-1715
URL: https://issues.jboss.org/browse/TEIID-1715
Project: Teiid
Issue Type: Quality Risk
Components: ODBC
Affects Versions: 7.4.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.4.1, 7.5
The results message is being built separately then copied into results buffer. These should use a single buffer. Also we are mistakenly using direct buffers. Beyond the possible memory implications in heavy usage scenarios, direct buffers cannot grow which means that any result over the ODBCPacketSize (such as a lob) will cause an exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month