[ https://issues.apache.org/jira/browse/HIVE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783368#comment-13783368 ]
Edward Capriolo commented on HIVE-5400: --------------------------------------- Did not mean "hack in" in a bad way. But we do not want a lot of strings and have connect the dots between seemingly unrelated classes as to why a feature is working or not. > 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)