hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-21753) Update HiveMetastore authorization to enable use of HiveAuthorizer implementation
Date Sat, 01 Jun 2019 16:37:01 GMT

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

Hive QA commented on HIVE-21753:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12970240/HIVE-21753.6.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/17390/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17390/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17390/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12970240/HIVE-21753.6.patch
was found in seen patch url's cache and a test was probably run already on it. Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12970240 - PreCommit-HIVE-Build

> Update HiveMetastore authorization to enable use of HiveAuthorizer implementation
> ---------------------------------------------------------------------------------
>
>                 Key: HIVE-21753
>                 URL: https://issues.apache.org/jira/browse/HIVE-21753
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 3.1.2
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>            Priority: Critical
>              Labels: pull-request-available
>         Attachments: HIVE-21753.1.patch, HIVE-21753.2.patch, HIVE-21753.3.patch, HIVE-21753.4.patch,
HIVE-21753.5.patch, HIVE-21753.6.patch
>
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
>
> Currently HMS supports authorization using StorageBasedAuthorizationProvider which relies
on permissions at filesystem – like HDFS. Hive supports a pluggable authorization interface,
and multiple authorizer implementations (like SQLStd, Ranger, Sentry) are available to authorizer
access in Hive. Extending HiveMetastore to use the same authorization interface as Hive will
enable use of pluggable authorization implementations; and will result in consistent authorization
across Hive, HMS and other services that use HMS (like Spark).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message