[
https://issues.apache.org/jira/browse/HIVE-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984708#comment-13984708
]
Thejas M Nair commented on HIVE-6692:
-------------------------------------
Added comments to review board. The main concern is this needs some changes to
sql standard authorization to keep it working with this change. I can make that
change in SQL standard authorization - I didn't have a strong use case for
making that change. The workaround so far in SQL standard auth was to put the
URI and other database/table type in different Entity types.
[~navis] Is the change to use write entity for URI in these cases for intuitive
code or targeting further changes ? (Just trying to get a background of the
change, to understand how urgently I should make the changes to SQL standard
auth).
> Location for new table or partition should be a write entity
> ------------------------------------------------------------
>
> Key: HIVE-6692
> URL: https://issues.apache.org/jira/browse/HIVE-6692
> Project: Hive
> Issue Type: Task
> Components: Authorization
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-6692.1.patch.txt
>
>
> Locations for "create table" and "alter table add partition"should be write
> entities.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
