snazy commented on PR #193: URL: https://github.com/apache/polaris/pull/193#issuecomment-2306394001
We had to tackle the same problem (object-storage layout) in Nessie, but also wanted to retain the ability to control the table's location for data security reasons and generating IAM policies. Technically, there's sadly not only `write.(meta)data.path`, but also the (deprecated) `write.object-storage.path` and `write.folder-storage.path`. 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). Users only have to set `write.object-storage.enabled = true` and the catalog's doing the "right" thing. This way we can still generate IAM policies that are compatible to the object-storage layout. -- 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]
