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

Ashutosh Chauhan commented on HIVE-5959:
----------------------------------------

I have created HIVE-6338 and have marked it for 0.13 Reason I don't want to 
make these  changes (which anyways don't serve purpose of this jira) is because 
I have set of jiras which are dependent on this one, like HIVE-5944 HIVE-5943 
HIVE-5952 

I am happy to make your suggested changes in different one. It might even make 
sense to scrub all of Hive code to spot on those kind of incorrect exception 
handling and fix them.

> SQL std auth - bootstrap SUPERUSER, PUBLIC roles
> ------------------------------------------------
>
>                 Key: HIVE-5959
>                 URL: https://issues.apache.org/jira/browse/HIVE-5959
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Authorization
>            Reporter: Thejas M Nair
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-5959.2.patch, HIVE-5959.3.patch, HIVE-5959.5.patch, 
> HIVE-5959.6.patch, HIVE-5959.7.patch, HIVE-5959.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> SUPERUSER and PUBLIC are two roles that are always present, these need to be 
> added automatically on metastore startup. This would be similar to creation 
> of the "default" database from HMSHandler.init().
> A config param in hive-site.xml will be used to specify the list of users who 
> belong to the SUPERUSER role.
>  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to