November 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1292) Invalid Fetch Size using JDBC ODBC bridge to query MS Access via a Teiid VDB

by Warren Gibson (JIRA)

Invalid Fetch Size using JDBC ODBC bridge to query MS Access via a Teiid VDB ---------------------------------------------------------------------------- Key: TEIID-1292 URL: https://jira.jboss.org/browse/TEIID-1292 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steven Hawkins When using Squirrel as a client to query an Access DB with a Teiid VDB using the ODBC bridge I am getting an invalid Fetch Size. I have a DSN set up and can query the Access DB with an ODBC client using the DSN. There seems to be lots of chatter on the web about this but I didn't find a solution. This seems to be a KI with the JDBC ODBC bridge and is not a Teiid Bug but possibly Teiid can offer a workaround. 2010-10-05 15:52:17,421 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue16) Source-specific command: SELECT EmpData.LastName, EmpData.FirstName, EmpData.MiddleName, EmpData.EmpId, EmpData.Department, EmpData.AnnualSalary, EmpData.Title, EmpData.HomePhone, EmpData.Manager, EmpData.Street, EmpData.City, EmpData.State, EmpData.zip FROM EmpData 2010-10-05 15:52:17,421 DEBUG [org.teiid.COMMAND_LOG] (Worker3_QueryProcessorQueue16) ERROR SRC COMMAND: endTime=2010-10-05 15:52:17.421 requestID=o1eKkvzGMfT4.7 sourceCommandID=2 txID=null modelName=ODBCTesting connectorBindingName=jdbc-simple sessionID=o1eKkvzGMfT4 principal=admin@teiid-security finalRowCount=null 2010-10-05 15:52:17,421 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue16) Connector worker process failed for atomic-request=o1eKkvzGMfT4.7.2.1 [JDBCExecutionException] 0: Error Code:0 Message:'Invalid Fetch Size' error executing statement(s): [Prepared Values: [] SQL: SELECT EmpData.LastName, EmpData.FirstName, EmpData.MiddleName, EmpData.EmpId, EmpData.Department, EmpData.AnnualSalary, EmpData.Title, EmpData.HomePhone, EmpData.Manager, EmpData.Street, EmpData.City, EmpData.State, EmpData.zip FROM EmpData] 1 [SQLException]Invalid Fetch Size at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:189) 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(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.sql.SQLException: Invalid Fetch Size at sun.jdbc.odbc.JdbcOdbcStatement.setFetchSize(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedStatement.setFetchSize(WrappedStatement.java:647) at org.teiid.translator.jdbc.JDBCBaseExecution.setSizeContraints(JDBCBaseExecution.java:138) at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:167) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:82) ... 12 more -- 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

15 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1259) Multi-line error message is difficult to follow

by Steven Hawkins (JIRA)

Multi-line error message is difficult to follow ----------------------------------------------- Key: TEIID-1259 URL: https://jira.jboss.org/browse/TEIID-1259 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 7.1.1 Errors with JDBC source queries are producing a multi-line error message that is hard to follow in the logs. -- 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

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1258) fixed formatting of translators.xml in reference guide

by Darrin Mison (JIRA)

fixed formatting of translators.xml in reference guide ------------------------------------------------------ Key: TEIID-1258 URL: https://jira.jboss.org/browse/TEIID-1258 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins The formatting of http://anonsvn.jboss.org/repos/teiid/branches/7.1.x/documentation/referen... made the XML very very hard to read. A patch is attached with the XML reformatted for readability. A few spelling mistakes have also been corrected. -- 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

15 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-1205) First deployment of weather example fails to query and requires restarting JBoss AS (weather does not exist)

by Paul Nittel (JIRA)

First deployment of weather example fails to query and requires restarting JBoss AS (weather does not exist) ------------------------------------------------------------------------------------------------------------ Key: TEIID-1205 URL: https://jira.jboss.org/browse/TEIID-1205 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Fedora 12, Teiid 7.1 CR2 Reporter: Paul Nittel Assignee: Steve Hawkins I started by installing JBoss AS and Teiid 7.1CR2 (plus JDBC drivers). After starting JBoss AS, I deployed the weather-ds and weather-vdb files. After seeing the VDB was "active" I used the simpleclient to execute this query: ./run.sh localhost 31000 weather "select t.* from (call weather.invoke(action='GET', endpoint=querystring('', '63017 10530' as zipCodeList, 'glance' as product, '2010-08-12T14:00:00' as \"begin\", '2010-08-12T14:00:00' as \"end\", 'maxt' as maxt, 'mint' as mint) )) w, XMLTABLE('/dwml/data/parameters' passing w.result columns Location string path '@applicable-location', TempName string path 'temperature/name', TempValue string path 'temperature/value' ) t" The result was: [QueryMetadataException]weather does not exist. at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:176) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.resolveSubQuery(SimpleQueryResolver.java:208) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:362) at org.teiid.query.sql.lang.SubqueryFromClause.acceptVisitor(SubqueryFromClause.java:127) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:73) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:259) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:523) at org.teiid.query.sql.lang.From.acceptVisitor(From.java:144) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:186) at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:103) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:174) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:126) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:100) at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:277) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:378) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:437) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:351) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:174) 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: [QueryMetadataException]weather does not exist. at org.teiid.query.metadata.CompositeMetadataStore.getSchema(CompositeMetadataStore.java:65) at org.teiid.query.metadata.CompositeMetadataStore.getStoredProcedure(CompositeMetadataStore.java:108) at org.teiid.query.metadata.TransformationMetadata.getStoredProcedureInfoForProcedure(TransformationMetadata.java:300) at org.teiid.query.metadata.BasicQueryMetadataWrapper.getStoredProcedureInfoForProcedure(BasicQueryMetadataWrapper.java:273) at org.teiid.query.metadata.BasicQueryMetadataWrapper.getStoredProcedureInfoForProcedure(BasicQueryMetadataWrapper.java:273) at org.teiid.query.resolver.command.ExecResolver.findCommandMetadata(ExecResolver.java:79) at org.teiid.query.resolver.command.ExecResolver.resolveProceduralCommand(ExecResolver.java:246) at org.teiid.query.resolver.ProcedureContainerResolver.resolveCommand(ProcedureContainerResolver.java:195) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:174) ... 26 more I shut down JBoss AS and restarted it and was able to execute the same query successfully. -- 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

15 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1297) Missing message key when no result for executes system procedure: "Request.no_result_set" in: org.teiid.query.i18n

by Ted Jones (JIRA)

Missing message key when no result for executes system procedure: "Request.no_result_set" in: org.teiid.query.i18n ------------------------------------------------------------------------------------------------------------------ Key: TEIID-1297 URL: https://jira.jboss.org/browse/TEIID-1297 Project: Teiid Issue Type: Bug Affects Versions: 7.1.1 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 7.1.1 Missing message key when no result for executes system procedure: WARN [PROCESSOR] Processing exception '<Missing message for key "Request.no_result_set" in: org.teiid.query.i18n>' for request c6cjFsmq1zcB.6. Exception type org.teiid.api.exception.query.QueryValidatorException thrown from org.teiid.dqp.internal.process.Request.createCommandContext(Request.java:222). Enable more detailed logging to see the entire stacktrace. -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1303) Sybase 15 Queries - Incorrect syntax on queries with FULL OUTER JOIN

by Warren Gibson (JIRA)

Sybase 15 Queries - Incorrect syntax on queries with FULL OUTER JOIN -------------------------------------------------------------------- Key: TEIID-1303 URL: https://jira.jboss.org/browse/TEIID-1303 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steven Hawkins The following query and error is an example of Sybase 15 queries with a FULL OUTER JOIN. Sybase does not support FULL OUTER JOIN and a Translator change is needed. SELECT BQT2.SmallB.IntKey, y.DoubleNum FROM BQT2.SmallB FULL OUTER JOIN (SELECT IntKey, DoubleNum FROM BQT1.MediumA) AS y ON BQT2.SmallB.IntKey = y.IntKey ORDER BY IntKey, DoubleNum - RDBMS_Test_Queries_9500_TestQuery113 Error Code:102 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:102 Message:Error Code:102 Message:'Incorrect syntax near 'FULL'.' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.IntKey AS c_0, g_1.DoubleNum AS c_1 FROM SmallB g_0 FULL OUTER JOIN MediumA g_1 ON g_0.IntKey = g_1.IntKey ORDER BY c_0, c_1] -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1296) Multi-Source may not be wrapping the transactional scope correctly

by Ramesh Reddy (JIRA)

Multi-Source may not be wrapping the transactional scope correctly ------------------------------------------------------------------ Key: TEIID-1296 URL: https://jira.jboss.org/browse/TEIID-1296 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 The distributed transaction is required when multiple sources are involved. Teiid determines this by counting the number of access nodes that represent sources. In the multi-source it counts as one, even in the cases it involves multiple sources underneath. -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1299) Remove un-implemented Admin API methods.

by Ramesh Reddy (JIRA)

Remove un-implemented Admin API methods. ---------------------------------------- Key: TEIID-1299 URL: https://jira.jboss.org/browse/TEIID-1299 Project: Teiid Issue Type: Task Components: AdminApi Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1, 7.2 Admin methods setRuntimeProperty - is not implemented, and signature may be not sufficient to implement in the future. Remove this and add when feature is required. getWorkManagerStats(String identifier) - since there is going to be single Teiid engine in a given VM, there is no need for the "identifier" parameter, this needs to be removed for simplicity. getProcesses(String processIdentifier) - this method is not also implemented, it was kept to make "AdminApiServerDiscovery" supported. However the way it is currently it is not functional, either this needs to be removed or fixed for correct usage. -- 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

15 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1262) Update Netty to 3.2.1 in the 7.1.x branch

by Van Halbert (JIRA)

Update Netty to 3.2.1 in the 7.1.x branch ----------------------------------------- Key: TEIID-1262 URL: https://jira.jboss.org/browse/TEIID-1262 Project: Teiid Issue Type: Task Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1.1 Netty needs to be updated to 3.2.1 version -- 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

15 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1293) subqueries should not allow select into

by Steven Hawkins (JIRA)

subqueries should not allow select into --------------------------------------- Key: TEIID-1293 URL: https://jira.jboss.org/browse/TEIID-1293 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 We already validate that union cannot contain a select into, we should ensure that exists/scalarsubquries/inlineviews/etc. cannot use select into. -- 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

15 years, 5 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2010