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

Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/02/21 10:50:00 UTC

[jira] [Resolved] (CALCITE-2582) FilterProjectTransposeRule does not always simplify the new filter condition

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

Stamatis Zampetakis resolved CALCITE-2582.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.19.0

Fixed in [233d9dd5671477ce06d777cd5ef3ee56df4664f8|https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=233d9dd5671477ce06d777cd5ef3ee56df4664f8].

> FilterProjectTransposeRule does not always simplify the new filter condition
> ----------------------------------------------------------------------------
>
>                 Key: CALCITE-2582
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2582
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.17.0
>            Reporter: Stamatis Zampetakis
>            Assignee: Julian Hyde
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.19.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After pushing the filter below the project a new condition is going to be generated along with a new Filter operator. The new condition is not going to be simplified if the filter operator is copied and not created using the RelBuilder. 
> Thus the resulting plan may contain redundant conditions which can have a slight impact on performance. Apart, from that tests verifying the resulting (logical/physical) plan may produce indeterministic results if the rule is applied with (a different order and in combination with other rules). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)