You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/10/11 14:00:00 UTC

[jira] [Commented] (CALCITE-5264) Allow HintStrategy exclusion rules check for all the rels of a single match

    [ https://issues.apache.org/jira/browse/CALCITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615836#comment-17615836 ] 

Aitozi commented on CALCITE-5264:
---------------------------------

hi, anyone can help review this PR ?

> 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: 20m
>  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)