[
https://issues.apache.org/jira/browse/HIVE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894654#comment-13894654
]
Prasad Mujumdar commented on HIVE-4741:
---------------------------------------
This particular is not directly exposed to end users via SQL or configuration.
It fixes the way this restrict list configuration can be changed
programatically from a HiveServer2 session. It's only useful for custom hooks.
> Add Hive config API to modify the restrict list
> -----------------------------------------------
>
> Key: HIVE-4741
> URL: https://issues.apache.org/jira/browse/HIVE-4741
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 0.11.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Fix For: 0.13.0
>
> Attachments: HIVE-4714.2.patch.txt, HIVE-4741-1.patch
>
>
> HiveConf supports a restrict list configuration which is a black list of
> configurations that can be modified through the 'set x=y'. This is especially
> useful for HiveServer2 to restrict clients from overriding some of server
> configurations.
> Currently the restrict list value can't be changed after the HiveConf object
> is instantiated. It would be useful for custom code like Hooks to have a way
> to be able to update that setting.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
