[
https://issues.apache.org/jira/browse/HIVE-25222?focusedWorklogId=612469&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-612469
]
ASF GitHub Bot logged work on HIVE-25222:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Jun/21 07:15
Start Date: 21/Jun/21 07:15
Worklog Time Spent: 10m
Work Description: szlta merged pull request #2368:
URL: https://github.com/apache/hive/pull/2368
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 612469)
Time Spent: 0.5h (was: 20m)
> 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
> 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)
