[
https://issues.apache.org/jira/browse/CALCITE-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270083#comment-17270083
]
Ruben Q L commented on CALCITE-4475:
------------------------------------
I see that {{SortJoinTransposeRule}} puts back the original sort on top of the
join after performing the transpose operation [1].
Could anyone explain why this is necessary? Should this be applied also for
SEMI/ANTI case?
[1]
https://github.com/apache/calcite/blob/2ee4d841312049298840c22d36db6ab980ec5994/core/src/main/java/org/apache/calcite/rel/rules/SortJoinTransposeRule.java#L160
> New Sort SEMI/ANTI Join Transpose optimization
> ----------------------------------------------
>
> Key: CALCITE-4475
> URL: https://issues.apache.org/jira/browse/CALCITE-4475
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Ruben Q L
> Priority: Major
>
> If I am not mistaken, the optimization that is currently applied by
> {{SortJoinTransposeRule}} for LEFT and RIGHT joins could also by applied to
> SEMI / ANTI joins (it would be very similar to the current LEFT join
> optimization).
> It is proposed to either improve this rule to cover SEMI / ANTI joins or
> create a new dedicated rule for this matter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
