[GitHub] [iceberg] pvary commented on issue #1617: Support relative paths in Table Metadata

[GitBox <gi...@apache.org>]

pvary commented on issue #1617:
URL: https://github.com/apache/iceberg/issues/1617#issuecomment-878245863


   > @pvary, we can explore that, but it is fairly easy to write a new metadata file and use that for a table. At least that's a small operation, compared to rewriting all metadata and position delete files.
   
   @rdblue: I am not sure that I understand what are you proposing here. I might be mistaken, but AFAIK we store the locations of the files in the `snapshot` file, in the `manifest` files and also in v2  the `position delete` files as well. If we want to create a usable full copy of the table then currently we need to do the following:
   - Copy the data files
   - Recreate or parse and replace the path in all of the files mentioned above (`snapshot`, `manifest` files and `position delete` files)
   
   Is there an easier way to create a full working replica of an Iceberg table where we do not use any files/data from the original table and the 2 tables (original and the new) can live independently after the creation of the replica?
   
   > My main point is that we need to have a well-documented plan for tracking the table location.
   
   Totally agree with this 👍 
   
   Thanks,
   Peter


-- 
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: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org