You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2022/07/06 08:19:00 UTC

[jira] [Resolved] (RANGER-768) Hive Metastore Plugin

     [ https://issues.apache.org/jira/browse/RANGER-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Mani resolved RANGER-768.
--------------------------------
    Fix Version/s: 2.1.0
         Assignee: Ramesh Mani
       Resolution: Fixed

This was implemented in https://issues.apache.org/jira/browse/HIVE-21753

> Hive Metastore Plugin
> ---------------------
>
>                 Key: RANGER-768
>                 URL: https://issues.apache.org/jira/browse/RANGER-768
>             Project: Ranger
>          Issue Type: New Feature
>          Components: admin, plugins
>            Reporter: Yan
>            Assignee: Ramesh Mani
>            Priority: Major
>             Fix For: 2.1.0
>
>         Attachments: Design Proposal for Hive Metastore Plugin of Ranger - V1.2.docx, Design Proposal for Hive Metastore Plugin of Ranger - V1.3.docx, Design Proposal for Hive Metastore Plugin of Ranger - V1.4.docx, Design Proposal for Hive Metastore Plugin of Ranger.docx, Design Proposal for Hive Metastore Plugin of Ranger.docx
>
>
> Currently there is no Ranger processing of Hive table meta store events that could result in privilege modifications. One example is that when a table is renamed by a Hive Server 2 client (the "beeline"), no proper privilege adjustments in Ranger are made to allow/deny previously allowed/denied users the same privileges as before. In addition, more advanced features, such as granting/denying similar accesses to Hive's HDFS data to users that have (or do not have) privileges in the Hive, would require that detailed metadata of the Hive table, the storage info to be specific, be available to Ranger in order to make the corresponding HDFS  data accessible to the Hive users directly.
> This plugin will depend upon the existing Ranger Hive plugin, so it shares the same "service" name as the associated Ranger Hive service deployed, and it will be "co-enabled" with the existing Ranger Hive plugin.
> Design doc will come soon.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)