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

Posted to issues@calcite.apache.org by "Haisheng Yuan (Jira)" <ji...@apache.org> on 2020/01/29 19:40:00 UTC

[jira] [Resolved] (CALCITE-3755) Ascending rule match with RelSubset operand doesn't work

     [ https://issues.apache.org/jira/browse/CALCITE-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Haisheng Yuan resolved CALCITE-3755.
------------------------------------
    Fix Version/s: 1.22.0
       Resolution: Fixed

Fixed in https://github.com/apache/calcite/commit/0b97f45752f111b56aa499b037077d27db82ec47.

> Ascending rule match with RelSubset operand doesn't work
> --------------------------------------------------------
>
>                 Key: CALCITE-3755
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3755
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>            Reporter: Haisheng Yuan
>            Priority: Major
>             Fix For: 1.22.0
>
>
> Given a rule with match pattern {{operand(Filter, operand(RelSubset))}}, when we add a new RelSubset into the set, planner will fire rules for RelSubset. 
> But in {{VolcanoRuleCall.matchRecurse}}, if !inputRels.contains(previous), it will skip. Obviously, the input rels will never contain a RelSubset, hence fails to match the rule.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)