[
https://issues.apache.org/jira/browse/CALCITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated CALCITE-5264:
----------------------------
Description:
In the https://issues.apache.org/jira/browse/CALCITE-3781, calcite can specify
a hint for a relNode to let the planner exclude some rule when optimze. But as
[~julianhyde] sail, 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.
was:
In the https://issues.apache.org/jira/browse/CALCITE-3781, calcite can specify
a hint for a relNode to let the planner exclude some rule when optimze. But as
[~julianhyde] sail, 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 on in at the bottom.
So I proposal to check all the rels for the rule.
> Allow HintStrategy exclusion rules check for all the rels of a single match
> ---------------------------------------------------------------------------
>
> Key: CALCITE-5264
> URL: https://issues.apache.org/jira/browse/CALCITE-5264
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Aitozi
> Priority: Major
>
> In the https://issues.apache.org/jira/browse/CALCITE-3781, calcite can
> specify a hint for a relNode to let the planner exclude some rule when
> optimze. But as [~julianhyde] sail, 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)
