Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
db_policy_store
-
None
-
None
Description
The privilegeName column in the Privilege table was initially created to enforce uniqueness of Privileges with same server+db+table+uri+action. This can be done using composite unique key constraint in the underlying db.
It would also cleanup the Sentry Store codebase a bit..
Attachments
Attachments
Issue Links
- is depended upon by
-
SENTRY-340 Database implement for "with grant option"
- Resolved
- is duplicated by
-
SENTRY-148 Remove privilege name from TSentryPrivilege
- Resolved
- relates to
-
SENTRY-500 1.4 to 1.5 upgrade needs to handle empty strings with __NULL__
- Resolved
-
SENTRY-372 Clean-up MSentryPrivilege constructor to ensure __NULL__ values are handled consistently
- Open
- links to