travis-bowen opened a new pull request, #2697: URL: https://github.com/apache/polaris/pull/2697
This implements finer grained operations and privileges for update table in a backwards compatible way as discussed on the mailing list. (Seems the mailing list split the thread in two but it's [here](https://lists.apache.org/thread/19tjcs8j9b7mzk8l64p2xxv358t8vtq3) and [here](https://lists.apache.org/thread/vk0mtx0jjnr42szrqnk5b53f9l43dn87)) The design doc is [here](https://docs.google.com/document/d/1LRB0LDevc6EQa0NWiLHi-jKmrwNA_XXWiHKfskZ6VwU/edit?usp=sharing) The idea is that all the existing privileges and operations will work and continue to work even after this change. (i.e. TABLE_WRITE_PROPERTIES will still ensure update table is authorized even after these changes). However, because Polaris will now be able to identify each operation within an UpdateTable request and has a privilege model with inheritance that maps to each operation, users will now have the option of restricting permissions at a finer level if desired. -- 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]
