[ https://issues.apache.org/jira/browse/CALCITE-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731212#comment-17731212 ]
Benchao Li commented on CALCITE-5740: ------------------------------------- [~rongr] I agree that your last case can be improved, by introducing another rule which matches any node on top of {{Join}}. Do you have any idea in your mind how to analyze the "any node"'s input fields? > Support for AggToSemiJoinRule > ----------------------------- > > Key: CALCITE-5740 > URL: https://issues.apache.org/jira/browse/CALCITE-5740 > Project: Calcite > Issue Type: New Feature > Reporter: Rong Rong > Priority: Major > > **Description** > Currently we only have JoinToSemiJoin and ProjectToSemiJoin rule. which in > the rule itself it performance check and see if the project accesses columns > from the RHS result > This can be extended to Aggregate as well, experimental code: > https://github.com/walterddr/calcite/pull/1/files > **Alternative** > Alternative is to add a project/calc between the join and the aggregate to > activate the project-to-semi-join rule. please share if there's any other > alternative if I haven't considered. > thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)