May 2012 - teiid-issues - Jboss List Archives

[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

11 years, 6 months

1
3
0 / 0

[JBoss JIRA] (TEIID-1806) Make unordered limit handling consistent

by Steven Hawkins (Created) (JIRA)

Make unordered limit handling consistent ---------------------------------------- Key: TEIID-1806 URL: https://issues.jboss.org/browse/TEIID-1806 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 With the resolution of TEIID-1422, unordered limit handling was both internally inconsistent and typically did not reflect the logical application of the limit. We should be consistent by default and always enforce the presumed intent of the unordered limit. A hint should be handled to allow for non-strict application similar to our current handling. -- 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

11 years, 6 months

3
2
0 / 0

[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

11 years, 6 months

1
3
0 / 0

[JBoss JIRA] (TEIID-2042) Large query plans may cause OOM error

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2042: ------------------------------------- Summary: Large query plans may cause OOM error Key: TEIID-2042 URL: https://issues.jboss.org/browse/TEIID-2042 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7.1, 8.1 Since the query plan is held in memory, a large plan can exhaust the heap for reasonable VM sizes. -- 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

11 years, 6 months

1
2
0 / 0

[JBoss JIRA] (TEIID-1920) Dynamic sql using a non-literal requires a keyword

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1920: ------------------------------------- Summary: Dynamic sql using a non-literal requires a keyword Key: TEIID-1920 URL: https://issues.jboss.org/browse/TEIID-1920 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7 When entering dynamic sql in designer, the resulting string form omits the string keyword. However the resulting form will not parse is a non-literal dynamic sql string is used. We should use a string from that has IMMEDIATE. Also the docs should be updated to show EXECUTE IMMEDIATE examples and to change UVAR to DVAR. -- 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

11 years, 6 months

2
12
0 / 0

[JBoss JIRA] (TEIID-1985) Additional avenues for plan information

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1985: ------------------------------------- Summary: Additional avenues for plan information Key: TEIID-1985 URL: https://issues.jboss.org/browse/TEIID-1985 Project: Teiid Issue Type: Enhancement Components: Common Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7.1 Processor plans should be available for in-flight queries via the admin api. Also processing plans should be logged in the command log probably at a finer level of detail. -- 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

11 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-657) Support Batched Updates in the Salesforce Connector

by John Doyle (JIRA)

Support Batched Updates in the Salesforce Connector --------------------------------------------------- Key: TEIID-657 URL: https://jira.jboss.org/jira/browse/TEIID-657 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Affects Versions: 6.0.0, 6.1.0 Reporter: John Doyle Assignee: John Doyle Salesforce supports batched updates via the WS API. Since Teiid supports batched updates as well, the SF connector should support them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
9
0 / 0

[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

11 years, 6 months

4
12
0 / 0

[JBoss JIRA] Created: (TEIID-1543) Add a query hint to limit the number of concurrent source queries

by Steven Hawkins (JIRA)

Add a query hint to limit the number of concurrent source queries ----------------------------------------------------------------- Key: TEIID-1543 URL: https://issues.jboss.org/browse/TEIID-1543 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins We would like a new query hint to limit the number of parallel executions of union members. This is useful in two situations: 1. When the queries are expensive, but the overall union contains a limit that is most likely to be fulfilled by the first member of the union 2. When the queries are backed by a common resource which may be overloaded by multiple queries The addition of a hint would make this manageable by the client; perhaps something like "/*+ parallel=2*/"? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic

by Steve Hawkins (JIRA)

Reuse dynamic sql plans and allow for prepared statements in procedure logic ---------------------------------------------------------------------------- Key: TEIID-1226 URL: https://jira.jboss.org/browse/TEIID-1226 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Minor Fix For: 8.0 Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse. Also procedure logic should have a mechanism to execute prepared statements for further plan reuse. -- 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

11 years, 7 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2012