[
https://issues.apache.org/jira/browse/HIVE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831381#comment-13831381
]
Hive QA commented on HIVE-4741:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12615539/HIVE-4714.2.patch.txt
{color:green}SUCCESS:{color} +1 4687 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/433/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/433/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.
ATTACHMENT ID: 12615539
> 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-4714.2.patch.txt, 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)
