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


   I don't think it is a good idea in general to use relative paths. We 
recently had an issue where using a `hdfs` location without authority caused a 
user's data to be deleted by the `RemoveOrphanFiles` action because the 
resolution of the table root changed. The main problem is that places in 
Iceberg would need to have some idea of "equivalent" paths and path resolution. 
Full URIs are much easier to work with and more reliable.
   
   But there is still a way to do both. Catalogs and tables can inject their 
own `FileIO` implementation, which is what is used to open files. That can do 
any resolution that you want based on environment. So you could use an 
implementation that allows you to override a portion of the file URI and read 
it from a different underlying location. I think that works better overall 
because there are no mistakes about equivalent URIs, but you can still read a 
table copy without rewriting the metadata.


----------------------------------------------------------------
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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to