[teiid-issues] [JBoss JIRA] Created: (TEIID-568) Appears that join criteria not always propagated to dependent side of join.

Ken Johnson (JIRA) jira-events at lists.jboss.org
Fri May 8 11:34:58 EDT 2009


Appears that join criteria not always propagated to dependent side of join.
---------------------------------------------------------------------------

                 Key: TEIID-568
                 URL: https://jira.jboss.org/jira/browse/TEIID-568
             Project: Teiid
          Issue Type: Bug
          Components: Query Engine
    Affects Versions: 6.0.0
         Environment: Teiid 6.0.0 (Apr 27).  Running in JBoss AS 4.2.3 but also happens in Designer during Preview or SQL Execution.  VDB and model project set attached.  
            Reporter: Ken Johnson
            Assignee: Steven Hawkins


Getting exception in Teiid that suggests join criteria is not being propagated to the dependent side of the join in this case.  This same query and model set/VDB work correctly in MMX 5.5.3 but error in Teiid.  All data sources, drivers are the same, running on the same physical system.

The problematic model is ReportingSchema.xmiin VirtualQueryLayer.  All three views therein have the problem.  The exception below is generated from this query:

select * from AllData_Flattened

Exception:
May 08, 2009 11:21:09.246 [QueryProcessorQueue0|0] ERROR <DQP|0> ############# PW EXITING on 00000000-0000-0001-0000-000000000001.0 - error occurred ###########
[MetaMatrixComponentException] ERR.015.006.0033: Unable to evaluate Products_DS.products.productdata.ProductID: No value was available
	at com.metamatrix.query.eval.Evaluator.internalEvaluate(Evaluator.java:500)
	at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:475)
	at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:195)
	at com.metamatrix.query.eval.Evaluator.evaluateTVL(Evaluator.java:109)
	at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:98)
	at com.metamatrix.query.processor.relational.JoinNode.matchesCriteria(JoinNode.java:290)
	at com.metamatrix.query.processor.relational.MergeJoinStrategy.nextTuple(MergeJoinStrategy.java:245)
	at com.metamatrix.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:183)
	at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
	at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173)
	at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
	at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
	at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
	at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:269)
	at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:213)
	at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
	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

        



More information about the teiid-issues mailing list