singhpk234 commented on PR #13225: URL: https://github.com/apache/iceberg/pull/13225#issuecomment-5079169541
Hey (@smaheshwar-pltr @ggershinsky @xanderbailey @szlta @huaxingao ), Revisiting this PR again, I wanted to make sure this working group is aligned completely next steps. Background : As as i stated my stance [here](https://github.com/apache/iceberg/pull/13225#issuecomment-4372653091) I am effectively +0 for this in its current state, I also raised this in the catalog community sync [here](https://youtu.be/OaeTob3lM1Q) and with the discussion it came up if there is use case for this Frankenstein mode, we should support, i am really looking forward to use case, but i feel hive catalog is not the right precedence to follow ([here](https://docs.google.com/document/d/1VSewbVmjukU5eTiZruCJVmUZcRZvcAsd4JOeC6Lt3fo/edit?disco=AAAB_OHeuQc)) . In the meanwhile (@szlta proposed the spec extension which https://docs.google.com/document/d/1VSewbVmjukU5eTiZruCJVmUZcRZvcAsd4JOeC6Lt3fo/edit?tab=t.0 along with @ggershinsky) we discussed a lot about what use case being solved Current State : There is a [REST catalog spec proposal](https://github.com/apache/iceberg/pull/17155) out there, which enhance REST spec to give KMS creds, and at least it feels like for there is a concencus to use either only client side creds or server side creds ([here](https://docs.google.com/document/d/1VSewbVmjukU5eTiZruCJVmUZcRZvcAsd4JOeC6Lt3fo/edit?disco=AAAB_OHeuQc)) Question to the working group is, are you all ok with next steps ? do you have concrete use case for this PR, where we take server side vended creds for storage and client side creds for KMS, how do we proceed together in this. Thanks a ton for all your work / patience ! -- 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]
