August 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1582) Avoid buffering in enhanced sort merge join

by Steven Hawkins (JIRA)

Avoid buffering in enhanced sort merge join ------------------------------------------- Key: TEIID-1582 URL: https://issues.jboss.org/browse/TEIID-1582 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 If one side is small enough, then the other side should be accessed by a non-buffered iterator. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1577) ArrayIndexOutOfBoundsException in queries with ORDER BY

by Claudio Venturini (JIRA)

ArrayIndexOutOfBoundsException in queries with ORDER BY ------------------------------------------------------- Key: TEIID-1577 URL: https://issues.jboss.org/browse/TEIID-1577 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Environment: Teiid 7.4 cr1 (with build #1483 of Teiid Engine 7.4 cr2) deployed on JBoss AS 5.1, installed on Ubuntu Server 10.04 LTS. Three source models: one in MySQL 5.1.51 (on the same machine of JBoss), one on SQLServer 2000 (on another machine), one on SQLServer 2005 (on another machine) Reporter: Claudio Venturini Assignee: Steven Hawkins The models are almost the same described in [https://issues.jboss.org/browse/TEIID-1576]. There's a global view model (named "aop") that integrates the data from three view models (using a UNION ALL operator). It has been already described in [https://issues.jboss.org/browse/TEIID-1562]. When I run the following query I get an IndexOutOfBoundsException: {code:sql} SELECT codop, codice, data, codref, groupdim FROM aop.misura124.aop.vendita_referenza order by data asc {code} The content of the log file is the following: {noformat} 2011-05-04 17:36:38,681 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-1) START USER COMMAND: startTime=2011-05-04 17:36:38.681 requestID=fvJwLRknMQEc.2 txID=null sessionID=fvJwLRknMQEc applicationName=JDBC principal=admin@teiid-security vdbName=misura124 vdbVersion=1 sql=SELECT VDBName AS TABLE_CAT, SchemaName AS TABLE_SCHEM, Name AS TABLE_NAME, CASE WHEN IsSystem = 'true' and UCASE(Type) = 'TABLE' THEN 'SYSTEM TABLE' ELSE UCASE(Type) END AS TABLE_TYPE, Description AS REMARKS, NULL AS TYPE_CAT, NULL AS TYPE_SCHEM, NULL AS TYPE_NAME, NULL AS SELF_REFERENCING_COL_NAME, NULL AS REF_GENERATION, IsPhysical AS ISPHYSICAL FROM SYS.Tables g WHERE UCASE(VDBName) LIKE ? ESCAPE '\' AND UCASE(SchemaName) LIKE ? ESCAPE '\' AND UCASE(Name) LIKE ? ESCAPE '\' AND (CASE WHEN IsSystem = 'true' and UCASE(Type) = 'TABLE' THEN 'SYSTEM TABLE' ELSE UCASE(Type) END LIKE ? ESCAPE '\' ) ORDER BY TABLE_TYPE, TABLE_SCHEM, TABLE_NAME codop, codice, data, codref, groupdim FROM aop.misura124.aop.vendita_referenza order by data asc 2011-05-04 17:36:40,071 DEBUG [org.teiid.COMMAND_LOG] (Worker1_QueryProcessorQueue6) ERROR USER COMMAND: endTime=2011-05-04 17:36:40.071 requestID=qaDAPpF9gmnN.0 txID=null sessionID=qaDAPpF9gmnN principal=admin@teiid-security vdbName=misura124 vdbVersion=1 finalRowCount=null 2011-05-04 17:36:40,071 ERROR [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue6) Unexpected exception for request qaDAPpF9gmnN.0 java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.get(ArrayList.java:324) at org.teiid.query.optimizer.relational.rules.RuleMergeVirtual.checkForSimpleProjection(RuleMergeVirtual.java:288) at org.teiid.query.optimizer.relational.rules.RuleMergeVirtual.doMerge(RuleMergeVirtual.java:158) at org.teiid.query.optimizer.relational.rules.RuleMergeVirtual.execute(RuleMergeVirtual.java:73) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:460) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:225) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:192) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:429) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:452) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:425) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:224) 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$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {noformat} If I remove the GROUP BY statement, the query works. I also tried to sort on other fields, but the result doesn't change. As always, I've reduced the models in order to highlight where the problem is. I attach the project which contains them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1534) The driver incorrectly reports column labels as column names

by Steven Hawkins (JIRA)

The driver incorrectly reports column labels as column names ------------------------------------------------------------ Key: TEIID-1534 URL: https://issues.jboss.org/browse/TEIID-1534 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 The metadata for column names are actually column labels and the real value for the column name is not actually reported by the MetadataProcesor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-513) Make the commandcontext available to the evaluatablevisitor

by Steven Hawkins (JIRA)

Make the commandcontext available to the evaluatablevisitor ----------------------------------------------------------- Key: TEIID-513 URL: https://jira.jboss.org/jira/browse/TEIID-513 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.x If the commandcontext is available to the evaluatablevisitor, then we can make a better decision about what determinism level to accept for planning function evaluation. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1574) Add new permission types for alter/execute

by Steven Hawkins (JIRA)

Add new permission types for alter/execute ------------------------------------------ Key: TEIID-1574 URL: https://issues.jboss.org/browse/TEIID-1574 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 In addition to CRUD, we should have more idiomatic permissions for allowing alter (alter) statements and for procedure/function execution (execute). For backwards compatibility READ would still be accepted as the execute permission. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1572) Teiid ODBC does not handle SET and Show operations correctly

by Ramesh Reddy (JIRA)

Teiid ODBC does not handle SET and Show operations correctly ------------------------------------------------------------ Key: TEIID-1572 URL: https://issues.jboss.org/browse/TEIID-1572 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.2 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.4 - ODBC protocol expects 'SET' string as command completion when a SET command is issued, this is being ignored - PG lets user query the database on configuration using SHOW command. Teiid supports the SHOW command, however since not all properties defined during initialization and some defaults not set explicitly they are not available for the SHOW command. This command being used by Python client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1595) User without required role is able to explicitly create a temporary table

by Paul Nittel (JIRA)

User without required role is able to explicitly create a temporary table ------------------------------------------------------------------------- Key: TEIID-1595 URL: https://issues.jboss.org/browse/TEIID-1595 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Paul Nittel Assignee: Steven Hawkins In testing roles, I created a VDB with roles, some of which permit the creation of temporary tables. It turns out Teiid allows creation of temporary tables whether or not you're allowed to. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1571) Error due to merge virtual with join and group by

by Steven Hawkins (JIRA)

Error due to merge virtual with join and group by ------------------------------------------------- Key: TEIID-1571 URL: https://issues.jboss.org/browse/TEIID-1571 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 A query such as "SELECT x FROM (select c.e1 as x from (select e1 from pm1.g1) as c, pm1.g2 as d) as a group by x" will fail with invalid group by column aliases due to an invalid merge. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1644) Teiid not passing back min/max as result data element when MIN/MAX used in query

by Warren Gibson (JIRA)

Teiid not passing back min/max as result data element when MIN/MAX used in query -------------------------------------------------------------------------------- Key: TEIID-1644 URL: https://issues.jboss.org/browse/TEIID-1644 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.5 Environment: Teiid7.5 Alfa1 Reporter: Warren Gibson Assignee: Steven Hawkins Attachments: QT_MySql50_Push.vdb Not passing back min/max as result data element when MIN/MAX used in query. Two queries are shown below with actual results and expected results. This may be related to JIRA 1643 also. VDB is attached. SELECT MIN(IntKey) FROM BQT1.SmallA Actual Results: <dataElement type="integer">IntKey</dataElement> Expected Results: <dataElement type="integer">min</dataElement> - - - - - - - - - - - - - - - - - SELECT MAX(IntKey) FROM BQT1.SmallA Actual Results: <dataElement type="integer">IntKey</dataElement> Expected Results: <dataElement type="integer">max</dataElement> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1583) importer.useFullSchemaName property default value is incorrectly documented

by Scott Dawson (JIRA)

importer.useFullSchemaName property default value is incorrectly documented --------------------------------------------------------------------------- Key: TEIID-1583 URL: https://issues.jboss.org/browse/TEIID-1583 Project: Teiid Issue Type: Bug Affects Versions: 7.3 Environment: JBoss AS 5.1 Teiid 7.3 Reporter: Scott Dawson Assignee: Steven Hawkins In the Teiid Reference Document, table 10.4 'Importer Properties' in section 10.2.2 'JDBC Translator', specifies the default value for the useFullSchemaName property as 'true' which is incorrect, it defaults to 'false'. As Ramesh Reddy says in the forum thread (see forum link), it may be preferable to change the code to match the documentation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2011