[
https://issues.apache.org/jira/browse/HIVE-25871?focusedWorklogId=711404&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-711404
]
ASF GitHub Bot logged work on HIVE-25871:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jan/22 14:10
Start Date: 19/Jan/22 14:10
Worklog Time Spent: 10m
Work Description: pvary commented on pull request #2948:
URL: https://github.com/apache/hive/pull/2948#issuecomment-1016501611
> HiveSchemaConverter assigned field ids starting from 0, while Iceberg
assigns field ids starting from 1. This caused test failures because the name
mapping had wrong field ids. So in the second commit I fixed
HiveSchemaConverter as well.
If we provide a schema where the id is starting from 0, would that mean that
the schema is not correct? Or this is just to be more aligned with the way
Iceberg generates ids?
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 711404)
Time Spent: 40m (was: 0.5h)
> Hive should set name mapping table property for migrated Iceberg tables
> -----------------------------------------------------------------------
>
> Key: HIVE-25871
> URL: https://issues.apache.org/jira/browse/HIVE-25871
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Hive should set the name-mapping table property during table migration.
> It would be useful for [column
> projection|https://iceberg.apache.org/#spec/#column-projection] for files
> without field ids.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
