You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Steve Carlin (Jira)" <ji...@apache.org> on 2025/09/10 03:39:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=18019277#comment-18019277 ]
Steve Carlin commented on IMPALA-14419:
---------------------------------------
The Calcite issue added to v1.40 was described in this Jira: https://issues.apache.org/jira/browse/CALCITE-6893
The Impala follow-up Jira to fix the problem is IMPALA-14420
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org