[
https://issues.apache.org/jira/browse/IMPALA-12845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823560#comment-17823560
]
Daniel Becker commented on IMPALA-12845:
----------------------------------------
Hi [~laszlog] it is only related because it affects Iceberg metadata tables, I
actually noticed this bug when playing with metadata tables.
??a completely innocent user action can bring down an Impala cluster??
It may not be that bad because the crash is because of a DCHECK. I can check
what happens in release mode.
Anyway, this is under review: https://gerrit.cloudera.org/#/c/21105/
> Crash with DESCRIBE on a complex type from an Iceberg table
> -----------------------------------------------------------
>
> Key: IMPALA-12845
> URL: https://issues.apache.org/jira/browse/IMPALA-12845
> Project: IMPALA
> Issue Type: Bug
> Reporter: Daniel Becker
> Assignee: Daniel Becker
> Priority: Critical
>
> A DESCRIBE statement on a struct contained in an Iceberg table crashes Impala:
> In Hive:
> {code:java}
> create table ice_struct (id INT, s STRUCT<i: INT>) stored by iceberg;{code}
> In Impala:
> {code:java}
> describe ice_struct.s
> Caught exception TSocket read 0 bytes, type=<class
> 'thrift.transport.TTransport.TTransportException'> in FetchResults.
> Error communicating with impalad: TSocket read 0 bytes{code}
> The logs in impalad.FATAL indicate that we hit a DCHECK:
> {code:java}
> F0227 11:53:49.936864 680819 query-result-set.cc:386] Check failed: num_col
> == metadata_.columns.size() (3 vs. 4){code}
>
> Note that this also happens with Iceberg metadata tables, for example:
> {code:java}
> describe
> functional_parquet.iceberg_query_metadata.entries.readable_metrics;{code}
> With non-Iceberg tables there is no error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
