eric-maynard commented on issue #503: URL: https://github.com/apache/polaris/issues/503#issuecomment-2538352695
Agreed @mrcnc. The chief concern was that someone could have existing catalogs that overlap. Besides that, they may just have some business justification for overlapping catalogs. It's also important to point out that the restrictions against overlap do not provide ironclad guarantees as they stand. Even when catalogs are restricted s.t. they can't overlap, things you mentioned are already possible. Vended credentials can potentially read other data that is under a table's prefix. Two (EXTERNAL, by default IIRC) table locations can already overlap within a catalog. Given this, and given the fact that some early users told us they wanted the option to have overlapping catalog locations, we added that flag. -- 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]
