January 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1374) Nested correlated reference issue with rewritten queries

by Steven Hawkins (JIRA)

Nested correlated reference issue with rewritten queries -------------------------------------------------------- Key: TEIID-1374 URL: https://jira.jboss.org/browse/TEIID-1374 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins In a query such as "select * from bqt1.smalla where exists (select intnum from bqt1.smalla x where smalla.intnum = x.intnum and exists (select intnum from bqt1.smalla where exists (select intnum from bqt1.smalla x where smalla.intnum = x.intnum)))" we will inappropriately report that the top exists subquery has 2 correlated references since we see the more deeply nested smalla.intnum also. This is generally not a issue, it can introduce errors in places where subqueries are rewritten, such as with subquery optimization or inherently updatable view queries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1366) Merge VDB action should provide way to persist the results

by Ramesh Reddy (JIRA)

Merge VDB action should provide way to persist the results ----------------------------------------------------------- Key: TEIID-1366 URL: https://jira.jboss.org/browse/TEIID-1366 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.2 Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently "merge vdb" admin action is memory resident and does not persist between server restarts. Need to explore way to make this action persistent. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
15
0 / 0

[JBoss JIRA] Created: (TEIID-1598) translator scoped result set caching

by Mark Addleman (JIRA)

translator scoped result set caching ------------------------------------ Key: TEIID-1598 URL: https://issues.jboss.org/browse/TEIID-1598 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor Something Steven mentioned in Teiid-1589 got me thinking: It would be helpful for individual translators to request that Teiid cache results sets that match the query as presented to the execution factory (after the planner is done rewriting the query based on the translator's capabilities). I envision a new method on an Execution getCacheTtlMs() where zero or negative indicates that Teiid shouldn't cache the results. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
15
0 / 0

[JBoss JIRA] Created: (TEIID-1280) Add parameters to procedure definition

by Steven Hawkins (JIRA)

Add parameters to procedure definition -------------------------------------- Key: TEIID-1280 URL: https://jira.jboss.org/browse/TEIID-1280 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.0 Our procedure syntax needs to add parameter definition to be independent of Designer. -- 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

3
4
0 / 0

[JBoss JIRA] (TEIID-1884) COMMAND Logging incorrectly reporting END USER COMMAND record count in EDS for forward only resultsets

by Johnathon Lee (Created) (JIRA)

COMMAND Logging incorrectly reporting END USER COMMAND record count in EDS for forward only resultsets ------------------------------------------------------------------------------------------------------ Key: TEIID-1884 URL: https://issues.jboss.org/browse/TEIID-1884 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6, 7.5, 7.4, 7.3, 7.2, 7.1 Reporter: Johnathon Lee Assignee: Steven Hawkins Running a query [1] that returns 406 rows in sql client, near the end of my log I get this output [2]. [1] select * from CIS_Test.GetListOfLanguageNames [2] 2011-12-28 12:34:34,169 DEBUG [org.teiid.COMMAND_LOG] (Worker0_QueryProcessorQueue26) END USER COMMAND: endTime=2011-12-28 12:34:34.169 requestID=EED0CMZyYmnc.7 txID=null sessionID=EED0CMZyYmnc principal=teiid@teiid-security vdbName=CIStest vdbVersion=1 finalRowCount=0 -- 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

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-1600) Exact numerical literal parsing

by Steven Hawkins (JIRA)

Exact numerical literal parsing ------------------------------- Key: TEIID-1600 URL: https://issues.jboss.org/browse/TEIID-1600 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 Teiid diverges from the SQL spec by parsing numerical expressions of the form <integral value>.<integral value> as doubles rather than as an exact numeric type (which for us would be BigDecimal). I believe this was originally done to match Java parsing semantics and potentially to avoid performance overhead of using BigBecimal. However this can lead to a loss of precision that is not expected by ANSI SQL. inexact numeric values entered in scientific notation would not be affected by this change. They would still be parsed as doubles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
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

12 years, 1 month

3
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

12 years, 1 month

2
12
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

12 years, 1 month

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

12 years, 1 month

4
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2012