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 "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2021/11/04 18:00:11 UTC
[jira] [Resolved] (IMPALA-10974) Impala cannot resolve columns of
converted Iceberg table
[ https://issues.apache.org/jira/browse/IMPALA-10974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltán Borók-Nagy resolved IMPALA-10974.
----------------------------------------
Fix Version/s: Impala 4.1.0
Resolution: Fixed
> Impala cannot resolve columns of converted Iceberg table
> --------------------------------------------------------
>
> Key: IMPALA-10974
> URL: https://issues.apache.org/jira/browse/IMPALA-10974
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: impala-iceberg
> Fix For: Impala 4.1.0
>
>
> When a regular Parquet/ORC table is converted to Iceberg via Hive, only the Iceberg metadata files need to be created. The data files can stay in place.
> This causes problems when the data files don't have field ids for the schema elements. Currently Impala resolves columns in data files based on Iceberg field ids, but since they are missing, Impala raises an error or returns NULLs.
> We could fallback to the default column resolution strategy when the data files lack field ids.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org