[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties

[Qiang Zhang (JIRA)]

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

Qiang Zhang commented on RANGER-689:


+1

> For Solr plugin, use resources folders for adding Ranger properties
> ---
>
> Key: RANGER-689
> URL: https://issues.apache.org/jira/browse/RANGER-689
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Affects Versions: 0.5.0
>Reporter: Don Bosco Durai
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch
>
>
> Currently, the jars required by Ranger are added to WEB-INF/lib and 
> WEB-INF/classes folders. However, Solr recommends to put all extension jars 
> in server/lib/ext and properties in server/resources
> We should update out plugin installer code to use the new location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties

[peng.jianhua (JIRA)]

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

peng.jianhua commented on RANGER-689:
-

+1

> For Solr plugin, use resources folders for adding Ranger properties
> ---
>
> Key: RANGER-689
> URL: https://issues.apache.org/jira/browse/RANGER-689
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Affects Versions: 0.5.0
>Reporter: Don Bosco Durai
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch
>
>
> Currently, the jars required by Ranger are added to WEB-INF/lib and 
> WEB-INF/classes folders. However, Solr recommends to put all extension jars 
> in server/lib/ext and properties in server/resources
> We should update out plugin installer code to use the new location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (RANGER-1947) RangerHivePlugin does not authorize location on INSERT OVERWRITE DIRECTORY query

[Jake Moon (JIRA)]

Jake Moon created RANGER-1947:
-

 Summary: RangerHivePlugin does not authorize location on INSERT 
OVERWRITE DIRECTORY query
 Key: RANGER-1947
 URL: https://issues.apache.org/jira/browse/RANGER-1947
 Project: Ranger
  Issue Type: Bug
  Components: plugins
Affects Versions: 0.7.1
 Environment: hadoop 2.7.5 + hive 2.3.2 + ranger 0.7.1
Reporter: Jake Moon


{code}
insert overwrite directory '/user/user1/nonewrite3'
ROW FORMAT DELIMITED 
FIELDS TERMINATED BY ','
SELECT u.id, u.age, u.city, c.city
FROM user_table  u JOIN city_table c ON (u.city = c.code)
WHERE u.age > 25
AND u.age <= 28
AND c.city = 'New York'
{code}

This query's hive operation type is HiveOperationType.QUERY, and also have a 
write location to 'hdfs://my.cluster/user/user1/nonewrite3'

RangerHiveAuthorizer must authorize the location, but 
getURIAccessType(HiveOperationType.QUERY) always return FsAction.NONE, so it's 
not work.

If hive-server2 have enough permission on hdfs with no impersonation, every 
user can format hdfs like this.
{code}
insert overwrite directory '/'
ROW FORMAT DELIMITED 
FIELDS TERMINATED BY ','
SELECT 1
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Hadoop 3 support

[Abhay Kulkarni]

All,

Here is another proposal for Ranger release 1.0.0.

Atlas team is planning to make a Atlas-0.8.2 release towards the end of
this month. Once that is done, Ranger can do release 1.0.0 with dependency
on Atlas 0.8.2 (without Hadoop 3.0.0).

Thanks,
-Abhay

On 1/8/18, 12:23 PM, "Velmurugan Periasamy"  wrote:

>+1 for getting the 1.0.0 release out soon.
>
>From:  Colm O hEigeartaigh 
>Reply-To:  "dev@ranger.apache.org" ,
>"cohei...@apache.org" 
>Date:  Monday, January 8, 2018 at 12:37 PM
>To:  Ramesh Mani 
>Cc:  "dev@ranger.apache.org" 
>Subject:  Re: Hadoop 3 support
>
>OK thanks. I will test the patch a bit more thoroughly before submitting
>for a RR.
>
>Just in regards as to whether to release 1.0.0 with or without Hadoop
>3.0.0...currently we have a dependency on Atlas 1.0.0-SNAPSHOT. What's the
>timeline for releasing this? That would be the only thing blocking getting
>a 1.0.0 of Ranger out "quickly". If that's not imminent then I guess that
>gives us the time to get Ranger 1.0.0 out with Hadoop 3.0.0 support.
>
>However, it's been ages since the last release so we should probably not
>wait too long before getting a release out.
>
>Colm.
>
>On Fri, Jan 5, 2018 at 6:39 PM, Ramesh Mani  wrote:
>
>>  Thanks Colm,
>> 
>>  I am fine with Option 1 or 3.  Do you want to create a RR for this
>>patch?
>> 
>>  Thanks,
>>  Ramesh
>> 
>>  From: Colm O hEigeartaigh 
>>  Reply-To: "cohei...@apache.org" 
>>  Date: Friday, January 5, 2018 at 4:19 AM
>>  To: Ramesh Mani 
>>  Cc: "dev@ranger.apache.org" 
>>  Subject: Re: Hadoop 3 support
>> 
>>  I should have added - a third option is just not to support Hadoop
>>3.0.0
>>  at all in Ranger 1.0.0 - but to release Ranger 1.0.0 soon and then
>>update
>>  to Hadoop 3.0.0 in Ranger 1.1/2.0 etc.
>> 
>>  Colm.
>> 
>>  On Fri, Jan 5, 2018 at 12:17 PM, Colm O hEigeartaigh
>>
>>  wrote:
>> 
>>>  Hi Ramesh,
>>> 
>>>  Yes, the Ranger core will depend on Hadoop 3.0.0, and the HDFS + Yarn
>>>  plugins will support Hadoop 3.0.0 only. There is no other option due
>>>to API
>>>  changes. A user can use the earlier plugins from 0.7.x if support for
>>>  Hadoop 2.7.x is required.
>>> 
>>>  I am not really tied to this approach though - I'm also fine with just
>>>  having new plugins to support Hadoop 3.0.0 and Yarn 3.0.0. The
>>>approach to
>>>  update all of Ranger to use Hadoop 3.0.0 was based on the comments on
>>>this
>>>  JIRA:
>>> 
>>>  https://issues.apache.org/jira/browse/RANGER-1738
>>> 
>>>  Colm.
>>> 
>>>  On Fri, Jan 5, 2018 at 12:55 AM, Ramesh Mani 
>>>  wrote:
>>> 
  Colm,
 
  Is this proposal is to have Ranger 1.0.0 support Hadoop 3.0.0 only?
 
  Thanks.
  Ramesh
 
 
 
  On 1/4/18, 9:32 AM, "Colm O hEigeartaigh" 
wrote:
 
>  >Hi Ranger devs,
>  >
>  >I posted an initial patch here to bump Ranger up to use Hadoop
>3.0.0:
>  >
>  >https://issues.apache.org/jira/browse/RANGER-1935
>  >
>  >I would appreciate some initial feedback before proceeding further
>with
>  >testing it (just a general "looks ok" or "this would be problematic
>  >because
>  >X").
>  >
>  >Colm.
>  >
>  >
>  >--
>  >Colm O hEigeartaigh
>  >
>  >Talend Community Coder
>  >http://coders.talend.com
 
 
>>> 
>>> 
>>>  --
>>>  Colm O hEigeartaigh
>>> 
>>>  Talend Community Coder
>>>  http://coders.talend.com
>>> 
>> 
>> 
>> 
>>  --
>>  Colm O hEigeartaigh
>> 
>>  Talend Community Coder
>>  http://coders.talend.com
>> 
>
>
>
>-- 
>Colm O hEigeartaigh
>
>Talend Community Coder
>http://coders.talend.com
>
>
>

Re: Hadoop 3 support

[Velmurugan Periasamy]

+1 for getting the 1.0.0 release out soon.

From:  Colm O hEigeartaigh 
Reply-To:  "dev@ranger.apache.org" ,
"cohei...@apache.org" 
Date:  Monday, January 8, 2018 at 12:37 PM
To:  Ramesh Mani 
Cc:  "dev@ranger.apache.org" 
Subject:  Re: Hadoop 3 support

OK thanks. I will test the patch a bit more thoroughly before submitting
for a RR.

Just in regards as to whether to release 1.0.0 with or without Hadoop
3.0.0...currently we have a dependency on Atlas 1.0.0-SNAPSHOT. What's the
timeline for releasing this? That would be the only thing blocking getting
a 1.0.0 of Ranger out "quickly". If that's not imminent then I guess that
gives us the time to get Ranger 1.0.0 out with Hadoop 3.0.0 support.

However, it's been ages since the last release so we should probably not
wait too long before getting a release out.

Colm.

On Fri, Jan 5, 2018 at 6:39 PM, Ramesh Mani  wrote:

>  Thanks Colm,
> 
>  I am fine with Option 1 or 3.  Do you want to create a RR for this patch?
> 
>  Thanks,
>  Ramesh
> 
>  From: Colm O hEigeartaigh 
>  Reply-To: "cohei...@apache.org" 
>  Date: Friday, January 5, 2018 at 4:19 AM
>  To: Ramesh Mani 
>  Cc: "dev@ranger.apache.org" 
>  Subject: Re: Hadoop 3 support
> 
>  I should have added - a third option is just not to support Hadoop 3.0.0
>  at all in Ranger 1.0.0 - but to release Ranger 1.0.0 soon and then update
>  to Hadoop 3.0.0 in Ranger 1.1/2.0 etc.
> 
>  Colm.
> 
>  On Fri, Jan 5, 2018 at 12:17 PM, Colm O hEigeartaigh 
>  wrote:
> 
>>  Hi Ramesh,
>> 
>>  Yes, the Ranger core will depend on Hadoop 3.0.0, and the HDFS + Yarn
>>  plugins will support Hadoop 3.0.0 only. There is no other option due to API
>>  changes. A user can use the earlier plugins from 0.7.x if support for
>>  Hadoop 2.7.x is required.
>> 
>>  I am not really tied to this approach though - I'm also fine with just
>>  having new plugins to support Hadoop 3.0.0 and Yarn 3.0.0. The approach to
>>  update all of Ranger to use Hadoop 3.0.0 was based on the comments on this
>>  JIRA:
>> 
>>  https://issues.apache.org/jira/browse/RANGER-1738
>> 
>>  Colm.
>> 
>>  On Fri, Jan 5, 2018 at 12:55 AM, Ramesh Mani 
>>  wrote:
>> 
>>>  Colm,
>>> 
>>>  Is this proposal is to have Ranger 1.0.0 support Hadoop 3.0.0 only?
>>> 
>>>  Thanks.
>>>  Ramesh
>>> 
>>> 
>>> 
>>>  On 1/4/18, 9:32 AM, "Colm O hEigeartaigh"  wrote:
>>> 
  >Hi Ranger devs,
  >
  >I posted an initial patch here to bump Ranger up to use Hadoop 3.0.0:
  >
  >https://issues.apache.org/jira/browse/RANGER-1935
  >
  >I would appreciate some initial feedback before proceeding further with
  >testing it (just a general "looks ok" or "this would be problematic
  >because
  >X").
  >
  >Colm.
  >
  >
  >--
  >Colm O hEigeartaigh
  >
  >Talend Community Coder
  >http://coders.talend.com
>>> 
>>> 
>> 
>> 
>>  --
>>  Colm O hEigeartaigh
>> 
>>  Talend Community Coder
>>  http://coders.talend.com
>> 
> 
> 
> 
>  --
>  Colm O hEigeartaigh
> 
>  Talend Community Coder
>  http://coders.talend.com
> 



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties

[Ramesh Mani (JIRA)]

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

Ramesh Mani commented on RANGER-689:


I have verified this
+1
Thanks,
Ramesh

> For Solr plugin, use resources folders for adding Ranger properties
> ---
>
> Key: RANGER-689
> URL: https://issues.apache.org/jira/browse/RANGER-689
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Affects Versions: 0.5.0
>Reporter: Don Bosco Durai
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch
>
>
> Currently, the jars required by Ranger are added to WEB-INF/lib and 
> WEB-INF/classes folders. However, Solr recommends to put all extension jars 
> in server/lib/ext and properties in server/resources
> We should update out plugin installer code to use the new location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-689:


Thanks for the testing the patch...I still need a +1 from a Ranger committer 
though.

> For Solr plugin, use resources folders for adding Ranger properties
> ---
>
> Key: RANGER-689
> URL: https://issues.apache.org/jira/browse/RANGER-689
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Affects Versions: 0.5.0
>Reporter: Don Bosco Durai
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch
>
>
> Currently, the jars required by Ranger are added to WEB-INF/lib and 
> WEB-INF/classes folders. However, Solr recommends to put all extension jars 
> in server/lib/ext and properties in server/resources
> We should update out plugin installer code to use the new location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Hadoop 3 support

[Colm O hEigeartaigh]

OK thanks. I will test the patch a bit more thoroughly before submitting
for a RR.

Just in regards as to whether to release 1.0.0 with or without Hadoop
3.0.0...currently we have a dependency on Atlas 1.0.0-SNAPSHOT. What's the
timeline for releasing this? That would be the only thing blocking getting
a 1.0.0 of Ranger out "quickly". If that's not imminent then I guess that
gives us the time to get Ranger 1.0.0 out with Hadoop 3.0.0 support.

However, it's been ages since the last release so we should probably not
wait too long before getting a release out.

Colm.

On Fri, Jan 5, 2018 at 6:39 PM, Ramesh Mani  wrote:

> Thanks Colm,
>
> I am fine with Option 1 or 3.  Do you want to create a RR for this patch?
>
> Thanks,
> Ramesh
>
> From: Colm O hEigeartaigh 
> Reply-To: "cohei...@apache.org" 
> Date: Friday, January 5, 2018 at 4:19 AM
> To: Ramesh Mani 
> Cc: "dev@ranger.apache.org" 
> Subject: Re: Hadoop 3 support
>
> I should have added - a third option is just not to support Hadoop 3.0.0
> at all in Ranger 1.0.0 - but to release Ranger 1.0.0 soon and then update
> to Hadoop 3.0.0 in Ranger 1.1/2.0 etc.
>
> Colm.
>
> On Fri, Jan 5, 2018 at 12:17 PM, Colm O hEigeartaigh 
> wrote:
>
>> Hi Ramesh,
>>
>> Yes, the Ranger core will depend on Hadoop 3.0.0, and the HDFS + Yarn
>> plugins will support Hadoop 3.0.0 only. There is no other option due to API
>> changes. A user can use the earlier plugins from 0.7.x if support for
>> Hadoop 2.7.x is required.
>>
>> I am not really tied to this approach though - I'm also fine with just
>> having new plugins to support Hadoop 3.0.0 and Yarn 3.0.0. The approach to
>> update all of Ranger to use Hadoop 3.0.0 was based on the comments on this
>> JIRA:
>>
>> https://issues.apache.org/jira/browse/RANGER-1738
>>
>> Colm.
>>
>> On Fri, Jan 5, 2018 at 12:55 AM, Ramesh Mani 
>> wrote:
>>
>>> Colm,
>>>
>>> Is this proposal is to have Ranger 1.0.0 support Hadoop 3.0.0 only?
>>>
>>> Thanks.
>>> Ramesh
>>>
>>>
>>>
>>> On 1/4/18, 9:32 AM, "Colm O hEigeartaigh"  wrote:
>>>
>>> >Hi Ranger devs,
>>> >
>>> >I posted an initial patch here to bump Ranger up to use Hadoop 3.0.0:
>>> >
>>> >https://issues.apache.org/jira/browse/RANGER-1935
>>> >
>>> >I would appreciate some initial feedback before proceeding further with
>>> >testing it (just a general "looks ok" or "this would be problematic
>>> >because
>>> >X").
>>> >
>>> >Colm.
>>> >
>>> >
>>> >--
>>> >Colm O hEigeartaigh
>>> >
>>> >Talend Community Coder
>>> >http://coders.talend.com
>>>
>>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties

[Vishal Suvagia (JIRA)]

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

Vishal Suvagia commented on RANGER-689:
---

Tested and verified the above patch.Looks good to me +1.

> For Solr plugin, use resources folders for adding Ranger properties
> ---
>
> Key: RANGER-689
> URL: https://issues.apache.org/jira/browse/RANGER-689
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Affects Versions: 0.5.0
>Reporter: Don Bosco Durai
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch
>
>
> Currently, the jars required by Ranger are added to WEB-INF/lib and 
> WEB-INF/classes folders. However, Solr recommends to put all extension jars 
> in server/lib/ext and properties in server/resources
> We should update out plugin installer code to use the new location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)