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/04/21 18:30:00 UTC

[jira] [Resolved] (CALCITE-3927) RelSubset is not fired for rule when set gets merged

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

Haisheng Yuan resolved CALCITE-3927.
------------------------------------
    Fix Version/s: 1.23.0
       Resolution: Fixed

Fixed in [https://github.com/apache/calcite/commit/ff71266352df23208a75b9076045e89f30b9bb0b], thanks for the PR, [~botong]!

> RelSubset is not fired for rule when set gets merged
> ----------------------------------------------------
>
>                 Key: CALCITE-3927
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3927
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>            Reporter: Haisheng Yuan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.23.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In VolcanoPlanner, when set gets merged, planner fires rules again for RelNodes in both sets, but not for RelSubset. We might miss something because of this. 
> If all the logical transformation rules and physical implementation rules are separated out in different stage and physical rules don't do logical work, we might be OK. But the reality is that all the things are mixed together at the moment.



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