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/01 22:13:27 UTC

[jira] [Updated] (HIVE-5400) Allow admins to disable compile and other commands

     [ https://issues.apache.org/jira/browse/HIVE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brock Noland updated HIVE-5400:
-------------------------------

    Attachment: HIVE-5400.patch

Attached is a patch which implements this for HS2 only. I think that makes sense as Admins will not be able to stop Hive CLI users from bypassing this mechanism anyway.

> Allow admins to disable compile and other commands
> --------------------------------------------------
>
>                 Key: HIVE-5400
>                 URL: https://issues.apache.org/jira/browse/HIVE-5400
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Brock Noland
>            Assignee: Edward Capriolo
>         Attachments: HIVE-5400.patch
>
>
> From here: https://issues.apache.org/jira/browse/HIVE-5253?focusedCommentId=13782220&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13782220
>  I think we should afford admins who want to disable this functionality the ability to do so. Since such admins might want to disable other commands such as add or dfs, it wouldn't be much trouble to allow them to do this as well. For example we could have a configuration option "hive.available.commands" (or similar) which specified add,set,delete,reset, etc by default. Then check this value in CommandProcessorFactory. It would probably make sense to add this property to the restrict list.



--
This message was sent by Atlassian JIRA
(v6.1#6144)