snazy commented on PR #1899: URL: https://github.com/apache/polaris/pull/1899#issuecomment-3052235252
> For storage config, the service identity isn't assigned by Polaris itself, it's provided by users via the CreateCatalogRequest. That's why I have this proposal to fix this issue. Also, the storage integration is currently created within the persistence layer: [TransactionalMetaStoreManagerImpl.java#L972-L978](https://github.com/apache/polaris/blob/main/polaris-core/src/main/java/org/apache/polaris/core/persistence/transactional/TransactionalMetaStoreManagerImpl.java#L972-L978). > That's why I was leaning toward assigning the service identity in the persistence layer. This tight coupling of the persistence concerns with object storage concerns frightens me for quite a while. I propose to remove this unnecessary tight coupling first, which then, according to your statement, eliminates the whole need for this "transformation system". You can then have/configure dedicated services/indirection to do what you need to do. -- 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: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
