[teiid-issues] [JBoss JIRA] (TEIID-5765) Criteria Pushdown is not working on FULL OUTER JOIN
Dmitrii Pogorelov (Jira)
issues at jboss.org
Thu Jun 13 06:09:00 EDT 2019
[ https://issues.jboss.org/browse/TEIID-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746271#comment-13746271 ]
Dmitrii Pogorelov commented on TEIID-5765:
------------------------------------------
[~shawkins] thx a lot for the quick fix, I've already checked these changes locally and it worked. Thx again!
> Criteria Pushdown is not working on FULL OUTER JOIN
> ---------------------------------------------------
>
> Key: TEIID-5765
> URL: https://issues.jboss.org/browse/TEIID-5765
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 12.0
> Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final)
> Reporter: Dmitrii Pogorelov
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 12.3, 12.1.2, 12.2.1
>
>
> Criteria Pushdown is not working on FULL OUTER JOIN (according to query plan criteria is not pushed down at all, it's in criteria of LEFT OUTER JOIN node):
> {code:noformat}
> ----------------------------------------------------------------------------
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> ProjectNode(0) output=[1] [1]
> SelectNode(1) output=[a.a] a.a = 1
> JoinNode(2) [MERGE JOIN (ALREADY_SORTED/ALREADY_SORTED)] [LEFT OUTER JOIN] criteria=[a.a=b.b] output=[a.a]
> AccessNode(3) output=[a.a] SELECT g_0.a AS c_0 FROM test.test_a AS g_0 ORDER BY c_0
> AccessNode(4) output=[b.b] SELECT g_0.b AS c_0 FROM dwh_my.test_a AS g_0 ORDER BY c_0
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the teiid-issues
mailing list