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

Posted to issues@impala.apache.org by "Steve Carlin (Jira)" <ji...@apache.org> on 2026/04/11 00:40:00 UTC

[jira] [Resolved] (IMPALA-14419) Calcite Planner: v1.40 of IntersectToDistinctRule throws exception

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

Steve Carlin resolved IMPALA-14419.
-----------------------------------
    Resolution: Won't Fix

Upgraded straight to 1.41

> Calcite Planner: v1.40 of IntersectToDistinctRule throws exception
> ------------------------------------------------------------------
>
>                 Key: IMPALA-14419
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14419
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Steve Carlin
>            Priority: Major
>
> The IntersectToDistinctRule is needed to change the LogicalIntersect RelNode into a RelNode that Impala can understand.  This Calcite v1.37 version of this rule worked fine with Impala.
> On upgrade to v1.40, the rule stopped working.  This is because it adds a COUNT() FILTER function which has issues that need further investigating.
> Since the rule works fine for 1.37 and it was just an optimization that was added, we can continue to use the 1.37 rule until the problem is fixed.  A Jira will be filed for enabling the 1.40 rule to work.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)