[jira] [Commented] (RANGER-1513) Add Support for S3 authorization in Ranger Hive Plugin

["Ramesh Mani (JIRA)" <ji...@apache.org>]

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

Ramesh Mani commented on RANGER-1513:
-------------------------------------

Master Commit link:
 http://git-wip-us.apache.org/repos/asf/ranger/commit/02f83498
 http://git-wip-us.apache.org/repos/asf/ranger/commit/13f01c82
ranger-0.7:
http://git-wip-us.apache.org/repos/asf/ranger/commit/2fabba3f


> Add Support for S3 authorization in Ranger Hive Plugin
> ------------------------------------------------------
>
>                 Key: RANGER-1513
>                 URL: https://issues.apache.org/jira/browse/RANGER-1513
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>    Affects Versions: master
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>             Fix For: master, 0.7.1
>
>         Attachments: s3.png
>
>
> Ranger Hive Plugin currently does authorization on the URI which are in Hive commands. 
> e.g
>  CREATE EXTERNAL TABLE .... LOCATION [URI];
>  LOAD DATA INPATH [URI] INTO TABLE ...;
> THE URIs in this commands would be HDFS uri and currently authorized by ranger.
> This URI can be in various hive commands like
> create database
> create table
> create function
> insert
> delete
> add jar
> add partition
> But in case if these URI is S3 it not authorized as hdfs doesn't have the api to do on this. This JIRA would provide a READ and WRITE permission to s3 URI via a new Ranger Hive Service URI resource. Attaching a screen shot on the same



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)