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 "Daniel Becker (Jira)" <ji...@apache.org> on 2024/08/05 07:20:00 UTC
[jira] [Assigned] (IMPALA-13272) Analyitic function of collections can lead to crash
[ https://issues.apache.org/jira/browse/IMPALA-13272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Becker reassigned IMPALA-13272:
--------------------------------------
Assignee: Daniel Becker
> Analyitic function of collections can lead to crash
> ---------------------------------------------------
>
> Key: IMPALA-13272
> URL: https://issues.apache.org/jira/browse/IMPALA-13272
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 4.4.0
> Reporter: Csaba Ringhofer
> Assignee: Daniel Becker
> Priority: Critical
>
> Using Impala's test data the following query leads to DCHECK in debug builds and may cause more subtle issues in RELEASE builds:
> {code}
> select
> row_no
> from (
> select
> arr.small,
> row_number() over (
> order by arr.inner_struct1.str) as row_no
> from functional_parquet.collection_struct_mix t, t.arr_contains_nested_struct arr
> ) res
> {code}
> The following DCHECK is hit:
> {code}
> tuple.h:296 Check failed: offset != -1
> {code}
> The problem seems to be with arr.small, which is referenced in the inline view, but not used in the outer query - removing it from the inline view or adding it to the outer select leads to avoiding the bug. The problem seems related to materialization - offset==-1 means that the slot is not materialized, but the Parquet scanner still tries to materialize it.
> It is not clear yet which commit introduced the bug or whether this is a bug in the planner or the backend.
--
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