[HIVE-12630] Import should create a new WriteEntity for the new table it's creating to mimic CREATETABLE behaviour

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.0, 1.3.0, 2.0.0, 2.1.0
• Component/s: Authorization, Import/Export
• Assignee: Sushanth Sowmyan
• Reporter: Sushanth Sowmyan
• Created: 09/Dec/15 18:15
• Updated: 09/Dec/15 18:18

Description

CREATE-TABLE creates a new WriteEntity for the new table being created, whereas IMPORT does not mimic that behaviour.

While SQLStandardAuth itself does not care about this difference, external Authorizers, as with Ranger can and do make a distinction on this, and can have policies set up on patterns for objects that do not yet exist. Thus, we must emit a WriteEntity for the yet-to-be-created table as well.

Issue Links

• relates to: RANGER-772 Hive plugin: Update Ranger authorizer to mimic changes made by Hive standard authorizer for the case when IMPORT can end up creating a table
• relates to: HIVE-11988 [hive] security issue with hive & ranger for import table command