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

ASF GitHub Bot commented on HIVE-12698:
---------------------------------------

GitHub user thejasmn opened a pull request:

    https://github.com/apache/hive/pull/58

    HIVE-12698 : introduce HiveAuthorizationTranslator interface for isolating 
authori…

    …zation impls from hive internal classes

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/thejasmn/hive HIVE-12698

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/58.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #58
    
----
commit 27e73f2a45aa3e5a158c14fb0693567158cef0d7
Author: Thejas Nair <the...@hortonworks.com>
Date:   2015-12-17T02:36:52Z

    introduce HiveAuthorizationTranslator interface for isolating authorization 
impls from hive internal classes

----


> Remove exposure to internal privilege and principal classes in HiveAuthorizer
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-12698
>                 URL: https://issues.apache.org/jira/browse/HIVE-12698
>             Project: Hive
>          Issue Type: Bug
>          Components: Authorization
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 1.3.0, 2.0.0
>
>
> The changes in HIVE-11179 expose several internal classes to 
> HiveAuthorization implementations. These include PrivilegeObjectDesc, 
> PrivilegeDesc, PrincipalDesc and AuthorizationUtils.
> We should avoid exposing that to all Authorization implementations, but also 
> make the ability to customize the mapping of internal classes to the public 
> api classes possible for Apache Sentry (incubating).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to