You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2013/10/14 21:48:42 UTC
[jira] [Commented] (HIVE-4741) Add Hive config API to modify the
restrict list
[ https://issues.apache.org/jira/browse/HIVE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794399#comment-13794399 ]
Brock Noland commented on HIVE-4741:
------------------------------------
[~prasadm], can you rebase this and submit with a name that works for HiveQA?
> 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
> Attachments: 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#6144)