[
https://issues.apache.org/jira/browse/HIVE-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618954#comment-14618954
]
Thejas M Nair commented on HIVE-11190:
--------------------------------------
I agree , it makes sense to update the description of the config param to say
that it is overridden with another value when authorization V2 is used.
Also, log a warning if user had set it to a non default value.
bq. About AuthorizationMetaStoreFilterHook, I found commandString didn't set to
HiveAuthzContext. Is it an issue? do you think I should open a ticket to fix it?
For calls that lead to the HiveAuthorizer.filterListCmdObjects , there will be
a call made to checkPrivileges as well, that call would have the command string
as well. I am not sure if there is a good way to get the commandstring in
AuthorizationMetaStoreFilterHook call (with current interface).
> ConfVars.METASTORE_FILTER_HOOK in authorization V2 should not be hard code
> when the value is not default
> --------------------------------------------------------------------------------------------------------
>
> Key: HIVE-11190
> URL: https://issues.apache.org/jira/browse/HIVE-11190
> Project: Hive
> Issue Type: Bug
> Reporter: Dapeng Sun
> Assignee: Dapeng Sun
> Attachments: HIVE-11190.001.patch
>
>
> ConfVars.METASTORE_FILTER_HOOK in authorization V2 should not be hard code
> when the value is not default.
> it will cause user failed to customize the METASTORE_FILTER_HOOK
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
