[
https://issues.apache.org/jira/browse/HIVE-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742223#comment-13742223
]
Hudson commented on HIVE-5048:
------------------------------
FAILURE: Integrated in Hive-trunk-hadoop1-ptest #129 (See
[https://builds.apache.org/job/Hive-trunk-hadoop1-ptest/129/])
HIVE-5048 : StorageBasedAuthorization provider causes an NPE when asked to
authorize from client side. (Sushanth Sowmyan via Ashutosh Chauhan) (hashutosh:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1514569)
*
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/security/authorization/HiveAuthorizationProviderBase.java
*
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/security/authorization/StorageBasedAuthorizationProvider.java
> StorageBasedAuthorization provider causes an NPE when asked to authorize from
> client side.
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-5048
> URL: https://issues.apache.org/jira/browse/HIVE-5048
> Project: Hive
> Issue Type: Bug
> Components: Security
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
> Fix For: 0.12.0
>
> Attachments: HIVE-5048.2.patch, HIVE-5048.patch
>
>
> StorageBasedAuthorizationProvider(henceforth referred to as SBAP) is a
> HiveMetastoreAuthorizationProvider (henceforth referred to as HMAP, and
> HiveAuthorizationProvider as HAP) that was introduced as part of HIVE-3705.
> As long as it's used as a HMAP, i.e. from the metastore-side, as was its
> initial implementation intent, everything's great. However, HMAP extends HAP,
> and there is no reason SBAP shouldn't be expected to work as a HAP as well.
> However, it uses a wh variable that is never initialized if it is called as a
> HAP, and hence, it will always fail when authorize is called on it.
> We should change SBAP so that it correctly initiazes wh so that it can be run
> as a HAP as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
