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 "Quanlong Huang (Jira)" <ji...@apache.org> on 2024/08/14 00:49:00 UTC

[jira] [Updated] (IMPALA-13129) Hit DCHECK when skipping MIN_MAX runtime filter

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

Quanlong Huang updated IMPALA-13129:
------------------------------------
    Fix Version/s: Impala 4.4.1

> Hit DCHECK when skipping MIN_MAX runtime filter
> -----------------------------------------------
>
>                 Key: IMPALA-13129
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13129
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.4.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 4.5.0, Impala 4.4.1
>
>
> A [DCHECK in hdfs-scanner.h|https://github.com/apache/impala/blob/ce8078204e5995277f79e226e26fe8b9eaca408b/be/src/exec/hdfs-scanner.h#L199] is hit when skipping a MIN_MAX runtime filter using RUNTIME_FILTER_IDS_TO_SKIP query option. This is because during runtime filter generation, HdfsScanNode.tryToComputeOverlapPredicate() is called and register a 
> TOverlapPredicateDesc, but the minmax filter is then skipped later, causing backend to hit DCHECK.



--
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