March 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-776) Enhancem multisource planning with aggregate pushdown

by Steven Hawkins (JIRA)

Enhancem multisource planning with aggregate pushdown ----------------------------------------------------- Key: TEIID-776 URL: https://jira.jboss.org/jira/browse/TEIID-776 Project: Teiid Issue Type: Feature Request Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.x Multisource modification happens after all rules have been fired, which means that aggregate and other sort/distinct pushdown optimizations do not happen. -- 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

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1490) In the process of loading the schema metadata and duplicate table is found, add a suggestion to the error message to use FQN option

by Van Halbert (JIRA)

In the process of loading the schema metadata and duplicate table is found, add a suggestion to the error message to use FQN option ------------------------------------------------------------------------------------------------------------------------------------ Key: TEIID-1490 URL: https://issues.jboss.org/browse/TEIID-1490 Project: Teiid Issue Type: Enhancement Components: Server Affects Versions: 7.1.1 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor When the dynamic vdb was triggering loading the metadata, a duplicate table was encountered and an exception was thrown indicating as such. It would be good to suggest in the message that the user should change the FQN option to true. This would help lead the user to resolving this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-417) Add REST Support to Data Services

by Ted Jones (JIRA)

Add REST Support to Data Services --------------------------------- Key: TEIID-417 URL: https://jira.jboss.org/jira/browse/TEIID-417 Project: Teiid Issue Type: Feature Request Components: SOAP Services Reporter: Ted Jones Assignee: Ted Jones Need to add support for REST to data services. REST needs be enabled in Axis2 and a REST endpoint should be added to the data services WSDL. -- 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

13 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (TEIID-1529) LIMIT not pushed down for queries with subselects and ORDER BY

by Mark Addleman (JIRA)

LIMIT not pushed down for queries with subselects and ORDER BY -------------------------------------------------------------- Key: TEIID-1529 URL: https://issues.jboss.org/browse/TEIID-1529 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.3 Reporter: Mark Addleman Assignee: Steven Hawkins It doesn't look like the engine pushes down LIMIT in the following query: SELECT B."SYSID", B."USERID", (SELECT COUNT(*) FROM (SELECT * FROM notes.RETRIEVE_NOTES WHERE OBJECT_PKEY = XMLSERIALIZE(XMLELEMENT("SECURITY.BASEUSER", XMLATTRIBUTES(B."SYSID",B."USERID")) as String)) as foo) as C_notesForObject, 'SECURITY.BASEUSER' as "__objecttype__" FROM "SECURITY.BASEUSER" as B ORDER BY B."USERID" ASC LIMIT 10 However, the engine does push down the LIMIT in the same query without the ORDER BY: SELECT B."SYSID", B."USERID", (SELECT COUNT(*) FROM (SELECT * FROM notes.RETRIEVE_NOTES WHERE OBJECT_PKEY = XMLSERIALIZE(XMLELEMENT("SECURITY.BASEUSER", XMLATTRIBUTES(B."SYSID",B."USERID")) as String)) as foo) as C_notesForObject, 'SECURITY.BASEUSER' as "__objecttype__" FROM "SECURITY.BASEUSER" as B LIMIT 10 Another piece of relevant information is notes.RETRIEVE_NOTE is a stored procedure backed by java code in a translator. Since SECURITY.BASEER contains ~20,000 rows and each row requires a select against the RETRIEVE_NOTE stored procedure, the difference in processing time is huge: about two minutes with the ORDER BY versus a few hundred milliseconds without the ORDER BY. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIID-1531) ODBC charset issues

by Steven Hawkins (JIRA)

ODBC charset issues ------------------- Key: TEIID-1531 URL: https://issues.jboss.org/browse/TEIID-1531 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 In testing odbc using the postgres jdbc issue I can see that we are not consistently handling the conversion of client encodings to charsets. Also later postgres clients can use the key UNICODE to refer to UTF-8. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1164) Getting the Procedure Parameter metadata is not supported in ODBC

by Ramesh Reddy (JIRA)

Getting the Procedure Parameter metadata is not supported in ODBC ----------------------------------------------------------------- Key: TEIID-1164 URL: https://jira.jboss.org/browse/TEIID-1164 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.1 Reporter: Ramesh Reddy Currently postgreSQL uses the JDBC array types in issuing the query to read the Procedure parameters. However, Teiid does not support the Array types yet in the JDBC layer, thus this is currently not implemented. This needs to be fixed to correctly return the metadata about the procedures. -- 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

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIID-1538) Invalid conversion from type class java.lang.Object with value 'oracle.sql.ROWID@1379cbd' to type class java.lang.String

by Russell Steel (JIRA)

Invalid conversion from type class java.lang.Object with value 'oracle.sql.ROWID@1379cbd' to type class java.lang.String ------------------------------------------------------------------------------------------------------------------------ Key: TEIID-1538 URL: https://issues.jboss.org/browse/TEIID-1538 Project: Teiid Issue Type: Bug Components: Query Engine, Server Affects Versions: 7.3 Reporter: Russell Steel Assignee: Steven Hawkins Attachments: O2_Teiid.vdb, server.log I have a VDB with 3 queries that select direct from an Oracle table, where a SUBSTRING function is being used on the ROWID column. I can successfully SELECT from the 3 queries without error, but when selecting from a 4th view that is join 2 of the 3 tables that I can successfully SELECT from via SQL SquirreL, the 4th view query is failing with; 2011-03-31 11:35:14,968 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) [Ljava.lang.Object;@168fb5a [TransformationException]Invalid conversion from type class java.lang.Object with value 'oracle.sql.ROWID@1379cbd' to type class java.lang.String at org.teiid.core.types.basic.ObjectToAnyTransform.transformDirect(ObjectToAnyTransform.java:59) at org.teiid.core.types.Transform.transform(Transform.java:47) at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:781) at org.teiid.dqp.internal.process.DataTierTupleSource.correctTypes(DataTierTupleSource.java:155) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:227) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:154) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) 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.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:158) at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:196) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:162) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:161) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:150) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:184) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1535) pg/odbc support should report rel oid with column metadata

by Steven Hawkins (JIRA)

pg/odbc support should report rel oid with column metadata ---------------------------------------------------------- Key: TEIID-1535 URL: https://issues.jboss.org/browse/TEIID-1535 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 describe columns should return the proper table oid and attnum for each column. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1474) Add query hint to limit parallel execution of union members

by Howard Abrams (JIRA)

Add query hint to limit parallel execution of union members ----------------------------------------------------------- Key: TEIID-1474 URL: https://issues.jboss.org/browse/TEIID-1474 Project: Teiid Issue Type: Feature Request Reporter: Howard Abrams Assignee: Steven Hawkins We would like a new query hint to limit the number of parallel executions of union members. This is useful in two situations: 1. When the queries are expensive, but the overall union contains a limit that is most likely to be fulfilled by the first member of the union 2. When the queries are backed by a common resource which may be overloaded by multiple queries The addition of a hint would make this manageable by the client; perhaps something like "/*+ parallel=2*/"? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIID-1515) ODBC does not report primarykeys on the tables

by Ramesh Reddy (JIRA)

ODBC does not report primarykeys on the tables ---------------------------------------------- Key: TEIID-1515 URL: https://issues.jboss.org/browse/TEIID-1515 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.3, 7.2, 7.1.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 7.1.1 ODBC Driver upon retrieval of metadata is not reporting the Primary Key information. Also it does not report "isNullable" property correctly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2011