May 2011 - teiid-issues - Jboss List Archives

[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-1570) pg catalog transformation issues

by Steven Hawkins (JIRA)

pg catalog transformation issues -------------------------------- Key: TEIID-1570 URL: https://issues.jboss.org/browse/TEIID-1570 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins pg_class and pg_index view definitions have type mismatches. -- 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-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-1548) Creating XA data sources from AdminShell: prop name "addtional-ds-properties" has misspelling - could cause confusion

by Paul Nittel (JIRA)

Creating XA data sources from AdminShell: prop name "addtional-ds-properties" has misspelling - could cause confusion --------------------------------------------------------------------------------------------------------------------- Key: TEIID-1548 URL: https://issues.jboss.org/browse/TEIID-1548 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.1.1 Environment: All Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor With help from Ramesh, I was able to create an XA data source using: dp.setProperty( "addtional-ds-properties", "ServerName=foo, PortNumber=50000, DatabaseName=dbdata, DriverType=4, User=someuser, Password=somepwd" ) I noticed that "additional" was misspelled and tried that. It doesn't work; you must use the misspelled version. I'd like to see this be corrected before some user tries to use this with the correct spelling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1567) Sybase translator needs to handle CROSS JOIN syntax.

by Mark Drilling (JIRA)

Sybase translator needs to handle CROSS JOIN syntax. ---------------------------------------------------- Key: TEIID-1567 URL: https://issues.jboss.org/browse/TEIID-1567 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.1.1 Reporter: Mark Drilling Assignee: Steven Hawkins Encountered this issue querying Sybase ASE 12.5 datasource. The pushed down query contained CROSS JOIN syntax resulting in failure since Sybase ASE 12 does not support cross join. This needs to be handled in the translator. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1546) Be more selective as to what are created as bind variables

by Steven Hawkins (JIRA)

Be more selective as to what are created as bind variables ---------------------------------------------------------- Key: TEIID-1546 URL: https://issues.jboss.org/browse/TEIID-1546 Project: Teiid Issue Type: Feature Request Components: JDBC Connector, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins It is desirable for user entered literals to not be handled as bind variables since the plans generated will be more amenable to optimization. -- 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-1549) aggregate unrelated order by error

by Steven Hawkins (JIRA)

aggregate unrelated order by error ---------------------------------- Key: TEIID-1549 URL: https://issues.jboss.org/browse/TEIID-1549 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 When using an aggregate with an unrelated order by clause, e.g. TEXTAGG(FOR c1 ORDER BY c2), the result is an error at processing time. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2011