September 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-700) Adding ORDER BY to a specific query (see details) gets ORA-00904: "C_0": invalid identifier

by Paul Nittel (JIRA)

Adding ORDER BY to a specific query (see details) gets ORA-00904: "C_0": invalid identifier ------------------------------------------------------------------------------------------- Key: TEIID-700 URL: https://jira.jboss.org/jira/browse/TEIID-700 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Environment: Fedora 10, OpenJDK 1.6.0, Teiid 6.1.0 Reporter: Paul Nittel Assignee: Steven Hawkins I created a query which worked fine until I added the ORDER BY clause: (SELECT INTKEY, 'A' AS WHEREFROM FROM BQT1.SMALLA LIMIT 6) UNION ALL (SELECT INTKEY, 'B' AS WHEREFROM FROM BQT2.SMALLB LIMIT 5) ORDER BY INTKEY, WHEREFROM LIMIT 10 Now, when executed, it generates this: Jul 01, 2009 10:37:09.727 [Worker5_QueryProcessorQueue47|0] ERROR <DQP|0> Unexpected exception for request 0.16 [MetaMatrixComponentException] 904: Error Code:904 Message:Error Code:904 Message:Error occurred on connector BQT1 Connector<8> - Error Code:904 Message:ORA-00904: "C_0": invalid identifier Executing statement: [SQL: SELECT * FROM (SELECT g_1.IntKey AS c_0, 'A' AS c_1 FROM SmallA g_1) WHERE ROWNUM <= 6 UNION ALL SELECT * FROM (SELECT g_0.IntKey AS c_0, 'B' AS c_1 FROM SmallB g_0) WHERE ROWNUM <= 5 ORDER BY c_0, c_1] 1 [ConnectorException]Error Code:904 Message:Error occurred on connector BQT1 Connector<8> - Error Code:904 Message:ORA-00904: "C_0": invalid identifier Executing statement: [SQL: SELECT * FROM (SELECT g_1.IntKey AS c_0, 'A' AS c_1 FROM SmallA g_1) WHERE ROWNUM <= 6 UNION ALL SELECT * FROM (SELECT g_0.IntKey AS c_0, 'B' AS c_1 FROM SmallB g_0) WHERE ROWNUM <= 5 ORDER BY c_0, c_1] 2 [JDBCExecutionException]Error Code:904 Message:ORA-00904: "C_0": invalid identifier Executing statement: [SQL: SELECT * FROM (SELECT g_1.IntKey AS c_0, 'A' AS c_1 FROM SmallA g_1) WHERE ROWNUM <= 6 UNION ALL SELECT * FROM (SELECT g_0.IntKey AS c_0, 'B' AS c_1 FROM SmallB g_0) WHERE ROWNUM <= 5 ORDER BY c_0, c_1] at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:128) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89) at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:136) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:81) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:110) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:160) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:264) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:210) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: org.teiid.connector.api.ConnectorException: Error Code:904 Message:Error occurred on connector BQT1 Connector<8> - Error Code:904 Message:ORA-00904: "C_0": invalid identifier Executing statement: [SQL: SELECT * FROM (SELECT g_1.IntKey AS c_0, 'A' AS c_1 FROM SmallA g_1) WHERE ROWNUM <= 6 UNION ALL SELECT * FROM (SELECT g_0.IntKey AS c_0, 'B' AS c_1 FROM SmallB g_0) WHERE ROWNUM <= 5 ORDER BY c_0, c_1] at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.handleError(ConnectorWorkItem.java:235) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:174) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69) ... 4 more Caused by: org.teiid.connector.jdbc.JDBCExecutionException: Error Code:904 Message:ORA-00904: "C_0": invalid identifier Executing statement: [SQL: SELECT * FROM (SELECT g_1.IntKey AS c_0, 'A' AS c_1 FROM SmallA g_1) WHERE ROWNUM <= 6 UNION ALL SELECT * FROM (SELECT g_0.IntKey AS c_0, 'B' AS c_1 FROM SmallB g_0) WHERE ROWNUM <= 5 ORDER BY c_0, c_1] at org.teiid.connector.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:103) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.processNewRequest(ConnectorWorkItem.java:277) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:157) ... 6 more Steve Hawkins suspects the OracleTranslator code. -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-710) DB2 does not support pushdown of null keyword as a select expression

by Steven Hawkins (JIRA)

DB2 does not support pushdown of null keyword as a select expression -------------------------------------------------------------------- Key: TEIID-710 URL: https://jira.jboss.org/jira/browse/TEIID-710 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 For example SELECT SmallA.IntKey, NULL FROM SmallA will fail. -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-360) SQLServer SQLTranslator issues

by Steven Hawkins (JIRA)

SQLServer SQLTranslator issues ------------------------------ Key: TEIID-360 URL: https://jira.jboss.org/jira/browse/TEIID-360 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The time literal for Access/SQLServer is incorrect - should use 1970 not 1900 Limit for a set op needs to use a subquery Support for repeat should be aliased to replicate -- 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

15 years, 7 months

1
7
0 / 0

[JBoss JIRA] Created: (TEIID-455) Config edits should use optimistic locking

by Steven Hawkins (JIRA)

Config edits should use optimistic locking ------------------------------------------ Key: TEIID-455 URL: https://jira.jboss.org/jira/browse/TEIID-455 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Config edits are atomic, but do not enforce consistency - the last one always wins. Optimistic locking should be used to properly ensure consistency. Also versions should be restorable. Currently it's not expected that multiple admins will be making changes concurrently, so this is not a critical issue. -- 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

15 years, 7 months

1
3
0 / 0

[JBoss JIRA] Commented: (TEIID-199) Integration with JBoss Identity project

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-199?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-199: ------------------------------------ Remove the Membership domain for 1) File 2) LDAP Since Teiid depends only upon JAAS, the implementations of JAAS like JBoss Identity will provide above facilities for authorizations. > Integration with JBoss Identity project > --------------------------------------- > > Key: TEIID-199 > URL: https://jira.jboss.org/jira/browse/TEIID-199 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: Steven Hawkins > Fix For: 6.3 > > > There is a project underway, JBoss Identity (https://jira.jboss.org/jira/browse/JBID), that aims to provide common identity management support across many JBoss projects/products. According to the project leader's blog (http://anil-identity.blogspot.com/2008/12/federated-identity-support-with...), JBoss Application Server, JBoss Portal, JBoss SOA, JBoss Rules/Drools, and JBoss Seam are all on board with this approach. We should see if it makes sense for us to jump on the bandwagon. > The end goal of using the JBoss Identity stuff would be to replace the custom membership domain provider for authentication, and also to leverage it to provide SAML-based authorization for (ideally fine grained) access to Federate virtual databases. > SAML-based authorization has been a frequent request by prospects/customers for the closed source MetaMatrix product that is an ancestor to Federate. > I'm deliberately logging this one in the Federate project rather than the JBEDSP product JIRA since JBoss Identity itself is also still in project-only status. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-155) Revisit TransformationMetadataFacade cache sizes

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-155?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-155. ---------------------------------- Resolution: Out of Date Given that we'll move away from our index structures soon, the current cache sizes seem valid (they were also updated in 6.2). > Revisit TransformationMetadataFacade cache sizes > ------------------------------------------------ > > Key: TEIID-155 > URL: https://jira.jboss.org/jira/browse/TEIID-155 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.3 > > > Defect Tracker #24593: Cases 5004 and 5835 have shown significant performance issues with resolving. While much of the performance impact was addressed with the 5.5 resolving refactor there is still a large performance hit for resolving that seems largely dependent upon metadata cache. We should investigate additional strategies (for example unified cache or writing more entries per index file read) as a way to increase performance. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-856) CTC Query Results have special characters in some cases depending on the OS causing unexpected results

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-856?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1082 to TEIID-856: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-856 (was: JBEDSP-1082) Component/s: Integration Tests (was: Testing) Affects Version/s: 6.3 (was: 5.5.4) > CTC Query Results have special characters in some cases depending on the OS causing unexpected results > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-856 > URL: https://jira.jboss.org/jira/browse/TEIID-856 > Project: Teiid > Issue Type: Bug > Components: Integration Tests > Affects Versions: 6.3 > Reporter: Warren Gibson > Assignee: Paul Nittel > > In some cases query error results are being returned to CTC with special characters depending on the OS. This results in unexpected results since CTC use the same set of expected results for all OS versions. Please strip off special characters from query results in CTC to accommodate differences between OS behavior. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-855) CTC is producting unexpected results due to case sensitive issues between different sources

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-855?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1094 to TEIID-855: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-855 (was: JBEDSP-1094) Component/s: Integration Tests (was: Testing) Affects Version/s: 6.3 (was: 5.5.4) > CTC is producting unexpected results due to case sensitive issues between different sources > ------------------------------------------------------------------------------------------- > > Key: TEIID-855 > URL: https://jira.jboss.org/jira/browse/TEIID-855 > Project: Teiid > Issue Type: Bug > Components: Integration Tests > Affects Versions: 6.3 > Reporter: Warren Gibson > Assignee: Van Halbert > > We found it necessary to do fresh imports from all the query sources. In doing so we found that some of the sources contain table and column names in all caps. This is causing non compare results when exceptions are thrown and the exception error messages are compared. Upper and Lower case should not create a non compare. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-854) Remove the legacy "server" project from the SCM

by Ramesh Reddy (JIRA)

Remove the legacy "server" project from the SCM ----------------------------------------------- Key: TEIID-854 URL: https://jira.jboss.org/jira/browse/TEIID-854 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 The "server" is now defunct with the features introduced in the 6.2 release and road map for 6.3 and beyond. This project does not have any resources that could be used in the core Teiid project, so this should be removed. -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-827) 6.1 api docs are missing

by Steven Hawkins (JIRA)

6.1 api docs are missing ------------------------ Key: TEIID-827 URL: https://jira.jboss.org/jira/browse/TEIID-827 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins The current doc link points to 6.0 docs. -- 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

16 years, 1 month

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2009