[jira] [Commented] (IMPALA-10466) Handle deprecated TWO_LEVEL Parquet arrays more gracefully

["Csaba Ringhofer (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-10466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711067#comment-17711067 ] 

Csaba Ringhofer commented on IMPALA-10466:
------------------------------------------

the behavior seems to be changed by IMPALA-9496, see
https://gerrit.cloudera.org/#/c/18596/7/testdata/workloads/functional-query/queries/QueryTest/parquet-ambiguous-list-legacy.test

> Handle deprecated TWO_LEVEL Parquet arrays more gracefully
> ----------------------------------------------------------
>
>                 Key: IMPALA-10466
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10466
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Csaba Ringhofer
>            Assignee: Csaba Ringhofer
>            Priority: Minor
>
> The default of PARQUET_ARRAY_RESOLUTION was changed from TWO_LEVEL_THEN_THREE_LEVEL to THREE_LEVEL in IMPALA-4725. This solved incorrectly detecting some ambiguous cases, but now old TWO_LEVEL Parquet lists are not read correctly by default, replacing values with NULL without any error message.
> I would prefer a solution that:
> a. detects the correct resolution when possible
> b. returns a clear warning/error when resolution is not possible or ambiguous, and points the user toward the query option that needs to be set manually



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