[
https://issues.apache.org/jira/browse/CALCITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119058#comment-17119058
]
Anton Haidai commented on CALCITE-3939:
---------------------------------------
[~julianhyde] , sorry, it took long to compose the previous comment so I didn't
see your comment before submitting.
I'm still not sure if this is a bug an if this is something that could affect
other Calcite's users.
To summarize, if my conclusions are correct, changes in the scope of this task
may lead to ignored rules on logical nodes with input if non-logical nodes
(like non-logical table scans) are used in logical plans.
If it seems like a bug for Calcite's developers, please feel free to create a
new issue regarding it or ping me if I should create this new issue.
> Change UnionEliminatorRule and ProjectRemoveRule to auto pruning
> SubstitutionRule
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-3939
> URL: https://issues.apache.org/jira/browse/CALCITE-3939
> Project: Calcite
> Issue Type: Improvement
> Reporter: Botong Huang
> Priority: Major
> Fix For: 1.23.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> UnionEliminatorRule and ProjectRemoveRule are both pruning rules for a
> RelNode. They can also become SubstitutionRule with autoprune enabled
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
