[teiid-issues] [JBoss JIRA] (TEIID-2625) Part of join criteria is getting ignored

[Jeff Hayes (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Hayes updated TEIID-2625:
------------------------------

    Description: 
The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. 

Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. 
 
Please see attached query plan.

One thing to note is that the same query on 7.7 works when the databases
are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? 

Any advice would be appreciated as this is affected a customer installation.

Thanks!
Jeff
 

  was:
The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. 

Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. 
 
Please see attached query plan.

Is there a fix for this or workaround for the query? 

Thanks!
Jeff
 


    
> Part of join criteria is getting ignored
> ----------------------------------------
>
>                 Key: TEIID-2625
>                 URL: https://issues.jboss.org/browse/TEIID-2625
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.7.1
>         Environment: z/OS JZOS 
>            Reporter: Jeff Hayes
>            Assignee: Steven Hawkins
>         Attachments: 7.7_Teiid_SHOWPLAN
>
>
> The second part of the join criteria (and CHORUS_J0.userid = CHORUS_B.evtuserid) appears to be getting ignored. The result has same results as when only the first criteria (CHORUS_J0.sysid = cx2.sysid) is provided. 
> Same query works are 8.1 with query plan listing both criteria in joinNode however for 7.7 only shows first criteria. 
>  
> Please see attached query plan.
> One thing to note is that the same query on 7.7 works when the databases
> are on DB2 (using DB2 translator) but not when they are on Datacom (different translator). Is this possibly a translator issue maybe not being able to support multiple join criteria? 
> Any advice would be appreciated as this is affected a customer installation.
> Thanks!
> Jeff
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira