[
https://issues.apache.org/jira/browse/HIVE-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069903#comment-14069903
]
Lefty Leverenz commented on HIVE-5923:
--------------------------------------
[~thejas], do the changes in the release note also apply to default Hive
authorization? (The wiki still shows ROLE and TABLE keywords.)
Also, while checking the Authorization doc for these changes I noticed a flaw
in the syntax for GRANT priv and REVOKE priv: they both say "ON object_type"
where object_type can be TABLE or DATABASE, but the name of the table or
database isn't in the syntax. Have I misunderstood, or does this need to be
fixed?
{code}
GRANT
priv_type [(column_list)]
[, priv_type [(column_list)]] ...
[ON object_type]
TO principal_specification [, principal_specification] ...
[WITH GRANT OPTION]
REVOKE [GRANT OPTION FOR]
priv_type [(column_list)]
[, priv_type [(column_list)]] ...
[ON object_type priv_level]
FROM principal_specification [, principal_specification] ...
object_type:
TABLE
| DATABASE
{code}
Of course, if this jira's changes don't apply to the default authorization then
this comment belongs somewhere else.
* [Authorization -- Grant/Revoke Privileges |
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Authorization#LanguageManualAuthorization-Grant/RevokePrivileges]
> SQL std auth - parser changes
> -----------------------------
>
> Key: HIVE-5923
> URL: https://issues.apache.org/jira/browse/HIVE-5923
> Project: Hive
> Issue Type: Sub-task
> Components: Authorization
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Fix For: 0.13.0
>
> Attachments: HIVE-5923.1.patch, HIVE-5923.2.patch, HIVE-5923.3.patch,
> HIVE-5923.4.patch
>
> Original Estimate: 96h
> Time Spent: 168h
> Remaining Estimate: 0h
>
> There are new access control statements proposed in the functional spec in
> HIVE-5837 . It also proposes some small changes to the existing query syntax
> (mostly extensions and some optional keywords).
> The syntax supported should depend on the current authorization mode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
