[
https://issues.apache.org/jira/browse/HIVE-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998097#comment-13998097
]
Thejas M Nair commented on HIVE-7061:
-------------------------------------
The top level operation type for insert queries can't change for this, as we
could have multiple inserts in a query, each with different behavior wrt
OVERWRITE.
WriteEntity will have to be enhanced to capture this information, to indicate
if it is going to be overwritten or appended. Semantic analyzer needs to
populate this information in the right places. The authorization mechanism has
to change to consider this additional information. Right now it is just a
mapping of Operation to Privileges required on input and output.
> sql std auth - insert queries without overwrite should not require delete
> privileges
> ------------------------------------------------------------------------------------
>
> Key: HIVE-7061
> URL: https://issues.apache.org/jira/browse/HIVE-7061
> Project: Hive
> Issue Type: Bug
> Components: Authorization, SQLStandardAuthorization
> Affects Versions: 0.13.0
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
>
> Insert queries can do the equivalent of delete and insert of all rows of a
> table or partition, if the overwrite keyword is used. As a result DELETE
> privilege is applicable to such queries.
> However, SQL Standard auth requires DELETE privilege even for queries that
> don't have the overwrite keyword.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
