hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5048) StorageBasedAuthorization provider causes an NPE when asked to authorize from client side.
Date Thu, 15 Aug 2013 20:41:22 GMT


Hive QA commented on HIVE-5048:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 2859 tests executed
*Failed tests:*

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed

This message is automatically generated.
> StorageBasedAuthorization provider causes an NPE when asked to authorize from client
> ------------------------------------------------------------------------------------------
>                 Key: HIVE-5048
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Security
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>         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:

View raw message