hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-6629) Change SET ROLE NONE to SET ROLE ALL
Date Fri, 14 Mar 2014 19:16:46 GMT

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

Brock Noland commented on HIVE-6629:
------------------------------------

[~thejas] since the queue is backed up, I tested this with our internal cluster.  Results
below. Those two tests are unrelated. If that is acceptable to you we can commit. I understand
if you'd prefer to use the precommit testing environment results.

{noformat}
2014-03-14 12:12:54,863 (main) [ERROR - ptest.execution.PTest] Test run exited with an unexpected
error
org.apache.hive.ptest.execution.TestsFailedException: 2 tests failed
	at org.apache.hive.ptest.execution.PTest.run(PTest.java:172)
	at org.apache.hive.ptest.execution.PTest.main(PTest.java:351)
2014-03-14 12:12:54,864 (main) [WARN - ptest.execution.PTest] 2 failed tests
2014-03-14 12:12:54,865 (main) [WARN - ptest.execution.PTest] org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_union_top_level
2014-03-14 12:12:54,865 (main) [WARN - ptest.execution.PTest] org.apache.hive.service.cli.thrift.TestThriftHttpCLIService.testExecuteStatementAsync
2014-03-14 12:12:54,865 (main) [INFO - ptest.execution.PTest] Executed 5370 tests
{noformat}

> 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