July 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2029) Allow defining multiple dependencies with "lib" property in the vdb.xml

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2029: ----------------------------------- Summary: Allow defining multiple dependencies with "lib" property in the vdb.xml Key: TEIID-2029 URL: https://issues.jboss.org/browse/TEIID-2029 Project: Teiid Issue Type: Enhancement Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 Currently "lib" property allows single module dependency, allow to define multiple modules with comma as the delimiter. Also allow the JAR or EAR/WAR based dependencies. -- 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
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] (TEIID-2104) Make it easier to detect failure during load

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2104: ------------------------------------- Summary: Make it easier to detect failure during load Key: TEIID-2104 URL: https://issues.jboss.org/browse/TEIID-2104 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 With the open shift work it was requested to make it easier to detect a failed load. Since we don't transition out of the loading status until we're either loaded or there was hard error, this cannot be done with status alone. -- 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

1
2
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-1971) Provide delegating Metadata Repository implementation class

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1971: ----------------------------------- Summary: Provide delegating Metadata Repository implementation class Key: TEIID-1971 URL: https://issues.jboss.org/browse/TEIID-1971 Project: Teiid Issue Type: Task Components: Connector API Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 The Metadata Repository is interface defined to import metadata from variety of sources. It is useful to provide a base implementation of of delegating metadata repository such that it can be overridden by users to provide their own implementations, on top of already already available methods. -- 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
2
0 / 0

[JBoss JIRA] (TEIID-2015) Create implementation to support calling remote Infinispan

by Van Halbert (JIRA)

Van Halbert created TEIID-2015: ---------------------------------- Summary: Create implementation to support calling remote Infinispan Key: TEIID-2015 URL: https://issues.jboss.org/browse/TEIID-2015 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Affects Versions: 7.7.1 Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.7.1 Implement the classes in order to support calling Infinispan remotely. This will include: - an ExecutionFactory to support Infinispan features and building the metadata when getMetadata(..) is called. This will be needed so that the metadata can be imported using Designer to build the source model(s). - implement the query logic needed to take a command and submit it Infinispan -- 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
3
0 / 0

[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

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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2012