[
https://issues.apache.org/jira/browse/HIVE-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065917#comment-14065917
]
Hive QA commented on HIVE-7361:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12656400/HIVE-7361.5.patch
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5744 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_ql_rewrite_gbtoidx
org.apache.hive.hcatalog.pig.TestHCatLoader.testReadDataPrimitiveTypes
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-Build/842/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-Build/842/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-Build-842/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12656400
> using authorization api for RESET, DFS, ADD, DELETE, COMPILE commands
> ---------------------------------------------------------------------
>
> Key: HIVE-7361
> URL: https://issues.apache.org/jira/browse/HIVE-7361
> Project: Hive
> Issue Type: Improvement
> Components: Authorization
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Labels: TODOC14
> Attachments: HIVE-7361.1.patch, HIVE-7361.2.patch, HIVE-7361.3.patch,
> HIVE-7361.4.patch, HIVE-7361.5.patch
>
>
> The only way to disable the commands SET, RESET, DFS, ADD, DELETE and COMPILE
> that is available currently is to use the hive.security.command.whitelist
> parameter.
> Some of these commands are disabled using this configuration parameter for
> security reasons when SQL standard authorization is enabled. However, it gets
> disabled in all cases.
> If authorization api is used authorize the use of these commands, it will
> give authorization implementations the flexibility to allow/disallow these
> commands based on user privileges.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
