You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2019/10/08 22:52:56 UTC

[GitHub] [incubator-iceberg] jun-ma-0 commented on issue #491: Use relative path for manifest_path and file_path

jun-ma-0 commented on issue #491: Use relative path for manifest_path and file_path
URL: https://github.com/apache/incubator-iceberg/pull/491#issuecomment-539737143
 
 
   @ppadma and I discussed offline. We have some thoughts and would like to get feedback from the community.
   1) Make path relative to manifest instead of table. This approach can make two use cases happen
   a)avoid rebuilding metadata when migrating data from one table to another
   b) allow table data to exist in multiple locations. 
   2) Backward compatibility. We can have a relative path flag in manifest or table level to control whether relative path should be used or not. Making it on manifest level may provide more flexibility. It should default to false to ensure backward compatibility.
   3) Forward compatibility. To ensure this, it seems both absolute path and relative path have to be populated. It's redundant and can be difficult to keep both fields consistent depending on how users are making use of the table. Can we avoid populating both fields? That may mean relative path will not be forward compatible.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

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