[
https://issues.apache.org/jira/browse/CALCITE-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537866#comment-17537866
]
xiong duan commented on CALCITE-5073:
-------------------------------------
[~libenchao] Hi, I don't have time to search for this issue for now. According
to the comment,The calcite have other Rule can do this, I think we don't need
to do same thing again. So I think we need to optimize the implementation to
cover the
[comment-test|https://github.com/apache/calcite/pull/2761#issuecomment-1091388684].
But I am not insist, just advice.
> JoinConditionPushRule cannot infer 'LHS.C1 = LHS.C2' from 'LHS.C1 = RHS.C1
> AND LHS.C2 = RHS.C1'
> -----------------------------------------------------------------------------------------------
>
> Key: CALCITE-5073
> URL: https://issues.apache.org/jira/browse/CALCITE-5073
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.30.0
> Reporter: Benchao Li
> Assignee: Benchao Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.31.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> For the below SQL:
> {code:java}
> SELECT * FROM T1, T2, T3
> WHERE T1.id = T3.id AND T2.id = T3.id{code}
> Currently, JoinConditionPushRule cannot infer the condition 'T1.id = T2.id'
> for the first join relation.
> There is another rule {{JoinPushThroughJoinRule}}, it can handle the above
> case in a different way (by reordering joins).
> This can be a more general optimization, which like the title says, we can
> infer more conditions from join condition (or above filter condition) to the
> Join's operands.
> It's reported in ML:
> https://lists.apache.org/thread/6fs09cgyz5rzrty90632ywoo477q0gdk
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
