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-6629) Change SET ROLE NONE to SET ROLE ALL
Date Fri, 14 Mar 2014 21:04:49 GMT

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

Hive QA commented on HIVE-6629:
-------------------------------



{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/12634455/HIVE-6629.patch

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5397 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_auto_sortmerge_join_16
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_bucketizedhiveinputformat
{noformat}

Test results: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1776/testReport
Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1776/console

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: 12634455

> Change SET ROLE NONE to SET ROLE ALL
> ------------------------------------
>
>                 Key: HIVE-6629
>                 URL: https://issues.apache.org/jira/browse/HIVE-6629
>             Project: Hive
>          Issue Type: Task
>    Affects Versions: 0.13.0
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>            Priority: Blocker
>             Fix For: 0.13.0
>
>         Attachments: HIVE-6629.patch, HIVE-6629.patch
>
>
> I understand this is well after it's been implemented. However, I think we need to discuss
the counter-intuitive SET ROLE semantics before we release 0.13.
> The new Hive Authz work implements "SET ROLE NONE" similar to MySQL meaning that "SET
ROLE NONE" actually sets your role to the default. This is extremely counter-intuitive.
> * [Oracle|http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_10004.htm]

> * [Informix|http://pic.dhe.ibm.com/infocenter/idshelp/v117/index.jsp?topic=%2Fcom.ibm.sqls.doc%2Fids_sqs_1186.htm]
> * [Vertica|https://my.vertica.com/docs/5.1.6/HTML/index.htm#15645.htm]
> * [SAP|http://www.sapdb.org/htmhelp/44/a17998442911d3a98200a0c9449261/content.htm]
> All of the widely deployed databases above have "SET ROLE NONE" disable all privileges.
Those databases have the intuitive "SET ROLE ALL" or "SET ROLE DEFAULT" enable all privileges.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message