danielcweeks commented on PR #5159: URL: https://github.com/apache/iceberg/pull/5159#issuecomment-1204289036
The concept of location ownership and catalog behaviors around it are something that I feel we need to be more specific about. While this may work for specific uses of HiveCatalog, it very likely wouldn't be consistent across catalog implementations and even has some potential side-effects (e.g. renamed tables may end up sharing location and result in dropping data incorrectly). These behaviors should really be owned by the Catalog (not the table) and should be tied to specific guarantees of the catalog implementation (i.e. de-conflicted/unique locations). I agree we want to be able to support this behavior, but I don't feel like this approach is comprehensive enough to address the problem. -- 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]
