anuragmantri commented on issue #1617:
URL: https://github.com/apache/iceberg/issues/1617#issuecomment-870115508
Thanks @rdblue for explaining how locations are tracked in Iceberg tables.
Based on your and @pvary's comments, I updated the design doc to include
- For HadoopTables
- The location passed to `HadoopTableOperations` will be used as base
table location.
- If metadata.json file contains a different `location`, we will ignore
it. (Do you see any issues?)
- For metastore tables
- For `HiveTable`
- We can use location property tracked in metastore as the base table
location.
OR
- We could just use `updateLocation()` API to create a new
metadata.json file and use the `location` attribute in that as base table
location.
- For other metastore tables
- For metastore tables that don't track table location, we can use
the `location` attribute of the metadata.json file as the base table location
- Path conversion is transparent to APIs. I removed sections of the doc that
refer to APIs that do not change.
What are your thoughts?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
