[
https://issues.apache.org/jira/browse/CALCITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Solimando resolved CALCITE-5264.
-------------------------------------------
Fix Version/s: 1.33.0
Resolution: Fixed
Fixed via
[{{2feb16a}}|https://github.com/apache/calcite/commit/2feb16aee9f2710bd361a787a80e1cd74cf759bb],
thanks [~aitozi] for the PR!
> HintStrategy rule exclusion does not match innermost rels
> ---------------------------------------------------------
>
> Key: CALCITE-5264
> URL: https://issues.apache.org/jira/browse/CALCITE-5264
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Aitozi
> Assignee: Aitozi
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.33.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> In CALCITE-3781, calcite can specify a hint for a relNode to let the planner
> exclude some rule when optimze. But as [~julianhyde] said, it's strange to
> only check for the {{{}rels[0]{}}}. If we have a rule to push a common
> project to the source scan, we want to prevent the common project optimized
> from the ProjectMerge Rule, it can not work, as the preserved one is at the
> bottom.
> So I proposal to check all the rels for the rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
