[
https://issues.apache.org/jira/browse/CALCITE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938204#comment-16938204
]
jin xing commented on CALCITE-3367:
-----------------------------------
I will close this Jira for now.
The reason is that
# A more straightforward/intuitive way to generate semi-join/anti-join from
IN/EXIST clause is by decorrelation, check
https://issues.apache.org/jira/browse/CALCITE-3373
# The matching pattern for optimization in AntiJoinRule is too strict and
limited.
> Add AntiJoinRule to convert project-filter-join-aggregate into anti-join
> ------------------------------------------------------------------------
>
> Key: CALCITE-3367
> URL: https://issues.apache.org/jira/browse/CALCITE-3367
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: jin xing
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> This Jira proposes to add AntiJoinRule to convert
> project-filter-join-aggregate into anti-join.
> The idea is from SemiJoinRule.
> This issue was found when I resolve CALCITE-3363 in
> [https://github.com/apache/calcite/pull/1466]
> I failed to construct an anti-join operator from SQL string.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
