[IMPALA-7075] Add support for object ownership for Impala

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.1.0
• Component/s: Frontend
• Labels: security
• Epic Name: OO
• Epic Color: ghx-label-3
• Assignee: Fredy Wijaya
• Reporter: Fredy Wijaya
• Created: 25/May/18 16:04
• Updated: 19/Jun/20 19:09
• Resolved: 17/Oct/18 22:03

Description

Currently when creating a database or table, a user does not automatically get ALL privilege on that object even though that person owns the table/object. The purpose of this epic is to add a concept of ownership where a user will automatically be granted ALL on the database/table he/she owns.

Issue Links

• is duplicated by: IMPALA-2238 Impala doesn't set HUE end user as the owner when creating tables

Sub-Tasks

• Implement ALTER TABLE/VIEW SET OWNER: Resolved
• Implement SHOW GRANT USER: Resolved
• Implement SHOW GRANT ROLE/USER ON: Resolved
• Implement ALTER DATABASE SET OWNER: Resolved
• Update OWNER privilege on CREATE, DROP, and ALTER SET OWNER: Resolved
• Impala 2.13 & 3.1 Docs: ALTER TABLE / VIEW SET OWNER: Closed
• Set owner type upon table creation: Resolved
• Drop table/database should remove owner privileges: Resolved
• ALTER TABLE/DB SET OWNER should update user privileges: Resolved
• Initial refactor to support user-level privileges: Resolved
• Change Sentry proxy to use the bulk API: Resolved
• Restrict ALTER DATABASE/TABLE SET OWNER to ALL/OWNER privilege with GRANT OPTION enabled: Resolved
• Add the OWNER privilege: Resolved
• Update Sentry for object ownership feature: Resolved
• SHOW GRANT USER not showing all privileges: Resolved
• Add Sentry configuration to allow specific privileges to be granted explicitly: Resolved
• Impala 2.13 & 3.1 Docs: ALTER DATABASE SET OWNER: Closed