Details
-
Task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
0.13.0
-
None
-
None
Description
I understand this is well after it's been implemented. However, I think we need to discuss the counter-intuitive SET ROLE semantics before we release 0.13.
The new Hive Authz work implements "SET ROLE NONE" similar to MySQL meaning that "SET ROLE NONE" actually sets your role to the default. This is extremely counter-intuitive.
All of the widely deployed databases above have "SET ROLE NONE" disable all privileges. Those databases have the intuitive "SET ROLE ALL" or "SET ROLE DEFAULT" enable all privileges.