[
https://issues.apache.org/jira/browse/HIVE-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739774#comment-13739774
]
Ashutosh Chauhan commented on HIVE-5048:
----------------------------------------
I think your checks are masking underlying problem. IMO correct fix for this is
that Warehouse should always be initialized. If it so happens that metastore is
up and warehouse isn't, thats illegal state, doesn't matter if calls are made
from client or server. This has been discussed before as well :
https://issues.apache.org/jira/browse/HIVE-2079?focusedCommentId=13104063&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13104063
> 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
> Attachments: 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
