February 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-762) tuplesource leak in update procedures

by Steven Hawkins (JIRA)

tuplesource leak in update procedures ------------------------------------- Key: TEIID-762 URL: https://jira.jboss.org/jira/browse/TEIID-762 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 Tuplesources are being leaked by update procedures that have execsqlstatement followed by another command execution, such as a loop. -- 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

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-610) Deleted connector bindings remain in the system state

by Steven Hawkins (JIRA)

Deleted connector bindings remain in the system state ----------------------------------------------------- Key: TEIID-610 URL: https://jira.jboss.org/jira/browse/TEIID-610 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.1 If a connector binding is first stopped and then removed, it remains in the system state (but is otherwise removed from the system). -- 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

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-608) Prevent duplicate hostcontroller launches

by Steven Hawkins (JIRA)

Prevent duplicate hostcontroller launches ----------------------------------------- Key: TEIID-608 URL: https://jira.jboss.org/jira/browse/TEIID-608 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Even if the hostcontroller persistent process is removed, we still need to ensure that multiple attempts to launch processes works well. The worst issue right now is that the log of the original hostconroller will be replaced with the new (which then immediately exits). See also TEIID-601 -- 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

14 years, 9 months

2
5
0 / 0

[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

14 years, 9 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

14 years, 9 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

14 years, 9 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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Moved: (TEIID-1000) Dependent Join in Virtual Model not pushing criteria to both sources

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-1000?page=com.atlassian.jira.plu... ] Van Halbert moved JBEDSP-1193 to TEIID-1000: -------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-1000 (was: JBEDSP-1193) Component/s: Query Engine (was: Query) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Dependent Join in Virtual Model not pushing criteria to both sources > -------------------------------------------------------------------- > > Key: TEIID-1000 > URL: https://jira.jboss.org/jira/browse/TEIID-1000 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > > Sample models are attached. User query is: > SELECT * FROM v_TV_SHOWS.v_SHOWS_ACTORS2 > WHERE SHOW_NAME LIKE '%E%' AND > NOT ACTOR_SHOW_ID IN (SELECT ACTOR_SHOW_ID FROM v_TV_SHOWS.v_SHOWS_ACTORS2 WHERE ACTOR_NAME = 'MALCOLM JAMAL-WARNER') > OPTION DEBUG and MMProcess.log are attached. > Customer complaint is that the query contains criteria on ACTOR_NAME and ACTOR_SHOW_ID which is coming from Oracle and on SHOW_NAME which is coming from SQL Server. In the query plan, there is a SELECT node that does not have criteria to Oracle. Instead it is SELECT * which pulls all records. Customer tables are huge so this is an issue for 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-999?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1031 to TEIID-999: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-999 (was: JBEDSP-1031) Component/s: Misc. Connectors (was: Connectors) Fix Version/s: (was: Future Versions) Affects Version/s: (was: Westport) (was: 5.5.4) > Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors > --------------------------------------------------------------------------------- > > Key: TEIID-999 > URL: https://jira.jboss.org/jira/browse/TEIID-999 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Environment: MS Excel 2003 > Reporter: Larry O'Leary > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access. > The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-979) Add support for Oracle XML queries in our Oracle connector

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-979?page=com.atlassian.jira.plug... ] Van Halbert updated TEIID-979: ------------------------------ Description: Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. It would be good to use these special SQL statements to extract XML data from Oracle via our Oracle connector. case 5715 was: Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. Genentech would like to be able to use these special SQL statements to extract XML data from Oracle via our Oracle connector. case 5715 > Add support for Oracle XML queries in our Oracle connector > ---------------------------------------------------------- > > Key: TEIID-979 > URL: https://jira.jboss.org/jira/browse/TEIID-979 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Marc Shirley > > Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. It would be good to use these special SQL statements to extract XML data from Oracle via our Oracle connector. > case 5715 -- 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

14 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2010