You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ádám Szita (Jira)" <ji...@apache.org> on 2021/06/21 07:17:00 UTC
[jira] [Resolved] (HIVE-25222) Fix reading Iceberg tables with a
comma in column names
[ https://issues.apache.org/jira/browse/HIVE-25222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ádám Szita resolved HIVE-25222.
-------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Committed to master. Thanks [~Marton Bod] for the fix, [~lpinter] and [~belugabehr] for the review.
> Fix reading Iceberg tables with a comma in column names
> -------------------------------------------------------
>
> Key: HIVE-25222
> URL: https://issues.apache.org/jira/browse/HIVE-25222
> Project: Hive
> Issue Type: Bug
> Reporter: Marton Bod
> Assignee: Marton Bod
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When using a table with a column name containing a comma (e.g. `employ,ee`), reading an Iceberg table fails because we rely on the property "hive.io.file.readcolumn.names" which encodes the read columns in a comma-separated list, put together by the ColumnProjectionUtils class.
> Because it's comma-separated in all cases, it will produce a string like: "id,birth_date,employ,ee" which can cause problems for Iceberg readers which use this string list to construct their expected read schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)