hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-5400) Allow admins to disable compile and other commands
Date Thu, 03 Oct 2013 00:00:42 GMT

    [ https://issues.apache.org/jira/browse/HIVE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784657#comment-13784657
] 

Hive QA commented on HIVE-5400:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12606456/HIVE-5400.patch

{color:green}SUCCESS:{color} +1 4046 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1001/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1001/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

> 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, HIVE-5400.patch, 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)

Mime
View raw message