[ https://issues.jboss.org/browse/TEIID-2870?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2870: ------------------------------------- * Yes, CROSS is eliminated because of the capabilities of translator define the JOINs as based KEY. So this gets handled by Teiid engine * Correct about LEFT OUTER behavior. On RIGHT OUTER, on I have two different scenarios. Where foreign table is available 1) only as embedded in parent's table 2) embedded in parent's table + a separate table, note the separate table may contain more rows than the embedded In scenario (1) yes RIGHT OUTER and INNER are same. However, on the scenario (2) INNER is fine, RIGHT OUTER is not, and currently I am just throwing exception. So, with this feature, I hope to detect that RIGHT OUTER in the last scenario during the planning phase and avoid the exception and do the processing in Teiid engine over the two separate tables. -- 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