July 2011 - teiid-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (TEIID-1532) ODBC prepared statement handling can hang

by Steven Hawkins (JIRA)

ODBC prepared statement handling can hang ----------------------------------------- Key: TEIID-1532 URL: https://issues.jboss.org/browse/TEIID-1532 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 preparedstatement execution through odbc can hang since we are never sending a synch. But we must only send a synch if there are no pending messages. -- 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-1569) Documentation on creating UDF, extending ExecutionFactory and defining @Translator name should indicate what to do with the translator name

by Van Halbert (JIRA)

Documentation on creating UDF, extending ExecutionFactory and defining @Translator name should indicate what to do with the translator name ------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1569 URL: https://issues.jboss.org/browse/TEIID-1569 Project: Teiid Issue Type: Enhancement Components: Documentation Affects Versions: 7.1.1 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor A user was trying to follow the documentation (http://docs.jboss.org/teiid/7.3.0.Final/developer-guide/en-US/html_single...) on creating a UDF and have it pushed down to the source. But they didn't make the correlation between the process of extending the ExecutionFactory and then having to use the defined @Translator name. It wasn't obvious to them. Therefore, I think it would be good to indicated in the "Required" segment of the example of extending the Oracle Connector: Required - extend the OracleExecutionFactory and add SCORE and CONTAINS as supported functions. For this example, we'll call the class MyOracleExecutionFactory. Add the org.teiid.translator.Translator annotation to the class, e.g. @Translator(name="myoracle") ------ Add a follow on sentence to indicate that the @Translator name (i.e., "myoracle") is the name to assign to the translator for the physical model for which the custom translator will be used (or something like that). -- 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-1561) Database Calender is not correctly being set in JDBC Translator

by Ramesh Reddy (JIRA)

Database Calender is not correctly being set in JDBC Translator --------------------------------------------------------------- Key: TEIID-1561 URL: https://issues.jboss.org/browse/TEIID-1561 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.4 When the JDBC translator extends the timezone property to set database calender, it is incorrectly being initialized for the executing thread. -- 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-1554) NullPointerException in NodeEditor

by Mark Addleman (JIRA)

NullPointerException in NodeEditor ---------------------------------- Key: TEIID-1554 URL: https://issues.jboss.org/browse/TEIID-1554 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.3 Reporter: Mark Addleman Assignee: Steven Hawkins NPE in NodeEditor with the following SQL: SQL 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 Stack trace: org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:497) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:214) at com.ca.chorus.db.DbExecutor.withResultSet(DbExecutor.java:198) at com.ca.chorus.db.DbExecutor.gatherResults(DbExecutor.java:367) at com.ca.chorus.db.DbExecutor.gatherResults(DbExecutor.java:361) at com.ca.chorus.teiidtest.TestTeiid.run(TestTeiid.java:72) at com.ca.chorus.teiidtest.TestTeiid.main(TestTeiid.java:24) Caused by: [TeiidException] 1 [NullPointerException] at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:177) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:557) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:335) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:218) 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:619) Caused by: java.lang.NullPointerException at org.teiid.query.optimizer.relational.plantree.NodeEditor.findAllNodesHelper(NodeEditor.java:123) at org.teiid.query.optimizer.relational.plantree.NodeEditor.findAllNodes(NodeEditor.java:102) at org.teiid.query.optimizer.relational.rules.RuleCollapseSource.execute(RuleCollapseSource.java:85) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:458) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:227) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:148) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:429) at org.teiid.dqp.internal.process.PreparedStatementRequest.generatePlan(PreparedStatementRequest.java:138) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:452) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:372) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:174) ... 7 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2011