hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (HIVE-5400) Allow admins to disable compile and other commands
Date Wed, 02 Oct 2013 13:10:25 GMT


Edward Capriolo commented on HIVE-5400:

Well lets do this. Lets extend the Command interface class.

interface Command {
  public List<String> provides = { set, bla , bla }

Then lets let the CommandProcessorFactory look a the users session state, the hive conf, and
determine to give back a command or throw an exception.

This maye be harder then it sounds but it feels like a clean way to do it. This allows us
to plug in new commands without much hassle.

> Allow admins to disable compile and other commands
> --------------------------------------------------
>                 Key: HIVE-5400
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Brock Noland
>            Assignee: Edward Capriolo
>         Attachments: HIVE-5400.patch
> From here:
>  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

View raw message