June 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1622) Optional JOIN hints don't get optimized out for UNION ALL view

by Mark Drilling (JIRA)

Optional JOIN hints don't get optimized out for UNION ALL view -------------------------------------------------------------- Key: TEIID-1622 URL: https://issues.jboss.org/browse/TEIID-1622 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Reporter: Mark Drilling Assignee: Steven Hawkins Fix For: 7.1.1 When we create a view with Optional JOIN hint on it, and execute a query against this view, the hint is properly honored. But if we create a view with UNION ALL on two such views and query the UNION ALL view the optional hint is not honored -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1656) Add pushdown support for Searched CASE expression over a UNION

by Mark Drilling (JIRA)

Add pushdown support for Searched CASE expression over a UNION -------------------------------------------------------------- Key: TEIID-1656 URL: https://issues.jboss.org/browse/TEIID-1656 Project: Teiid Issue Type: Enhancement Components: Query Engine, Server Affects Versions: 7.4, 7.1.1 Reporter: Mark Drilling Assignee: Steven Hawkins Fix For: 7.4.1 1) User has created a view MyView containing UNION all of two other views, eg "SELECT * FROM View1 UNION ALL SELECT * FROM View 2". 2) Then a user query containing a searched CASE type expression is submitted against the view, eg "SELECT CASE WHEN StringNum IS NULL THEN 0 ELSE 1 END FROM MyView" 3) With current planner the CASE expression is not pushed down to the individual sources. The enhancement request is to allow the pushdown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1623) ODBC numeric and string precision issues

by Mark Drilling (JIRA)

ODBC numeric and string precision issues ---------------------------------------- Key: TEIID-1623 URL: https://issues.jboss.org/browse/TEIID-1623 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.4, 7.3, 7.2, 7.1.1, 7.1 Reporter: Mark Drilling Assignee: Ramesh Reddy Fix For: 7.4.1, 7.1.1 ODBC is not correctly providing the precision and scale data for any numeric types. String types are also being reported 4 characters less then what is in the metadata. Attaching patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1495) Validate the TeraData Translator

by Ramesh Reddy (JIRA)

Validate the TeraData Translator -------------------------------- Key: TEIID-1495 URL: https://issues.jboss.org/browse/TEIID-1495 Project: Teiid Issue Type: Task Components: JDBC Connector Affects Versions: 7.3 Reporter: Ramesh Reddy Fix For: 7.4 Currently the Teiid does provide a Teradata translator, however it has been taken from the old MMX code, however it was never validated with Teiid to make sure this works correctly with the data source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1323) Add support for pushdown of non-literal procedure parameter expressions.

by Steven Hawkins (JIRA)

Add support for pushdown of non-literal procedure parameter expressions. ------------------------------------------------------------------------ Key: TEIID-1323 URL: https://jira.jboss.org/browse/TEIID-1323 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 We are forcing all push-down procedure arguments to be literals (for simplicity), when all expressions should be allowed. -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1450) The weather example test queries for SOAP/REST are unexecutable, as is, in README.txt file.

by Van Halbert (JIRA)

The weather example test queries for SOAP/REST are unexecutable, as is, in README.txt file. ------------------------------------------------------------------------------------------- Key: TEIID-1450 URL: https://issues.jboss.org/browse/TEIID-1450 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 7.1.1 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Blocker The test queries in the README.txt are invalid for execution, as is. And when the new line and tab characters are removed, they still don't work. Need queries that can be cut and pasted (without editing) for a RHEL OS shell script. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-1630) XQT queries failing with: [TeiidProcessingException] 1054: Error Code:1054 Message:Source: Error Code:1054 Message:'Unknown column 'c_2' in 'order clause'

by Warren Gibson (JIRA)

XQT queries failing with: [TeiidProcessingException] 1054: Error Code:1054 Message:Source: Error Code:1054 Message:'Unknown column 'c_2' in 'order clause' ----------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1630 URL: https://issues.jboss.org/browse/TEIID-1630 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.5 Environment: Teiid 7.5-Alpha1 Reporter: Warren Gibson Assignee: Steven Hawkins The following 4 XQT queries are failing query testing in MySQL50 and Teradata. I suspect they are failing in all sources. SELECT * FROM XQTDoc.defaultValueTestDocument ORDER BY XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.data, XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.key SELECT * FROM XQTDoc.defaultValueTestDocument ORDER BY XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.data DESC,XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.key SELECT * FROM XQTDoc.defaultValueTestDocument ORDER BY XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.key, XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.data SELECT * FROM XQTDoc.defaultValueTestDocument ORDER BY XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.key ASC, XQTDoc.defaultValueTestDocument.defaultValueTest.wrapper.data DESC 2011-06-09 09:16:20,342 DEBUG [org.teiid.PROCESSOR] (Worker8_QueryProcessorQueue24551) Sending error to client 9G7rbfezeXon.0 [TeiidProcessingException] 1054: Error Code:1054 Message:Source: Error Code:1054 Message:'Unknown column 'c_2' in 'order clause'' error executing statement(s): [Prepared Values: [] SQL: SELECT cast(g_1.INTNUM AS signed) AS c_0, cast(g_0.INTKEY AS signed) AS c_1 FROM smalla AS g_0, smallb AS g_1 WHERE cast(g_0.INTKEY AS signed) = cast(g_1.INTKEY AS signed) ORDER BY c_2, c_1] 1 [JDBCExecutionException] 1054: Error Code:1054 Message:'Unknown column 'c_2' in 'order clause'' error executing statement(s): [Prepared Values: [] SQL: SELECT cast(g_1.INTNUM AS signed) AS c_0, cast(g_0.INTKEY AS signed) AS c_1 FROM smalla AS g_0, smallb AS g_1 WHERE cast(g_0.INTKEY AS signed) = cast(g_1.INTKEY AS signed) ORDER BY c_2, c_1] 2 [MySQLSyntaxErrorException]Unknown column 'c_2' in 'order clause' at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:414) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:241) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:262) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:275) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:162) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:104) at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70) at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69) at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82) at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:91) at org.teiid.query.processor.xml.RelationalPlanExecutor.execute(RelationalPlanExecutor.java:98) at org.teiid.query.processor.xml.ExecSqlInstruction.process(ExecSqlInstruction.java:59) at org.teiid.query.processor.xml.XMLPlan.nextBatch(XMLPlan.java:161) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:104) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:306) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:234) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:56) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:197) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) 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: [JDBCExecutionException] 1054: Error Code:1054 Message:'Unknown column 'c_2' in 'order clause'' error executing statement(s): [Prepared Values: [] SQL: SELECT cast(g_1.INTNUM AS signed) AS c_0, cast(g_0.INTKEY AS signed) AS c_1 FROM smalla AS g_0, smallb AS g_1 WHERE cast(g_0.INTKEY AS signed) = cast(g_1.INTKEY AS signed) ORDER BY c_2, c_1] 1 [MySQLSyntaxErrorException]Unknown column 'c_2' in 'order clause' at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:340) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:82) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:137) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) ... 6 more Caused by: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'c_2' in 'order clause' at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723) at com.mysql.jdbc.Connection.execSQL(Connection.java:3283) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1332) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1467) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) ... 13 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-832) Support calling oracle stored functions returning result sets as stored procedures

by Steven Hawkins (JIRA)

Support calling oracle stored functions returning result sets as stored procedures ---------------------------------------------------------------------------------- Key: TEIID-832 URL: https://jira.jboss.org/jira/browse/TEIID-832 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 This is only an issue with oracle native drivers, which need to have the returned result set explicitly called as a return parameter. For this to work we'll need to ensure that the import metadata on a procedure is being set to isFunction appropriately and then use that metadata in the Oracle connector. -- 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, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (TEIID-1665) Optimize SELECT of all constants

by Mark Addleman (JIRA)

Optimize SELECT of all constants -------------------------------- Key: TEIID-1665 URL: https://issues.jboss.org/browse/TEIID-1665 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.4 Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor If a translator supports LIMIT but does not support select expressions, SELECT 'A' as A, 'B' as B FROM xyz GROUP BY A, B should be written as SELECT * FROM xyz LIMIT 1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1518) Add a correlated subquery evaluation cache

by Steven Hawkins (JIRA)

Add a correlated subquery evaluation cache ------------------------------------------ Key: TEIID-1518 URL: https://issues.jboss.org/browse/TEIID-1518 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins The subquery aware evaluator should cache deterministic evaluations for reuse. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2011