[JBoss JIRA] Created: (TEIID-914) OnWrapTransactionTests.testMultipleSourceTimeout test fails due to due to execpted error message is different
by Van Halbert (JIRA)
OnWrapTransactionTests.testMultipleSourceTimeout test fails due to due to execpted error message is different
-------------------------------------------------------------------------------------------------------------
Key: TEIID-914
URL: https://jira.jboss.org/jira/browse/TEIID-914
Project: Teiid
Issue Type: Bug
Components: Integration Tests
Affects Versions: 7.0
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
The OnWrapTransactionTests.testMultipleSourceTimeout test fails due to expected message is different. It appears the upstream error being thrown by sendRequestMessageAndWait(..) in MMStatement.executeSql(String[] commands, boolean isBatchedCommand, Boolean requiresResultSet) has changed. If I take the message from the caught exception and prepend to the created message and use that message in the MMSQLException throw, then the test passes.
Also, another problem with the current error message is that it gives no indication as to the problem why the statement cannot run, it only provides a general message, ilke the following:
"Error trying to execute a statement [insert into pm1.g1 (e1, e2) values(600,'600'), insert into pm1.g2 (e1, e2) values (600,'600') .........."
--
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, 4 months
[JBoss JIRA] Created: (TEIID-929) Virtual Procedure - IllegalArgumentException: Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl
by Warren Gibson (JIRA)
Virtual Procedure - IllegalArgumentException: Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-929
URL: https://jira.jboss.org/jira/browse/TEIID-929
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Warren Gibson
Assignee: Steven Hawkins
They following virtual procedure is failing with an IllegalArumentException. Does "Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl" mean anything to you? This query does run in Designer.
SELECT DNT FROM VirtProcs.vDate_n_Time WHERE intkey_in = 2"
2010-01-12 12:49:12,387 ERROR [Worker7_QueryProcessorQueue0] org.teiid.DQP - Unexpected exception for request 0.0
java.lang.IllegalArgumentException: Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl
at com.metamatrix.core.util.ArgCheck.isInstanceOf(ArgCheck.java:353)
at com.metamatrix.core.util.ArgCheck.isInstanceOf(ArgCheck.java:337)
at org.teiid.metadata.TransformationMetadata.isXMLGroup(TransformationMetadata.java:701)
at com.metamatrix.query.metadata.TempMetadataAdapter.isXMLGroup(TempMetadataAdapter.java:429)
at com.metamatrix.query.metadata.TempMetadataAdapter.isXMLGroup(TempMetadataAdapter.java:429)
at com.metamatrix.query.metadata.TempMetadataAdapter.isXMLGroup(TempMetadataAdapter.java:429)
at com.metamatrix.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:297)
at com.metamatrix.query.sql.lang.UnaryFromClause.acceptVisitor(UnaryFromClause.java:82)
at com.metamatrix.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:61)
at com.metamatrix.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:72)
at com.metamatrix.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:246)
at com.metamatrix.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:431)
at com.metamatrix.query.sql.lang.From.acceptVisitor(From.java:143)
at com.metamatrix.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:61)
at com.metamatrix.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:177)
at com.metamatrix.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:94)
at com.metamatrix.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:176)
at com.metamatrix.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:128)
at com.metamatrix.query.optimizer.relational.RelationalPlanner.resolveVirtualGroup(RelationalPlanner.java:905)
at com.metamatrix.query.optimizer.relational.RelationalPlanner.buildTree(RelationalPlanner.java:635)
at com.metamatrix.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:553)
at com.metamatrix.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:516)
at com.metamatrix.query.optimizer.relational.RelationalPlanner.generatePlan(RelationalPlanner.java:393)
at com.metamatrix.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:144)
at com.metamatrix.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:109)
at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:470)
at org.teiid.dqp.internal.process.Request.processRequest(Request.java:556)
at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:336)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:176)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211)
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)
--
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, 4 months
[JBoss JIRA] Created: (TEIID-753) MySQL translator issues
by Steven Hawkins (JIRA)
MySQL translator issues
-----------------------
Key: TEIID-753
URL: https://jira.jboss.org/jira/browse/TEIID-753
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
MySQL does not change the autocommit flag to false when running in a global transaction, however the current autocommit detection logic does not take whether we're in an xa transaction into account.
Also the timestamp literal format TIMESTAMP(...) actually produces a null value. This should be changed to either the jdbc escape syntax or simply the string literal form.
--
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, 4 months