vlsi commented on PR #1543: URL: https://github.com/apache/calcite/pull/1543#issuecomment-6341152737
Thank you for the patch and the discussion. I'm closing this PR because [CALCITE-3997](https://issues.apache.org/jira/browse/CALCITE-3997) (1.23.0) solved the problem for Enumerable in a different way: `ProjectMergeRule`, `FilterProjectTransposeRule`, and `SortRemoveConstantKeysRule` now implement `TransformationRule`, and `VolcanoPlanner` does not match them against `PhysicalNode` rels. Since [CALCITE-3923](https://issues.apache.org/jira/browse/CALCITE-3923) (1.25.0), a logical-only instance of any rule can be built from its config, for example `ProjectMergeRule.Config.DEFAULT.withOperandFor(LogicalProject.class).toRule()`. [CALCITE-3455](https://issues.apache.org/jira/browse/CALCITE-3455) has the details; the remaining case for JDBC rels is tracked in [CALCITE-7876](https://issues.apache.org/jira/browse/CALCITE-7876). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
