[
https://issues.apache.org/jira/browse/HIVE-6844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960422#comment-13960422
]
Thejas M Nair commented on HIVE-6844:
-------------------------------------
Since the parameter has been used for both types of security, for backward
compatibility reasons, if old authorization interface is used, it will still be
enabled if hive.security.authorization.enabled=true.
> support separate configuration param for enabling authorization using new
> interface
> -----------------------------------------------------------------------------------
>
> Key: HIVE-6844
> URL: https://issues.apache.org/jira/browse/HIVE-6844
> Project: Hive
> Issue Type: Bug
> Components: Authorization
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
>
> The existing configuration parameter *hive.security.authorization.enabled* is
> used for both "SQL query level authorization" at sql query compilation, and
> at "metatore api authorization" for the thrift metastore api calls. This
> makes it hard to flexibly/correctly configure the security settings.
> It should be possible to enable "SQL query level authorization" and
> "metastore api authorization" independently of each other.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
