[
https://issues.apache.org/jira/browse/CALCITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615882#comment-17615882
]
Alessandro Solimando edited comment on CALCITE-5264 at 10/11/22 2:54 PM:
-------------------------------------------------------------------------
I feel that the Jira title could be improved a bit to clarify the symptoms of
the actual limitation you are addressing.
What about "HintStrategy rule exclusion does not match innermost rels" or even
"HintStrategy rule exclusion does not match innermost statements" to be closer
to SQL parlance?
EDIT: please mark the ticket as "In Progress" when you are actively working on
it
was (Author: asolimando):
I feel that the Jira title could be improved a bit to clarify the symptoms of
the actual limitation you are addressing.
What about "HintStrategy rule exclusion does not match innermost rels" or even
"HintStrategy rule exclusion does not match innermost statements" to be closer
to SQL parlance?
> 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
> Assignee: Aitozi
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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)
