[JBoss JIRA] (TEIID-2007) JDBC warnings are not properly handled
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2007:
-------------------------------------
Summary: JDBC warnings are not properly handled
Key: TEIID-2007
URL: https://issues.jboss.org/browse/TEIID-2007
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
Adding warnings individually results in redundant exceptions. See also TEIID-1829
This is a behavior change though since the resulting warnings on the client side will be held by the cause. Proper access would be:
//warning will be an instanceof TeiidSQLWarning to convey model/source information
SQLWarning warning = stmt.getWarnings();
while (warning != null) {
Exception e = warning.getCause();
if (cause instanceof SQLWarning) {
//childWarning should now be the head of the source warning chain
SQLWarning childWarning = (SQLWarning)cause;
while (childWarning != null) {
//do something with childWarning
childWarning = childWarning.getNextWarning();
}
}
warning = warning.getNextWarning();
}
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2041) Regression RuleCleanCriteria
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2041:
-------------------------------------
Summary: Regression RuleCleanCriteria
Key: TEIID-2041
URL: https://issues.jboss.org/browse/TEIID-2041
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.7.1, 8.1
RuleCleanCriteria may not be adding in RuleRaiseNull when needed, which can result in invalid nodes under an accessnode. This in turn may manifest itself as:
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.elementData(ArrayList.java:338)
at java.util.ArrayList.get(ArrayList.java:351)
at org.teiid.query.optimizer.relational.rules.RuleCollapseSource.buildQuery(RuleCollapseSource.java:338)
at org.teiid.query.optimizer.relational.rules.RuleCollapseSource.buildQuery(RuleCollapseSource.java:373)
at org.teiid.query.optimizer.relational.rules.RuleCollapseSource.createQuery(RuleCollapseSource.java:228)
As there may not be from clause items to collapse.
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2232) Update Hive translator for newer version of Hive Driver
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2232:
-----------------------------------
Summary: Update Hive translator for newer version of Hive Driver
Key: TEIID-2232
URL: https://issues.jboss.org/browse/TEIID-2232
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 8.1
Reporter: Ramesh Reddy
Originally Hive translator designed for 0.7 version of the Hive JDBC driver, the current version is "30 April, 2012: release 0.9.0 available".
Another important update we should do is take advantage of their direct map-reduce job submission through Hive as native command feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (TEIID-1131) Document/expand sequence support
by Steve Hawkins (JIRA)
Document/expand sequence support
--------------------------------
Key: TEIID-1131
URL: https://jira.jboss.org/browse/TEIID-1131
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector, Query Engine
Affects Versions: 7.0
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1
Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month