tanishq-chugh commented on PR #6257: URL: https://github.com/apache/hive/pull/6257#issuecomment-3713465165
Thanks for checking this @ayushtkn , and the concern is absolutely valid. As of now, there's no way to figure out the value once write is done and also, using different values at time of write/read will lead to data corruption. I am considering two options moving ahead. 1. Going ahead with modifying the UDF definition of it allowing a maximum of 3 arguments instead of session level config. 3rd argument being optional for this transformation value, with default to the current value. This is needed for backward compatibility. Figuring out the transformation value at the time of read, would still remain the user responsibility. (Query History could be of help here). 2. Figuring out the mode at time of decryption could be automated if we have only GCM & AES (default mode) options, as falling back to legacy mode could be an option when decryption runs into AEADBadTagException. Let me know your thoughts on this. -- 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]
