collado-mike commented on PR #193: URL: https://github.com/apache/polaris/pull/193#issuecomment-2307419307
> The solution in Nessie to the "object-storage layout problem" is: If write.object-storage.enabled == true, then we return the "right" write.data.path value for the table's location (and remove the deprecated properties). By "right" `write.data.path`, you mean still under `catalog_root/namespace/table_dir`? That's specifically what this change is avoiding. If a catalog specifically declares `ALLOW_UNSTRUCTURED_TABLE_LOCATION`, we can allow any table location under the catalog root so that if there are many tables, writes and reads can be distributed (somewhat) evenly across the bucket. But setting that configuration is the admin's way of telling us they care more about the even distribution than they do scoped credential vending. A user _should_ be able to set the `write.data.path` to something within the table's subdirectory without setting `ALLOW_UNSTRUCTURED_TABLE_LOCATION` and I think they'll get what you described - object-storage layout scoped to within the table's subdirectory so that credential vending is still sub-scoped to the table. I can add a test to verify that use case. -- 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]
