Review - Draft : Board Report for Ranger - period Ending 01/31/2017

[Selvamohan Neethiraj]

Rangers:

Please review the draft Board report below and let me know if you need to 
add/mod anything below ….

Thanks,
Selva-

==
# Description
The Ranger project is a framework to enable, monitor and manage 
comprehensive data security across the Hadoop platform.

# Issues
* Running into some JIRA permission issues for the past few days. Working 
with INFRA team (INFRA-13423)

# Status
* Graduation approved by board on Jan 18, 2017
* Working through tasks required of graduating projects
* Release Plan for Ranger 0.7.0 will be started soon.

# Releases
* ranger-0.6.3 released on 2017-01-30 (Fixed some of the key security 
issues)

# Development Activity
* Community is discussing the scope of next release
* Jira: 55(added), 66(resolved) (in the last 31 days)
* Git(Source): 75 commits over last 31 days
* SVN(Site & Docs): 5 commits over last 31 days

# Community Activity
## Membership Changes
* Added all committers to PMC list as part of the graduation (01-18-2017); 
Added (Alok Lal, Colm O hEigeartaigh, Gautam Borad)
* No new committers in the last 31 days.
* Gautam Borad was added as a committer on 06-29-2015
## Mailing List Activity
* user@ranger: 48 messages over last 31 days
* dev@ranger: 587 messages over last 31 days
* commits@ranger:  96 messages over last 31 days
==

Re: svn commit: r1781018 - in /incubator/ranger/site/trunk: download.html faq.html index.html issue-tracking.html license.html mail-lists.html project-info.html project-summary.html quick_start_guide.

[Selvamohan Neethiraj]

Thanks Colm, I will file an INFRA jira to get this fixed.

Selva-


On 1/31/17, 4:42 AM, "Colm O hEigeartaigh"  wrote:

It looks like there is something missing to link the repo:

https://dist.apache.org/repos/dist/release/ranger/

with the official Apache dist repo:

http://www.apache.org/dist/ranger

The latter throws a 404. We must not link to "https://dist.apache.org/
repos/dist/release/ranger/0.6.3/apache-ranger-0.6.3.tar.gz" for the main
release by the way, but to a mirror of "http://www.apache.org/dist/ranger;.
Could someone ask INFRA why "http://www.apache.org/dist/ranger; is not
available?

Colm.

-- Forwarded message --
From: 
Date: Tue, Jan 31, 2017 at 4:49 AM
Subject: svn commit: r1781018 - in /incubator/ranger/site/trunk:
download.html faq.html index.html issue-tracking.html license.html
mail-lists.html project-info.html project-summary.html
quick_start_guide.html team-list.html
To: comm...@ranger.apache.org


Author: vel
Date: Tue Jan 31 04:49:16 2017
New Revision: 1781018

URL: http://svn.apache.org/viewvc?rev=1781018=rev
Log:
Updating the docs with 0.6.3 release

Modified:
incubator/ranger/site/trunk/download.html
incubator/ranger/site/trunk/faq.html
incubator/ranger/site/trunk/index.html
incubator/ranger/site/trunk/issue-tracking.html
incubator/ranger/site/trunk/license.html
incubator/ranger/site/trunk/mail-lists.html
incubator/ranger/site/trunk/project-info.html
incubator/ranger/site/trunk/project-summary.html
incubator/ranger/site/trunk/quick_start_guide.html
incubator/ranger/site/trunk/team-list.html

Modified: incubator/ranger/site/trunk/download.html
URL: http://svn.apache.org/viewvc/incubator/ranger/site/trunk/
download.html?rev=1781018=1781017=1781018=diff

==
--- incubator/ranger/site/trunk/download.html (original)
+++ incubator/ranger/site/trunk/download.html Tue Jan 31 04:49:16 2017
@@ -193,6 +193,13 @@
   
 0.6.2
 
+
+  
+
+  https://cwiki.apache.
org/confluence/display/RANGER/Apache+Ranger+0.6.3+-+Release+Notes"
class="externalLink" title="0.6.3">
+  
+0.6.3
+
 


@@ -259,13 +266,13 @@ LICENSE.txt and NOTICE.txt files contain
 

 
-The current stable release is Apache Ranger 0.6.2:
+The current stable release is Apache Ranger 0.6.3:
 

 
-https://dist.apache.org/
repos/dist/release/ranger/0.6.2-incubating/apache-ranger-
incubating-0.6.2.tar.gz">apache-ranger-incubating-0.6.2.tar.gz
-(https://dist.apache.org/
repos/dist/release/ranger/0.6.2-incubating/apache-ranger-
incubating-0.6.2.tar.gz.asc">PGP)
-(https://dist.apache.org/
repos/dist/release/ranger/0.6.2-incubating/apache-ranger-
incubating-0.6.2.tar.gz.mds">Digests)
+https://dist.apache.org/
repos/dist/release/ranger/0.6.3/apache-ranger-0.6.3.tar.gz">
apache-ranger-0.6.3.tar.gz
+(https://dist.apache.org/
repos/dist/release/ranger/0.6.3/apache-ranger-0.6.3.tar.gz.asc">PGP)
+(https://dist.apache.org/
repos/dist/release/ranger/0.6.3/apache-ranger-0.6.3.tar.gz.mds">Digests)
 
 


Modified: incubator/ranger/site/trunk/faq.html
URL: http://svn.apache.org/viewvc/incubator/ranger/site/trunk/
faq.html?rev=1781018=1781017=1781018=diff

==
--- incubator/ranger/site/trunk/faq.html (original)
+++ incubator/ranger/site/trunk/faq.html Tue Jan 31 04:49:16 2017
@@ -193,6 +193,13 @@
   
 0.6.2
 
+
+  
+
+  https://cwiki.apache.
org/confluence/display/RANGER/Apache+Ranger+0.6.3+-+Release+Notes"
class="externalLink" title="0.6.3">
+  
+0.6.3
+
 



Modified: incubator/ranger/site/trunk/index.html
URL: http://svn.apache.org/viewvc/incubator/ranger/site/trunk/
index.html?rev=1781018=1781017=1781018=diff

==
--- incubator/ranger/site/trunk/index.html (original)
+++ incubator/ranger/site/trunk/index.html Tue Jan 31 04:49:16 2017
@@ -195,6 +195,13 @@
   
 0.6.2
 
+
+  
+
+  https://cwiki.apache.
org/confluence/display/RANGER/Apache+Ranger+0.6.3+-+Release+Notes"
class="externalLink" title="0.6.3">
+  
+0.6.3
+ 

Prep for ranger-0.7 release ...

[Selvamohan Neethiraj]

Rangers:

As we are planning to do a release of ranger 0.7 soon,  I would like to create 
a branch ranger-0.7 for stabilizing the release.
All of the fixes should go into the master which will track for our next major 
release (planning to call  it as 1.0.0 )  and if needed will get cherry-picked 
into ranger-0.7 release.

I am Volunteering  to be the release manager for ranger 0.7 release.

Please let me know if any of you have any concerns and/or suggestions  on the 
release process.

Thanks,
Selva-

Re: Moving GIT repo from Incubating to TLP

[Selvamohan Neethiraj]

FYI:

Just filed a ticket for moving Ranger Repo from Incubator to TLP - 
https://issues.apache.org/jira/browse/INFRA-13386

Thanks,
Selva-

From:  Selvamohan Neethiraj <sneet...@apache.org>
Date:  Tuesday, January 24, 2017 at 9:10 AM
To:  "d...@ranger.incubator.apache.org" <d...@ranger.incubator.apache.org>, 
<dev@ranger.apache.org>
Subject:  Moving GIT repo from Incubating to TLP

Congrats to all Rangers … As we have graduated to Top Level Project, we need to 
move our GIT repo moved 
>From  https://git-wip-us.apache.org/repos/asf/incubator-ranger.git  
   to   https://git-wip-us.apache.org/repos/asf/ranger.git

I am thinking of creating a INFRA ticket to move the repo in the next 8 hour 
and try to update some of the documents (release docs – that refers to 
incubation updated corrected)

Please let me know if this would cause any issues for your tasks …

Thanks,
Selva-

Problem in "Editing JIRA issue in Apache Ranger" - INFRA ticket open ....

[Selvamohan Neethiraj]

I saw few discussions related to permission for creation of public comments and 
assigning JIRA(s) to others. 

I have created a INFRA- lira to get this fixed.   
https://issues.apache.org/jira/browse/INFRA-13423

Please let me know if you have come across any other issues after we graduated 
to Top Level Project (TLP).

Thanks,
Selva-

Re: [VOTE] Release Apache Ranger 0.6.3 - release candidate 1 (dev group vote)

[Selvamohan Neethiraj]

+1 (binding)

Selva-

On 1/26/17, 3:50 PM, "Velmurugan Periasamy"  wrote:

Rangers:

Apache Ranger 0.6.3 release candidate #1 is now available for a vote within 
dev community. Links to release artifacts are given below. Could you please 
review and vote? Please note that this vote is being redone after Ranger has 
graduated from incubator to a TLP.

The vote will be open for at least 72 hours or until necessary number of 
votes are reached.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1

Thank you,
Vel

Git tag for the release:
  https://github.com/apache/ranger/tree/ranger-0.6.3-rc1  (last commit id : 
 bedbc4bda97b54113e166307596d8c62ce5d329f)
Sources for the release:
  
https://dist.apache.org/repos/dist/dev/ranger/0.6.3-rc1/apache-ranger-0.6.3.tar.gz

Source release verification:
PGP Signature:  
  
https://dist.apache.org/repos/dist/dev/ranger/0.6.3-rc1/apache-ranger-0.6.3.tar.gz.asc
 
MD5/SHA  Hash:
  
https://dist.apache.org/repos/dist/dev/ranger/0.6.3-rc1/apache-ranger-0.6.3.tar.gz.mds
 

Keys to verify the signature of the release artifact are available at:
  https://people.apache.org/keys/group/ranger.asc

Re: Rangers: Need help to move 9 open JIRA(s) to either RESOLVED state or move out to 1.0.0 version ....

[Selvamohan Neethiraj]

Rangers:

 

I have moved the following 7 JIRA(s) out of 0.7.0 release to fixVersion =  1.0.0

 

RANGER-1252

RANGER-1326

RANGER-1348

RANGER-1354

RANGER-1364

RANGER-1383

RANGER-1392

 

Thanks,

Selva-

 

From: Selvamohan Neethiraj <sneet...@apache.org>
Date: Monday, February 20, 2017 at 1:18 AM
To: <dev@ranger.apache.org>
Subject: Rangers: Need help to move 9 open JIRA(s) to either RESOLVED state or 
move out to 1.0.0 version 

 

Rangers:

 

As I am preparing for ranger-0.7.0  release, I still see 9 more open issues 
targeted for ranger 0.7 fix version. 

(JIRA Filter:  project = RANGER AND fixVersion = 0.7.0 AND resolution = 
Unresolved and type not in (Task) ORDER BY due ASC, priority DESC, created ASC)

Can you please review this list and move your assigned jira(s) to next release 
version 1.0.0 if you cannot resolve it in next 4 hours?  If it is not moved out 
(or resolved), I will have to move them to 1.0.0 release before sending the 
release for VOTE.

 

Just another FYI:  I have disabled the build.apache.org Jenkin Job that was 
publishing our 0.7.0-SNAPSHOT libraries to Apache (since we have changed the 
version to 0.7.0 and the release is not yet approved).

 

Thanks,

Selva-

Plan on kicking off release - ranger-0.7 release on Monday (02/20/2017)

[Selvamohan Neethiraj]

Just FYI:

I am planning to kick off the release of ranger-0.7 on Monday (02/20/2017).
I will review those patches that are requested to be merged to be ranger-0.7 
today and tomorrow and send out note to the dev list.

Thanks,
Selva-

From:  Selvamohan Neethiraj <sneet...@apache.org>
Date:  Wednesday, February 8, 2017 at 10:53 AM
To:  <dev@ranger.apache.org>
Subject:  Prep for ranger-0.7 release ...

Rangers:

As we are planning to do a release of ranger 0.7 soon,  I would like to create 
a branch ranger-0.7 for stabilizing the release.
All of the fixes should go into the master which will track for our next major 
release (planning to call  it as 1.0.0 )  and if needed will get cherry-picked 
into ranger-0.7 release.

I am Volunteering  to be the release manager for ranger 0.7 release.

Please let me know if any of you have any concerns and/or suggestions  on the 
release process.

Thanks,
Selva-

Re: Review Request 56829: Ranger-1395: LDAP group sync fails with InvalidNameException

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56829/#review166044
---



Can you please provide little more details on how the manual testing was done. 
This would be helpful for reviewer 

- Selvamohan Neethiraj


On Feb. 19, 2017, 5:30 p.m., Yan Zhou wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56829/
> ---
> 
> (Updated Feb. 19, 2017, 5:30 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Some LDAP servers throw exception on group search on posix user names that 
> are not full DNs.
> 
> 
> Diffs
> -
> 
>   
> ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapUserGroupBuilder.java
>  8cf6816 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/process/PolicyMgrUserGroupBuilder.java
>  070a39b 
> 
> Diff: https://reviews.apache.org/r/56829/diff/
> 
> 
> Testing
> ---
> 
> Manual
> 
> 
> Thanks,
> 
> Yan Zhou
> 
>

Rangers: Need help to move 9 open JIRA(s) to either RESOLVED state or move out to 1.0.0 version ....

[Selvamohan Neethiraj]

Rangers:

 

As I am preparing for ranger-0.7.0  release, I still see 9 more open issues 
targeted for ranger 0.7 fix version. 

(JIRA Filter:  project = RANGER AND fixVersion = 0.7.0 AND resolution = 
Unresolved and type not in (Task) ORDER BY due ASC, priority DESC, created ASC)

Can you please review this list and move your assigned jira(s) to next release 
version 1.0.0 if you cannot resolve it in next 4 hours?  If it is not moved out 
(or resolved), I will have to move them to 1.0.0 release before sending the 
release for VOTE.

 

Just another FYI:  I have disabled the build.apache.org Jenkin Job that was 
publishing our 0.7.0-SNAPSHOT libraries to Apache (since we have changed the 
version to 0.7.0 and the release is not yet approved).

 

Thanks,

Selva-

Re: Review Request 56780: RANGER-1391:Error occurred when use EndDate as Search Filter in Audit Access WebPage

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56780/#review166049
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Feb. 17, 2017, 2:54 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56780/
> ---
> 
> (Updated Feb. 17, 2017, 2:54 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
> Neethiraj, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1391
> https://issues.apache.org/jira/browse/RANGER-1391
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> #Solution:
> Add dateFieldName when use EndDate to query solr.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/solr/SolrUtil.java e0ab372 
> 
> Diff: https://reviews.apache.org/r/56780/diff/
> 
> 
> Testing
> ---
> 
> #Test Result:
> 1.Start Ranger-Admin success
> 2.Search success to use EndDate as Search Filter in Audit Access WebPage
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Review Request 56280: RANGER-1347 - The AtlasClient should fall back to the plain password if the password decryption fails

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56280/#review166050
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Feb. 3, 2017, 10:52 a.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56280/
> ---
> 
> (Updated Feb. 3, 2017, 10:52 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1347
> https://issues.apache.org/jira/browse/RANGER-1347
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The AtlasClient should fall back to the plain password if the password 
> decryption fails. Otherwise trying to Test the Connection when creating a new 
> service fails for me. The KnoxClient also follows this approach.
> 
> 
> Diffs
> -
> 
>   
> plugin-atlas/src/main/java/org/apache/ranger/services/atlas/client/AtlasClient.java
>  4f90469 
> 
> Diff: https://reviews.apache.org/r/56280/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

Re: Prep for ranger-0.7 release ...

[Selvamohan Neethiraj]

Sorry, I missed the ‘git push’ … It should be available now. 

Thanks,
Selva-

From:  Colm O hEigeartaigh <cohei...@apache.org>
Reply-To:  "dev@ranger.apache.org" <dev@ranger.apache.org>, 
"cohei...@apache.org" <cohei...@apache.org>
Date:  Thursday, February 9, 2017 at 9:40 AM
To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
Subject:  Re: Prep for ranger-0.7 release ...

Did you push the branch? It's not available yet as can be seen here:
https://git-wip-us.apache.org/repos/asf?p=ranger.git

Colm.

On Thu, Feb 9, 2017 at 1:54 PM, Selvamohan Neethiraj <sneet...@apache.org>
wrote:

 All:

 I have Just created ranger-0.7 branch on Apache Ranger GIT at “02/09/2017
 13:50:12 GMT”,  which will be used for ranger-0.7 release.
 Please continue to use master branch for development.

 For release, I will cherry-pick any fixes needed from the master.
 If you feel that any of your fix needs to be merged to ranger-0.7 branch,
 please do send an email to the dev@ranger.apache.org.

 Thanks,
 Selva-

 From:  "Lal,Alok(allal)" <al...@ebay.com>
 Reply-To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
 Date:  Wednesday, February 8, 2017 at 1:08 PM
 To:  "dev@ranger.apache.org" <dev@ranger.apache.org>, "cohei...@apache.org"
 <cohei...@apache.org>
 Subject:  Re: Prep for ranger-0.7 release ...

 @Selva, Sounds good.

 On 2/8/17, 9:15 AM, "Colm O hEigeartaigh" <cohei...@apache.org> wrote:

 Sounds good to me. Perhaps we could wait a short period of time before
 enforcing "strict" cherry-picking, so that some of the more recent
 patches
 can appear in 0.7.

 Colm.

 On Wed, Feb 8, 2017 at 3:53 PM, Selvamohan Neethiraj <
 sneet...@apache.org>
 wrote:

 > Rangers:
 >
 > As we are planning to do a release of ranger 0.7 soon,  I would like
 to
 > create a branch ranger-0.7 for stabilizing the release.
 > All of the fixes should go into the master which will track for our
 next
 > major release (planning to call  it as 1.0.0 )  and if needed will
 get
 > cherry-picked into ranger-0.7 release.
 >
 > I am Volunteering  to be the release manager for ranger 0.7 release.
 >
 > Please let me know if any of you have any concerns and/or
 suggestions  on
 > the release process.
 >
 > Thanks,
 > Selva-
 >
 >
 >


 --
 Colm O hEigeartaigh

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







-- 
Colm O hEigeartaigh

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

[RESULT] [VOTE] Apache Ranger Release 0.7.0 - rc1

[Selvamohan Neethiraj]

Hello Rangers:

Thank you so much for your efforts to validate Apache Ranger 0.7.0 release 
candidate #1 and your feedback/vote.

More than 72 hours have passed and the current vote thread is considered 
concluded and passes with the following resolution:

Five  +1 votes from the following PPMC member(s):
+1 Colm O hEigeartaigh
+1 Gautam Borad
+1 Ramesh Mani
+1 Selvamohan Neethiraj
+1 Velmurugan Periasamy

Two +1 votes from the following non-PPMC member(s):
+1 Abhay Kulkarni
+1 Sailaja Polavarapu

Zero -1 votes:

I will start the process of moving the release artifacts to the mirrors.

Voting thread for reference - 
https://lists.apache.org/thread.html/7681e93c81caf9b7800e4adfd1984a53f6575003e5b1238dacbb707d@%3Cdev.ranger.apache.org%3E
 
<https://lists.apache.org/thread.html/7681e93c81caf9b7800e4adfd1984a53f6575003e5b1238dacbb707d@%3Cdev.ranger.apache.org%3E>

Issues fixed in this release - 
https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.7.0+-+Release+Notes
 
<https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.7.0+-+Release+Notes>

Thank you,
Selva-



> On Feb 22, 2017, at 2:47 AM, Velmurugan Periasamy 
> <vperias...@hortonworks.com> wrote:
> 
> +1
> 
> - Able to build successfully
> - Signatures are good
> - Rat check is fine
> - No binary files
> 
> From: Sailaja Polavarapu 
> <spolavar...@hortonworks.com<mailto:spolavar...@hortonworks.com>>
> Reply-To: "dev@ranger.apache.org<mailto:dev@ranger.apache.org>" 
> <dev@ranger.apache.org<mailto:dev@ranger.apache.org>>
> Date: Tuesday, February 21, 2017 at 8:20 PM
> To: "dev@ranger.apache.org<mailto:dev@ranger.apache.org>" 
> <dev@ranger.apache.org<mailto:dev@ranger.apache.org>>
> Subject: Re: [VOTE] Apache Ranger Release 0.7.0 - rc1
> 
> +1
> - Successfully extracted tar file
> - Able to clean and build successfully with rat plugin.
> 
> Thanks,
> Sailaja
> 
> 
> 
> 
> 
> 
> On 2/21/17, 3:37 PM, "Abhay Kulkarni" 
> <akulka...@hortonworks.com<mailto:akulka...@hortonworks.com>> wrote:
> 
> +1
> - Successfully built ranger from apache-ranger-0.7.0.tar.gz with rat plugin
> - Verified MD5/SHA hash
> 
> Thanks,
> -Abhay
> 
> On 2/21/17, 11:32 AM, "Ramesh Mani" 
> <rm...@hortonworks.com<mailto:rm...@hortonworks.com>> wrote:
> 
> +1 (binding)
> 
> - Did successful build of apache-ranger-0.7.0.tar.gz  with rat plugin.
> - Verified PGP signature, MD5/SHA hash.
> 
> Thanks,
> Ramesh
> 
> 
> On 2/20/17, 10:21 AM, "Selvamohan Neethiraj" 
> <sneet...@apache.org<mailto:sneet...@apache.org>> wrote:
> 
> Rangers:
> 
> 
> Thank you for your contribution to this Apache community to be able to
> release this major release ­ Ranger 0.7.0.
> 
> This release includes numerous improvements/bug-fixes as well as some new
> features over the previous release of Ranger (see Release Notes for
> details).
> 
> 
> Apache ranger-0.7.0 release candidate # 1 is now available with the
> following artifacts up for vote.
> 
> I kindly request all of the Rangers (dev & PMC members) to review and
> vote on this release.
> 
> 
> Git tag for the release:
> 
> https://github.com/apache/ranger/tree/ranger-0.7.0-rc1 (last commit id:
> f39e4880082f5579db49b29be735977a341c041b)
> 
> 
> Sources for the release:
> 
> https://dist.apache.org/repos/dist/dev/ranger/0.7.0-rc1/apache-ranger-0.7
> .
> 0.tar.gz
> 
> 
> Source release verification:
> 
> PGP Signature:
> 
> 
> https://dist.apache.org/repos/dist/dev/ranger/0.7.0-rc1/apache-ranger-0.7
> .
> 0.tar.gz.asc
> 
> MD5/SHA Hash:
> 
> 
> https://dist.apache.org/repos/dist/dev/ranger/0.7.0-rc1/apache-ranger-0.7
> .
> 0.tar.gz.mds
> 
> 
> Keys to verify the signature of the release artifact are available at:
> 
>  https://people.apache.org/keys/group/ranger.asc
> 
> 
> Release Notes:
> 
> 
> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.7.0+-+
> R
> elease+Notes
> 
> 
> Build verification steps can be found at:
> 
>   http://ranger.apache.org/quick_start_guide.html
> 
> 
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
> 
> [ ] +1  approve
> 
> [ ] +0  no opinion
> 
> [ ] -1  disapprove (and reason why)
> 
> 
> Here is my +1 (binding).
> 
> 
> Thank you,
> 
> Selva-
> 
> 
> 
> 
> 

Re: Review Board requests

[Selvamohan Neethiraj]

Colm,

Reopened https://issues.apache.org/jira/browse/INFRA-13508 …

Thanks,
Selva-


From:  Colm O hEigeartaigh <cohei...@apache.org>
Reply-To:  "dev@ranger.apache.org" <dev@ranger.apache.org>, 
"cohei...@apache.org" <cohei...@apache.org>
Date:  Thursday, April 13, 2017 at 8:18 AM
To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
Subject:  Re: Review Board requests

Hi Selvamohan,

Could you re-open the JIRA (
https://issues.apache.org/jira/browse/INFRA-13508) please? Maybe INFRA
didn't see my comment on it.

Colm.

On Thu, Apr 6, 2017 at 10:13 AM, Selvamohan Neethiraj <sneet...@apache.org>
wrote:

 Colm,

 Based on my permission, I am not able to close down all old RR.
 Thanks for offering to lead this effort to close old RR; Please work with
 INFRA and keep us informed if you run into any trouble.

 Thanks,
 Selva-

 From:  Colm O hEigeartaigh <cohei...@apache.org>
 Reply-To:  "dev@ranger.apache.org" <dev@ranger.apache.org>, "
 cohei...@apache.org" <cohei...@apache.org>
 Date:  Wednesday, April 5, 2017 at 6:41 PM
 To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
 Subject:  Re: Review Board requests

 Hi Selvamohan,

 Any update on this? It would be great to be able to close submitted review
 requests rather than having to chase the submitter up. It makes it very
 difficult to see what RR are outstanding or not at the moment. If you want
 I can take the lead on talking to INFRA about this.

 Thanks,

 Colm.

 On Wed, Mar 8, 2017 at 1:56 PM, Selvamohan Neethiraj <sneet...@apache.org>
 wrote:

  Colm:



  I am able to see more RR only if I use the url,
  https://reviews.apache.org/groups/ranger/

  However, this view does not allow me to edit … Let me play with it today
  and see if I can resolve it soon … Otherwise, I will open a JIRA to take
  care of this.



  Selva-



  From: Colm O hEigeartaigh <cohei...@apache.org>
  Reply-To: <cohei...@apache.org>
  Date: Tuesday, March 7, 2017 at 9:07 AM
  To: Selvamohan Neethiraj <sneet...@apache.org>
  Cc: "dev@ranger.apache.org" <dev@ranger.apache.org>
  Subject: Re: Review Board requests



  No, I don't think so, they all appear to be related to Ranger? I am
  looking here:

  https://reviews.apache.org/dashboard/?group=ranger

  For example:

  https://reviews.apache.org/r/50754/

  is still open, but refers to the resolved JIRA:

  https://issues.apache.org/jira/browse/RANGER-1197

  Colm.





  On Tue, Mar 7, 2017 at 1:56 PM, Selvamohan Neethiraj <sneet...@apache.org
 >
  wrote:

  Colm,

  I am seeing only 23 open incoming issues.
  Are you seeing the issues from other project (other than, ranger) ?
  Because, the filter group=ranger seems to be bringing RR from other
  projects too …

  Selva-


  On 3/7/17, 8:50 AM, "Colm O hEigeartaigh" <cohei...@apache.org> wrote:

  I see 140+ RR associated with the Ranger group:

  https://reviews.apache.org/dashboard/?group=ranger

  If I go to the second page, almost all of the issues appear to be
  shipped,
  but the issues aren't marked as submitted, unless I'm missing
  something.

  Colm,

  On Tue, Mar 7, 2017 at 1:45 PM, Selvamohan Neethiraj <
  sneet...@apache.org>
  wrote:

  > Colm:
  >
  > I was able to close all older RR from https://reviews.apache.org/r
  > Do you still see them in your inbox of your review board ?
  >
  > Selva-
  >
  > On 3/7/17, 7:00 AM, "Colm O hEigeartaigh" <cohei...@apache.org>
  wrote:
  >
  > As per the INFRA JIRA https://issues.apache.org/
  > jira/browse/INFRA-13508 -
  > it appears we now have the ability to close (submitted) review
  board
  > requests...Selvamohan does it work for you?
  >
  > Colm.
  >
  > On Thu, Feb 16, 2017 at 10:06 AM, Velmurugan Periasamy <
  v...@apache.org
  > >
  > wrote:
  >
  > > I agree. I request all patch submitters to close the
  > submitted/discarded
  > > review requests.
  > >
  > > From: Colm O hEigeartaigh <cohei...@apache.org>
  > > Reply-To: "dev@ranger.apache.org" <dev@ranger.apache.org>, "
  > > cohei...@apache.org" <cohei...@apache.org>
  > > Date: Thursday, February 16, 2017 at 4:56 AM
  > > To: "dev@ranger.apache.org" <dev@ranger.apache.org>
  > > Subject: Re: Review Board requests
  > >
  > > I'll ask to see if INFRA know anything about it. I thought
  maybe
  > someone
  > > from the dev team had "administrator" privileges for the
 Ranger
  > group and
  > > could ad

Draft Board Report for Apache Ranger - Period Ending March-31-2017

[Selvamohan Neethiraj]

Rangers:


Here is the board report for March-2017.


Thanks,
Selva-





# Description:
The Ranger project is a framework to enable, monitor and manage comprehensive 
data security across the Hadoop platform.

# Issues:
* There are no issues requiring board attention at this time.

# Activity:
* Community is adding new enhancements for next 1.0.0 and lot of interest in 
inegration with Apache Atlas
* Jira: +73(added) -71(resolved) over last 31 days (Mar-2017)
* Git (Source): 67 commits over last 31 days (Mar-2017)
* SVN (Site & Docs): 2 commits over last 31 days (Mar-2017)

# Health report:
* Added one new committers and Expecting more adaption to Apache Ranger
* Scoping for next release is in progress, which may include integration with 
other Apache projects

## PMC changes:
 - Currently 17 PMC members.
 - Last PMC members were added as part of Ranger Graduation on Jan 18, 2017.
 - No new PMC members added in the last 1 months

# Committer base changes:
* Currently 23 committers.
* New commmitters in the last 1 months:
- Qiang Zhang was added as a committer on Mon Mar 04 2017

# Releases:
* No new releases in Mar 2017

# Mailing list activity:
* dev@ranger.apache.org:
- 734 emails sent to list (in the month of Mar 2017)
* u...@ranger.apache.org:
-  16 emails sent to list (in the month of Mar 2017)
* comm...@ranger.apache.org:
- 108 emails sent to list (in the month of Mar 2017)


# JIRA activity:
* 73 JIRA tickets created in the month of Mar 2017
* 71 JIRA tickets closed/resolved in the month of Mar 2017

Re: Can't change the Assignee to oneself?

[Selvamohan Neethiraj]

Yan,

I have added you as Contributor to Apache Ranger JIRA.

Thanks,
Selva-

On 3/8/17, 1:14 PM, "Yan Zhou" <yzhouopensou...@gmail.com> wrote:

Thanks Selvamohan.

I have actually contributed several patches. So please add me as a
contributor.

On Wed, Mar 8, 2017 at 9:05 AM, Selvamohan Neethiraj <sneet...@apache.org>
wrote:

> Hi Yan,
>
> Welcome to Ranger Dev Community ….
>
> Our Policy allows only Contributors/Committers to be able to set/modify
> the assignee of the JIRA.
>
> If you would like to provide patch and/or documentation for the Apache
> Ranger, please send a request to add yourself as a contributor in the dev
> mailing list.
> Once you are added as contributors (by the JIRA Administrators), you
> should be able to assign/re-assign JIRA yourself.
>
> Thanks,
> Selva-
>
> From:  Yan Zhou <yzhouopensou...@gmail.com>
> Reply-To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
> Date:  Wednesday, March 8, 2017 at 11:59 AM
> To:  "dev@ranger.apache.org" <dev@ranger.apache.org>, Colm O hEigeartaigh
> <cohei...@apache.org>
> Subject:  Re: Can't change the Assignee to oneself?
>
> https://issues.apache.org/jira/browse/RANGER-1252, yzhou2001
>
> A basic question is whether there is a Ranger jira policy that only allows
> power users to set assignee? Or a grant of right has to be given by a 
power
> user ?
>
> Thanks,
>
> On Wed, Mar 8, 2017 at 8:51 AM, Colm O hEigeartaigh <cohei...@apache.org>
> wrote:
>
>  What JIRA number is it, and what is your JIRA account username?
>
>  Colm.
>
>  On Wed, Mar 8, 2017 at 4:41 PM, Yan Zhou <yzhouopensou...@gmail.com>
>  wrote:
>
>  > Hi, I filed a Ranger jira and posted a patch. But it seems to me that I
>  > can't change the assignee field to myself.  Is this the way that Ranger
>  > jira is supposed to work? Or do I need extra steps in order to be able
> to
>  > do so?
>  >
>  > Thanks!
>  >
>
>
>
>  --
>  Colm O hEigeartaigh
>
>  Talend Community Coder
>  http://coders.talend.com
>
>
>
>

Re: Request to make me contributor in Apache Ranger

[Selvamohan Neethiraj]

Hi Bhavik,

What is your JIRA identifier? If you do not have one, please create a JIRA id 
from https://issues.apache.org/jira and let me know your username in JIRA 
system.

Thanks,
Selva-


On 3/8/17, 11:45 PM, "Bhavik Patel"  wrote:

Rangers:

As I have been involved in the Apache Ranger project for a while now, Can
you please add me as a contributor to the project ?


Thanks,
Bhavik Patel

Re: Request to make me contributor in Apache Ranger

[Selvamohan Neethiraj]

Bhavik,

Your JIRA user account has been added as contributor for Apache Ranger.
Let me know if you run into any issues.

Thanks,
Selva-


> On Mar 9, 2017, at 10:57 PM, Bhavik Patel <bhavikpatel...@gmail.com> wrote:
> 
> Hi Selva,
> 
> Apache JIRA username: bpatel
> Email-id: bhavikpatel...@gmail.com <mailto:bhavikpatel...@gmail.com>
> 
> Please let me know if anything else is needed from my end.
> 
> 
> Thanks,
> Bhavik Patel
> 
> 
> On Thu, Mar 9, 2017 at 7:13 PM, Selvamohan Neethiraj <sneet...@apache.org 
> <mailto:sneet...@apache.org>> wrote:
> Hi Bhavik,
> 
> What is your JIRA identifier? If you do not have one, please create a JIRA id 
> from https://issues.apache.org/jira <https://issues.apache.org/jira> and let 
> me know your username in JIRA system.
> 
> Thanks,
> Selva-
> 
> 
> On 3/8/17, 11:45 PM, "Bhavik Patel" <bhavikpatel...@gmail.com 
> <mailto:bhavikpatel...@gmail.com>> wrote:
> 
> Rangers:
> 
> As I have been involved in the Apache Ranger project for a while now, Can
> you please add me as a contributor to the project ?
> 
> 
> Thanks,
> Bhavik Patel
> 
> 
> 
> 
> 

Re: Review Board requests

[Selvamohan Neethiraj]

Colm:

 

I am able to see more RR only if I use the url, 
https://reviews.apache.org/groups/ranger/ 

However, this view does not allow me to edit … Let me play with it today and 
see if I can resolve it soon … Otherwise, I will open a JIRA to take care of 
this.

 

Selva-

 

From: Colm O hEigeartaigh <cohei...@apache.org>
Reply-To: <cohei...@apache.org>
Date: Tuesday, March 7, 2017 at 9:07 AM
To: Selvamohan Neethiraj <sneet...@apache.org>
Cc: "dev@ranger.apache.org" <dev@ranger.apache.org>
Subject: Re: Review Board requests

 

No, I don't think so, they all appear to be related to Ranger? I am looking 
here:

https://reviews.apache.org/dashboard/?group=ranger

For example:

https://reviews.apache.org/r/50754/

is still open, but refers to the resolved JIRA: 

https://issues.apache.org/jira/browse/RANGER-1197

Colm.

 

 

On Tue, Mar 7, 2017 at 1:56 PM, Selvamohan Neethiraj <sneet...@apache.org> 
wrote:

Colm,

I am seeing only 23 open incoming issues.
Are you seeing the issues from other project (other than, ranger) ?  Because, 
the filter group=ranger seems to be bringing RR from other projects too …

Selva-


On 3/7/17, 8:50 AM, "Colm O hEigeartaigh" <cohei...@apache.org> wrote:

I see 140+ RR associated with the Ranger group:

https://reviews.apache.org/dashboard/?group=ranger

If I go to the second page, almost all of the issues appear to be shipped,
but the issues aren't marked as submitted, unless I'm missing something.

    Colm,

On Tue, Mar 7, 2017 at 1:45 PM, Selvamohan Neethiraj <sneet...@apache.org>
wrote:

> Colm:
>
> I was able to close all older RR from https://reviews.apache.org/r
> Do you still see them in your inbox of your review board ?
>
> Selva-
>
> On 3/7/17, 7:00 AM, "Colm O hEigeartaigh" <cohei...@apache.org> wrote:
>
> As per the INFRA JIRA https://issues.apache.org/
> jira/browse/INFRA-13508 -
> it appears we now have the ability to close (submitted) review board
> requests...Selvamohan does it work for you?
>
> Colm.
>
> On Thu, Feb 16, 2017 at 10:06 AM, Velmurugan Periasamy 
<v...@apache.org
> >
> wrote:
>
> > I agree. I request all patch submitters to close the
> submitted/discarded
> > review requests.
> >
> > From: Colm O hEigeartaigh <cohei...@apache.org>
> > Reply-To: "dev@ranger.apache.org" <dev@ranger.apache.org>, "
> > cohei...@apache.org" <cohei...@apache.org>
> > Date: Thursday, February 16, 2017 at 4:56 AM
> > To: "dev@ranger.apache.org" <dev@ranger.apache.org>
> > Subject: Re: Review Board requests
> >
> > I'll ask to see if INFRA know anything about it. I thought maybe
> someone
> > from the dev team had "administrator" privileges for the Ranger
> group and
> > could add individual developers. In the meantime, could all devs
> look at
> > the patches they have submitted and mark them as "submitted" if the
> patches
> > have been applied. In particular, kulkabhay and rmani have a lot of
> > outstanding review requests, thanks!
> >
> > Colm.
> >
> > On Mon, Feb 13, 2017 at 10:43 PM, Don Bosco Durai <bo...@apache.org>
> > wrote:
> >
> > Does anyone one know how about to do it?
> >
> > Thanks
> >
> > Bosco
> >
> >
> > On 2/6/17, 5:02 AM, "Colm O hEigeartaigh" <cohei...@apache.org>
> wrote:
> >
> >  There are a lot of open reviews requests that have in fact been
> > applied,
> >  but not marked as submitted.
> >
> >  Would it be possible to grant all PMC members administrator
> privileges
> > so
> >  that they can manually close submitted requests?
> >
> >  Or has anyone any better suggestions of managing the review
> board?
> >
> >  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






-- 

Colm O hEigeartaigh

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

Draft board report for Apache Ranger - Apr-2017 to Jun-2017 ...

[Selvamohan Neethiraj]

All:

Attached is the board report for the past 3 months (Apr-2017 to Jun-2017). 
As it is already past due, I am posting this report today. If any changes 
required, please send an email and I will update the report asap.

Thanks,
Selva-
===

# Description:
The Ranger project is a framework to enable, monitor and manage comprehensive 
data security across the Hadoop platform.

# Issues:
* There are no issues requiring board attention at this time.

# Activity:
* Community is working to improve security features of hive/hdfs/user sync 
modules and adding more integration with Apache Atlas
* Jira: +182(added) -176(resolved) over last 3 months (Apr-2017 to June-2017)
* Git (Source): 164 commits over last 3 months (Apr-2017 to Jun-2017)
* SVN (Site & Docs): 1 commits over last 3 months (Apr-2017 to Jun-2017)

# Health report:
* Fixed few CVE issues - raised by community and user groups
* Actively working to add more functionalities to Apache Ranger
* Still working on next release with more integration with Apache Atlas

## PMC changes:
 - Currently 17 PMC members.
 - Last PMC members were added as part of Ranger Graduation on Jan 18, 2017.
 - No new PMC members added in the last 3 months

# Committer base changes:
* Currently 23 committers.
* No new committers added in the last 3 months:
- Qiang Zhang was added as a committer on Mon Mar 04 2017

# Releases:
* 0.7.1: 2017-06-06

# Mailing list activity:
* dev@ranger.apache.org:
- 1755 emails sent to list (durng the period Apr-2017 and Jun-2017)
* u...@ranger.apache.org:
-  109 emails sent to list (durng the period Apr-2017 and Jun-2017)
* comm...@ranger.apache.org:
- 247 emails sent to list (durng the period Apr-2017 and Jun-2017)


# JIRA activity:
* 182 JIRA tickets created during the period Apr-2017 and Jun-2017
* 176 JIRA tickets closed/resolved during the period Apr-2017 and Jun-2017

Fwd: Good examples of licensing in ASF produced web apps?

[Selvamohan Neethiraj]

@Ranger,

Please see the email below which indicates that Ranger WAR file have 
dependencies that should not be bundled and/or specified in the LICENSE/NOTICE 
files. Can we review our binary release files to ensure that we are in 
compliance with Apache Releases?

@Roman:
We will try to go through the list and ensure that our LICENSE and NOTICE files 
are updated with bundled binaries ? (RANGER-1623 
)
In the meanwhile, if you can add the details on the files that are not in 
compliance in the above JIRA, it will greatly help the ranger community to fix 
it asap.


Thanks,
Selva-

> Begin forwarded message:
> 
> From: Roman Shaposhnik 
> Subject: Good examples of licensing in ASF produced web apps?
> Date: May 26, 2017 at 5:49:46 PM EDT
> To: "gene...@incubator.apache.org" 
> Reply-To: gene...@incubator.apache.org
> 
> Hi!
> 
> I advising a podling on producing a binary release that
> includes a Java web app (think war file). I wanted to give
> them a taste of what TLPs do so I went to the ones that
> I knew were generating war files: Oozie and Ranger.
> You know the stuff I'm familiar with in Hadoop ecosystem.
> 
> What he discovered may shock you! No, but seriously.
> 
> Here's what these projects publish on Maven central:
> 
> https://search.maven.org/remotecontent?filepath=org/apache/oozie/oozie-webapp/4.3.0/oozie-webapp-4.3.0.war
> https://search.maven.org/remotecontent?filepath=org/apache/ranger/security-admin-web/0.7.0/security-admin-web-0.7.0.war
> 
> Each of these WAR files:
>   1. bundles all sorts of dependancies -- not just the bits coming
>from the project itself
> 
>2. Neither provides a meanigful LICENSE nor NOTICE files.
>The ones under ./WEB-INF/classes/META-INF are stock ones
>and really don't address the binary dependencies bundling
> 
> Have we somehow relaxed the requirements for binary artifacts?
> I hope not -- and if not -- what are the good examples of web app
> projects doing it right?
> 
> Thanks,
> Roman.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

Re: Moving master to Java 1.8?

[Selvamohan Neethiraj]

+1

Thanks,
Selva-

> On Dec 18, 2017, at 2:52 PM, Velmurugan Periasamy  wrote:
> 
> Colm ­ this is a good idea. +1
> 
> From:  Ramesh Mani 
> Reply-To:  "dev@ranger.apache.org" 
> Date:  Monday, December 18, 2017 at 1:08 PM
> To:  "dev@ranger.apache.org" , "cohei...@apache.org"
> 
> Subject:  Re: Moving master to Java 1.8?
> 
> Colm,
> 
> I having being thinking on this, when we move to Hbase 2.0 version we need
> Java 1.8 for the  Ranger hbase plugin to compile.
> 
> +1 for this.
> 
> Thanks,
> Ramesh
> 
> On 12/16/17, 10:18 AM, "Colm O hEigeartaigh"  wrote:
> 
>> Hi all,
>> 
>> Before I fix the currently failing Hive tests with JDK 7, I'm wondering if
>> it's time to move Ranger master to require Java 1.8. Apache Hadoop 3.0.0
>> requires Java 1.8 - so we will have to make the switch if we want to pick
>> up Hadoop 3.0.0 for Ranger 1.0.0. Apache Knox 0.14.0 is also Java 8 only,
>> so we can't upgrade to that as things stand.
>> 
>> Thoughts?
>> 
>> Colm.
>> 
>> 
>> --
>> Colm O hEigeartaigh
>> 
>> Talend Community Coder
>> http://coders.talend.com
> 
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: Ranger website checks

[Selvamohan Neethiraj]

Thanks Owen. Ranger site issues raised from whimsy site-check tool is fixed 
(https://issues.apache.org/jira/browse/RANGER-1975 
)  and is now clean (see: 
https://whimsy.apache.org/site/project/ranger 
 ) ….

Selva-

> On Feb 7, 2018, at 1:14 PM, Owen O'Malley  wrote:
> 
> Hi,
>   The ranger.apache.org website is failing a lot of the automated checks
> that Apache runs.
> 
> https://whimsy.apache.org/site/project/ranger
> 
> In particular, Ranger should absolutely get the security check resolved.
> 
> Thanks,
>   Owen



signature.asc
Description: Message signed with OpenPGP

Re: Prep for ranger-1.0.0 release

[Selvamohan Neethiraj]

Thanks Sailaja for driving this effort …

+1 for Ranger Release version 1.0.0

Please let me know if you need any help on release related tasks ...

Thanks,
Selva-

> On Feb 22, 2018, at 8:34 PM, Sailaja Polavarapu  
> wrote:
> 
> Rangers:
> As we are planning to do a release of ranger 1.0.0 soon (tentatively 
> 3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing the 
> release. All of the fixes should go into the master which will track for our 
> next major release and if needed will get cherry-picked into ranger-1.0.0 
> release.
> 
> I am volunteering to be the release manager for ranger 1.0.0 release. Based 
> on the discussion, current plan is to make the ranger 1.0.0 release with 
> Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> 
> Please let me know if any of you have any concerns and/or suggestions on the 
> release process.
> 
> Thanks,
> Sailaja.



signature.asc
Description: Message signed with OpenPGP

Re: Review Request 68170: RANGER-2172: Fixing minor issue with the no. of characters read using sscanf

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68170/#review206821
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Aug. 2, 2018, 3:52 p.m., Sailaja Polavarapu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68170/
> ---
> 
> (Updated Aug. 2, 2018, 3:52 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-2172
> https://issues.apache.org/jira/browse/RANGER-2172
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Changed code to read only STRLEN-1 characters using sscanf in order to 
> correctly accommodate the array size.
> 
> 
> Diffs
> -
> 
>   unixauthnative/src/main/c/credValidator.c 189c2ca5e 
>   unixauthpam/src/main/c/pamCredValidator.c 8e3690301 
> 
> 
> Diff: https://reviews.apache.org/r/68170/diff/1/
> 
> 
> Testing
> ---
> 
> Tested manually from command line.
> 
> 
> Thanks,
> 
> Sailaja Polavarapu
> 
>

Draft board report for the period ending 07/31/2018

[Selvamohan Neethiraj]

Rangers:

Please review and provide your feedback on Apache board report for Apache 
Ranger for the past 3 months …

Thanks,
Selva-

===

## Description:
 - The Ranger project is a framework to enable, monitor and manage 
comprehensive data security across the Hadoop platform.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - Community has release Apache Ranger 1.1 and working on new 
features/improvements/bug fixes on the releases 2.0.0 and 1.x
 - Jira: +86(added) -65(resolved) over last 3 months
 - Git (Source): 53 commits over last 3 months
 - SVN (ranger site updates): 2 commits over last 3 months

## Health report:
 - Released Apache Ranger 1.1.0 with 20+ improvements to Apache Ranger and lot 
of bug fixes
 - Working on new features/improvements/bug fixes on the releases 2.0.0 and 1.x

## PMC changes:

 - Currently 18 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Abhay Kulkarni on Fri Dec 15 2017

## Committer base changes:

 - Currently 26 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Zsombor Gegesy at Sat Dec 09 2017

## Releases:

 - Apache Ranger 1.1.0 was released on Mon Jul 09 2018

## Mailing list activity:

 - dev@ranger.apache.org:
- 105 subscribers (up 1 in the last 3 months):
- 871 emails sent to list (1352 in previous quarter)

 - u...@ranger.apache.org:
- 173 subscribers (up 1 in the last 3 months):
- 67 emails sent to list (34 in previous quarter)


## JIRA activity:

 - 86 JIRA tickets created in the last 3 months
 - 65 JIRA tickets closed/resolved in the last 3 months

===




signature.asc
Description: Message signed with OpenPGP

Draft board report for the period ending 03/31/2018 ...

[Selvamohan Neethiraj]

Sorry for the delay in sending this out. Please review and provide your 
feedback on Apache board report for Apache Ranger.

Thanks,
Selva-


## Description:
 - The Ranger project is a framework to enable, monitor and manage 
comprehensive data security across the Hadoop platform.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - Community has release Apache Ranger 1.0 and working on improve/fix bugs on 
the releases both 1.0 and 0.7.x
 - Jira: +110(added) -96(resolved) over last 3 months
 - Git (Source): 58 commits over last 3 months
 - SVN (ranger site updates): 15 commits over last 3 months

## Health report:
 - Released Apache Ranger 1.0 with authorization engine to work with Apache 
Hadoop 3.0+ ecosystem
 - Working on some of the open bugs (branch 0.7 and 1.0 releases) along with 
new features for next release

## PMC changes:
 - Currently 18 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Abhay Kulkarni on Fri Dec 15 2017

## Committer base changes:
 - Currently 26 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Zsombor Gegesy at Sat Dec 09 2017

## Releases:
 - Apache Ranger 1.0.0 was released on Sun Mar 18 2018

## Mailing list activity:
 - dev@ranger.apache.org:
- 102 subscribers (up 1 in the last 3 months):
- 1144 emails sent to list (1356 in previous quarter)

 - u...@ranger.apache.org:
- 170 subscribers (up 1 in the last 3 months):
- 44 emails sent to list (56 in previous quarter)

## JIRA activity:
 - 110 JIRA tickets created in the last 3 months
 - 96 JIRA tickets closed/resolved in the last 3 months


signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache Ranger Release 1.0.0-rc1

[Selvamohan Neethiraj]

+1

Validated Signature
Validated Checksum
Build the source - successfully

Thanks,
Selva-


> On Mar 14, 2018, at 9:27 PM, Sailaja Polavarapu  
> wrote:
> 
> Rangers:
> Thank you for your contribution to Apache Ranger community. Apache Ranger 
> 1.0.0 release candidate #1 is now available for a vote within dev community. 
> Links to release artifacts are given below. I kindly request all of the 
> Rangers (dev & PMC members) to review and vote on this release.
> 
> Git tag for the release:
> 
> https://github.com/apache/ranger/tree/release-1.0.0-rc1 (last commit id:  
> c79aad4362b6f806da47462ec84e35108ba8eb1f)
> 
> 
> Sources for the release:
> https://dist.apache.org/repos/dist/dev/ranger/1.0.0-rc1/apache-ranger-1.0.0.tar.gz
> 
> 
> Source release verification:
> 
> PGP Signature:
> 
> https://dist.apache.org/repos/dist/dev/ranger/1.0.0-rc1/apache-ranger-1.0.0.tar.gz.asc
> 
> 
> MD5/SHA Hash:
> 
> https://dist.apache.org/repos/dist/dev/ranger/1.0.0-rc1/apache-ranger-1.0.0.tar.gz.mds
> 
> 
> Keys to verify the signature of the release artifact are available at:
> 
> https://dist.apache.org/repos/dist/release/ranger/KEYS
> 
> 
> Release Notes:
> 
>   https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75975356
> 
> 
> Build verification steps can be found at:
> 
>   http://ranger.apache.org/quick_start_guide.html
> 
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1
> 
> Thanks,
> Sailaja.
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache Ranger Release 1.2.0-rc1

[Selvamohan Neethiraj]

+1 for Apache Ranger 1.2.0-rc1 release ….

verified build & signature

Thanks,
Selva-

> On Sep 29, 2018, at 1:27 PM, Ramesh Mani  wrote:
> 
> +1 for release Apache Ranger 1.2.0-rc1
> 
> Verified build for the source with rat plugin and unit tests
> Verified some source files
> Verified PGP signature
> Verified MD5/SHA
> 
> Thanks,
> Ramesh
> 
> 
> 
> On 9/27/18, 4:24 PM, "Velmurugan Periasamy"  wrote:
> 
>> Hello Rangers:
>> 
>> Thank you for your contribution to Apache Ranger community. Apache Ranger
>> 1.2.0 release candidate #1 is now available for a vote within dev
>> community.
>> 
>> Links to RC1 release artifacts are given below. Kindly request all
>> Rangers (Dev's & PMC members) to review and vote on this release.
>> 
>> 
>> Git tag for the release:
>> https://github.com/apache/ranger/tree/ranger-1.2.0-rc1 (last commit id:
>> 39ec5a38913e1d852cffecbdb8688b2370b6318f)
>> 
>> 
>> Sources for the release:
>> https://dist.apache.org/repos/dist/dev/ranger/1.2.0-rc1/apache-ranger-1.2.
>> 0.tar.gz
>> 
>> 
>> Source release verification:
>> 
>> PGP Signature:
>> https://dist.apache.org/repos/dist/dev/ranger/1.2.0-rc1/apache-ranger-1.2.
>> 0.tar.gz.asc
>> 
>> MD5/SHA Hashes:
>> https://dist.apache.org/repos/dist/dev/ranger/1.2.0-rc1/apache-ranger-1.2.
>> 0.tar.gz.mds
>> https://dist.apache.org/repos/dist/dev/ranger/1.2.0-rc1/apache-ranger-1.2.
>> 0.tar.gz.sha1
>> https://dist.apache.org/repos/dist/dev/ranger/1.2.0-rc1/apache-ranger-1.2.
>> 0.tar.gz.sha256
>> https://dist.apache.org/repos/dist/dev/ranger/1.2.0-rc1/apache-ranger-1.2.
>> 0.tar.gz.sha512
>> 
>> 
>> Keys to verify the signature of the release artifact are available at:
>> https://dist.apache.org/repos/dist/release/ranger/KEYS
>> 
>> 
>> Release Notes:
>> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+1.2.0+-+R
>> elease+Notes
>> 
>> 
>> Build verification steps can be found at:
>> http://ranger.apache.org/quick_start_guide.html
>> 
>> 
>> The vote will be open for at least 72 hours or until necessary number of
>> votes are reached.
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> Here is my +1
>> 
>> Thank you,
>> Vel
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Draft board report for the period ending 09/30/2018

[Selvamohan Neethiraj]

Rangers:

Please review and provide your feedback on Apache board report for Apache 
Ranger for the past 3 months …

Thanks,
Selva-

===

## Description:
 - The Ranger project is a framework to enable, monitor and manage 
comprehensive data security across the Hadoop platform.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - Community has released Apache Ranger 1.2.0
 - Jira: has usual amount of activities in the community. +93(added) 
-64(resolved) over last 3 months.
 - Git (source): 253 commits over last 3 months; Some of the key improvements 
have been added to ranger source code along with backport to older 
maint-releases - showing unusally higher commits than usual.
 - SVN (ranger site updates): 2 commits over last 3 months;

## Health report:
 - Release Apache Ranger 1.2.0 with major performance improvement features and 
address some of the upgrade issues
 - Community is working on next release of 2.0.0 with features like support for 
Hive3.0, HBase 2.0, Kafka 2.0.0 along with Enhacements to Hive,HBase plugins to 
perform new authorization support.
 - Also, Community is working to release a maint release of 1.2.1 soon with few 
bug fixes.

## PMC changes:

 - Currently 18 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Abhay Kulkarni on Fri Dec 15 2017

## Committer base changes:

 - Currently 26 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Zsombor Gegesy at Sat Dec 09 2017

## Releases:

 - Apache Ranger 1.2.0 was released on Wed Oct 03 2018

## Mailing list activity:

 - TODO Please explain what the following statistics mean
   for the project. If there is nothing significant in the figures, omit this
   section.

 - dev@ranger.apache.org:
- 104 subscribers (up 0 in the last 3 months):
- 1020 emails sent to list (921 in previous quarter)

 - u...@ranger.apache.org:
- 176 subscribers (up 6 in the last 3 months):
- 17 emails sent to list (69 in previous quarter)


## JIRA activity:

 - 93 JIRA tickets created in the last 3 months
 - 64 JIRA tickets closed/resolved in the last 3 months

===



signature.asc
Description: Message signed with OpenPGP

Re: Subject: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[Selvamohan Neethiraj]

+1 

Thanks,
Selva-

> On Dec 10, 2018, at 3:06 PM, Velmurugan Periasamy  wrote:
> 
> Rangers:
> 
> Please see below. I propose to move ranger repos over to gitbox (from 
> git-wip-us.apache.org ) during the first phase 
> (voluntary coordination). Please share your thoughts. 
> 
> Once there is agreement in dev list, I can open INFRA ticket to complete the 
> move. Tentative target next week (week of Dec 17). 
> 
> Here’s my +1. 
> 
> Thank you,
> Vel
> 
> 
> From: Daniel Gruno 
> Sent: Friday, December 7, 2018 11:52 AM
> To: us...@infra.apache.org
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on 
> git-wip-us.apache.org
> 
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
> 
> Hello Apache projects,
> 
> I am writing to you because you may have git repositories on the
> git-wip-us server, which is slated to be decommissioned in the coming
> months. All repositories will be moved to the new gitbox service which
> includes direct write access on github as well as the standard ASF
> commit access via gitbox.apache.org.
> 
> ## Why this move? ##
> The move comes as a result of retiring the git-wip service, as the
> hardware it runs on is longing for retirement. In lieu of this, we
> have decided to consolidate the two services (git-wip and gitbox), to
> ease the management of our repository systems and future-proof the
> underlying hardware. The move is fully automated, and ideally, nothing
> will change in your workflow other than added features and access to
> GitHub.
> 
> ## Timeframe for relocation ##
> Initially, we are asking that projects voluntarily request to move
> their repositories to gitbox, hence this email. The voluntary
> timeframe is between now and January 9th 2019, during which projects
> are free to either move over to gitbox or stay put on git-wip. After
> this phase, we will be requiring the remaining projects to move within
> one month, after which we will move the remaining projects over.
> 
> To have your project moved in this initial phase, you will need:
> 
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project repos
>   over to gitbox (as stated, this is highly automated and will take
>   between a minute and an hour, depending on the size and number of
>   your repositories)
> 
> To sum up the preliminary timeline;
> 
> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>   relocation
> - January 9th -> February 6th: Mandated (coordinated) relocation
> - February 7th: All remaining repositories are mass migrated.
> 
> This timeline may change to accommodate various scenarios.
> 
> ## Using GitHub with ASF repositories ##
> When your project has moved, you are free to use either the ASF
> repository system (gitbox.apache.org) OR GitHub for your development
> and code pushes. To be able to use GitHub, please follow the primer
> at: https://reference.apache.org/committer/github
> 
> 
> We appreciate your understanding of this issue, and hope that your
> project can coordinate voluntarily moving your repositories in a
> timely manner.
> 
> All settings, such as commit mail targets, issue linking, PR
> notification schemes etc will automatically be migrated to gitbox as
> well.
> 
> With regards, Daniel on behalf of ASF Infra.
> 
> PS:For inquiries, please reply to us...@infra.apache.org, not your
> project's dev list :-).
> 
> 

Draft board report for the period ending 12/31/2018

[Selvamohan Neethiraj]

Rangers:

Please review and provide your feedback on Apache board report for Apache 
Ranger for the past 3 months …

Thanks,
Selva-


## Description:
 - The Ranger project is a framework to enable, monitor and manage 
comprehensive data security across the Hadoop platform.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - Jira activities are normal for a post release of 1.2.0 release and working 
towards new major release, 2.0.0.
 - SVN (ranger site updates): 2 commits over last 3 months - mainly to update 
migration to gitbox repository;

## Health report:
 - Team is working on a major release of Ranger - version 2.0.0 with supporting 
for securing new version of other apache projects (Kafaka 2.0, Knox 1.1.0, 
Kylin 2.5.0, ...)
 - Team is also working on a minor release of Ranger on 1.2.1 on top of the 
last release of 1.2.0 to fix few minor issues.
 - Worked with Apache INFRA team to move our repository to gitbox

## PMC changes:
 - Currently 18 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Abhay Kulkarni on Fri Dec 15 2017

## Committer base changes:
 - Currently 28 committers.
 - New commmitters:
- Bhavik Patel was added as a committer on Thu Nov 01 2018
- Nitin Galave was added as a committer on Thu Nov 01 2018

## Releases:
 - Apache Ranger 1.2.0 was released on Wed Oct 03 2018

## Mailing list activity:
 - dev@ranger.apache.org:
- 104 subscribers (up 0 in the last 3 months):
- 1004 emails sent to list (874 in previous quarter)
 - u...@ranger.apache.org:
- 180 subscribers (up 2 in the last 3 months):
- 15 emails sent to list (34 in previous quarter)

## JIRA activity:
 - 77 JIRA tickets created in the last 3 months
 - 78 JIRA tickets closed/resolved in the last 3 months

Re: Subject: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[Selvamohan Neethiraj]

All:

I have created RANGER-2316  
for updating repo URL in Quick Startup Guide and fixed it in the repo.
After update, I have followed the process mentioned in docs/README.txt to 
deploy the changes to documentation site, 
http://ranger.apache.org/quick_start_guide.html


Thanks,
Selva-

> On Dec 17, 2018, at 3:27 PM, Velmurugan Periasamy  wrote:
> 
> Migration has been completed. 
> 
> New target URL(s): 
> - https://gitbox.apache.org/repos/asf/ranger.git 
> - https://github.com/apache/ranger 
> 
> 
> 
>> On Dec 17, 2018, at 2:47 PM, Velmurugan Periasamy  wrote:
>> 
>> Hello Rangers:
>> 
>> Thank you for your responses. Since there is agreement in the dev list (ref: 
>> https://lists.apache.org/thread.html/fb07264b623c458389c8487e53d0a236341cb733a2055e970e13e1e1@%3Cdev.ranger.apache.org%3E
>>  
>> ),
>>  I will go ahead and open an Infra ticket to schedule the relocation of git 
>> repos.
>> 
>> Thank you,
>> Vel
>> 
>> 
>> From: Gautam Borad mailto:gau...@apache.org>>
>> Sent: Wednesday, December 12, 2018 3:49 AM
>> To: dev@ranger.apache.org 
>> Subject: Re: Subject: [NOTICE] Mandatory relocation of Apache git 
>> repositories on git-wip-us.apache.org 
>> 
>> +1
>> 
>> On Wed, Dec 12, 2018 at 2:45 AM Zs. > > wrote:
>> 
>>> +1
>>> 
>>> Regards,
>>> Zsombor
>>> 
>>> On Tue, Dec 11, 2018 at 7:28 PM Sailaja Polavarapu <
>>> spolavar...@hortonworks.com > wrote:
>>> 
 +1
 
 On 12/10/18, 1:22 PM, "Abhay Kulkarni" >>> >
>>> wrote:
 
+1
 
On 12/10/18, 12:06 PM, "Velmurugan Periasamy" >>> >
>>> wrote:
 
> Rangers:
> 
> Please see below. I propose to move ranger repos over to gitbox
>>> (from
> git-wip-us.apache.org  
> >) during 
> the
 first
> phase (voluntary coordination). Please share your thoughts.
> 
> Once there is agreement in dev list, I can open INFRA ticket to
 complete
> the move. Tentative target next week (week of Dec 17).
> 
> Here¹s my +1.
> 
> Thank you,
> Vel
> 
> 
> From: Daniel Gruno mailto:humbed...@apache.org>>
> Sent: Friday, December 7, 2018 11:52 AM
> To: us...@infra.apache.org 
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org 
> 
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
> 
> Hello Apache projects,
> 
> I am writing to you because you may have git repositories on the
> git-wip-us server, which is slated to be decommissioned in the
>>> coming
> months. All repositories will be moved to the new gitbox service
>>> which
> includes direct write access on github as well as the standard ASF
> commit access via gitbox.apache.org .
> 
> ## Why this move? ##
> The move comes as a result of retiring the git-wip service, as the
> hardware it runs on is longing for retirement. In lieu of this, we
> have decided to consolidate the two services (git-wip and gitbox),
>>> to
> ease the management of our repository systems and future-proof the
> underlying hardware. The move is fully automated, and ideally,
>>> nothing
> will change in your workflow other than added features and access to
> GitHub.
> 
> ## Timeframe for relocation ##
> Initially, we are asking that projects voluntarily request to move
> their repositories to gitbox, hence this email. The voluntary
> timeframe is between now and January 9th 2019, during which projects
> are free to either move over to gitbox or stay put on git-wip. After
> this phase, we will be requiring the remaining projects to move
>>> within
> one month, after which we will move the remaining projects over.
> 
> To have your project moved in this initial phase, you will need:
> 
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project
>>> repos
>  over to gitbox (as stated, this is highly automated and will take
>  between a minute and an hour, depending on the size and number of
>  your repositories)
> 
> To sum up the preliminary timeline;
> 
> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>  relocation
> - January 9th -> 

Re: Apache Ranger plugins

[Selvamohan Neethiraj]

Hi,

Please subscribe to dev@ranger.apache.org and post your API/dev questions in 
the mailing list to get faster response.

Please refer to the Wiki pages from http://ranger.apache.org/ for more details 
on the credentials storage for accessing Ranger Policy Manager API.
In a secured cluster, Kerberos credential is used to authenticate into Ranger 
Policy Manager Service. 

Let us know if you need more details,

Thanks,
Selva-


> On Jan 10, 2019, at 8:14 AM, Odon Copon  wrote:
> 
> Hi Selvamohan,
> I have a question regarding Ranger plugins. Have tried looking in the 
> documentation but haven't find any information about this. So I thought was a 
> good idea contacting directly the people involved in the development.
> How does the plugins communicate with Ranger Policy Manager API? Is there any 
> place where they store the credentials for accessing the API?
> I know the usersync has everything in rangerusersync.jceks but what about the 
> plugins? 
> If you don't know, would you please point me to anyone that could help me 
> understanding this?
> 
> Thanks.

Draft board report for the period ending 03/31/2019

[Selvamohan Neethiraj]

Rangers:

Please review and provide your feedback on Apache board report for Apache 
Ranger for the past 3 months …

Thanks,
Selva-




## Description:
 - The Ranger project is a framework to enable, monitor and manage 
comprehensive data security across the Hadoop platform.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - Team has been working on fixing issues to make Ranger work with Apache 
Hadoop 3.0+ technology suite for releasing next major Ranger version 2.0.0.
 - Also, team has added following new features in Ranger: Security 
Zone,Incremental Policy Upgrade, expand support for other HSM key storage.

## Health report:
 - As we are closer to the tail-end of the major release (Ranger 2.0.0), our 
mailing list counts seems to be lower than usual

## PMC changes:

 - Currently 19 PMC members.
 - Qiang Zhang was added to the PMC on Fri Feb 08 2019

## Committer base changes:

 - Currently 28 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Bhavik Patel at Thu Nov 01 2018

## Releases:

 - Last release was Apache Ranger 1.2.0 on Wed Oct 03 2018

## Mailing list activity:

 - dev@ranger.apache.org:
- 111 subscribers (up 5 in the last 3 months):
- 498 emails sent to list (795 in previous quarter)

 - u...@ranger.apache.org:
- 188 subscribers (up 6 in the last 3 months):
- 114 emails sent to list (15 in previous quarter)


## JIRA activity:

 - 76 JIRA tickets created in the last 3 months
 - 57 JIRA tickets closed/resolved in the last 3 months

Re: Review Request 70642: RANGER-2427: Tag policies are not evaluated if no security zones are configured

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70642/#review215258
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On May 14, 2019, 1:34 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70642/
> ---
> 
> (Updated May 14, 2019, 1:34 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj, Ramesh Mani, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-2427
> https://issues.apache.org/jira/browse/RANGER-2427
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Policies downloaded to plugin have empty string as a value for zone-name. 
> This causes the check for zone-name of policy(empty string) and zone-name of 
> accessed resource(null) to fail. Consequently, none of the tag policies will 
> match.
> 
> zone-name check condition is fixed to account for empty zone-name in policy.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyEngineImpl.java
>  365edcf35 
> 
> 
> Diff: https://reviews.apache.org/r/70642/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with a cluster with no configured security zone and with a tag policy. 
> Ensured that tag policy is selected for evaluation when the accessed resource 
> matches tagged resource.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: [VOTE] Apache Ranger Release 2.0.0-rc1

[Selvamohan Neethiraj]

+1

Verified build.
Verified PGP signature.
Verified SHA256 checksum
Verified SHA512 checksum

Thanks,
Selva-

> On Aug 2, 2019, at 5:19 PM, Velmurugan Periasamy  wrote:
> 
> Hello Ranger community:
> 
> Thank you for your contribution to Apache Ranger. Apache Ranger 2.0.0 release 
> candidate #1 is now available for a vote within dev community. 
> 
> Links to RC1 release artifacts are given below. Kindly request all Rangers 
> (Dev's & PMC members) to review and vote on this release.
> 
> 
> Git tag for the release:
> https://github.com/apache/ranger/tree/ranger-2.0.0-rc1 (last commit id:  
> 2a97668824d6a05f97193f3bf21d1bbe50a48330)
> 
> 
> Sources for the release:
> https://dist.apache.org/repos/dist/dev/ranger/2.0.0-rc1/apache-ranger-2.0.0.tar.gz
> 
> 
> Source release verification:
> 
> PGP Signature:
> https://dist.apache.org/repos/dist/dev/ranger/2.0.0-rc1/apache-ranger-2.0.0.tar.gz.asc
> 
> MD5/SHA Hashes:
> https://dist.apache.org/repos/dist/dev/ranger/2.0.0-rc1/apache-ranger-2.0.0.tar.gz.sha256
> https://dist.apache.org/repos/dist/dev/ranger/2.0.0-rc1/apache-ranger-2.0.0.tar.gz.sha512
> 
> 
> Keys to verify the signature of the release artifact are available at: 
> https://dist.apache.org/repos/dist/release/ranger/KEYS
> 
> 
> Release Notes:
> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.0.0+-+Release+Notes
> 
> 
> Build verification steps can be found at:
>   http://ranger.apache.org/quick_start_guide.html
> 
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1
> 
> Thank you,
> Velmurugan Periasamy
> 

Review Request 71587: RANGER-2606: added module to sign-artifacts profile to enable publish of all modules

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71587/
---

Review request for ranger, Colm O hEigeartaigh, Abhay Kulkarni, Ramesh Mani, 
and Velmurugan Periasamy.


Repository: ranger


Description
---

Added all modules to the sign-artifacts profile to fix this issue ...


Diffs
-

  pom.xml afc27d2cb 


Diff: https://reviews.apache.org/r/71587/diff/1/


Testing
---

Ran it from v2.0 release codebase to check if it is able to upload as part of 
the deployment. It works!
* Also, fixed some of the TAB characters (replaced with SPACE to look nice)


Thanks,

Selvamohan Neethiraj

Re: Review Request 71587: RANGER-2606: added module to sign-artifacts profile to enable publish of all modules

[Selvamohan Neethiraj]

> On Oct. 7, 2019, 5:39 p.m., Velmurugan Periasamy wrote:
> >

Was this patch worked for 2.0 release?  I will send another patch for master 
branch ...


- Selvamohan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71587/#review218125
---


On Oct. 7, 2019, 5:24 p.m., Selvamohan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/71587/
> ---
> 
> (Updated Oct. 7, 2019, 5:24 p.m.)
> 
> 
> Review request for ranger, Colm O hEigeartaigh, Abhay Kulkarni, Ramesh Mani, 
> and Velmurugan Periasamy.
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Added all modules to the sign-artifacts profile to fix this issue ...
> 
> 
> Diffs
> -
> 
>   pom.xml afc27d2cb 
> 
> 
> Diff: https://reviews.apache.org/r/71587/diff/1/
> 
> 
> Testing
> ---
> 
> Ran it from v2.0 release codebase to check if it is able to upload as part of 
> the deployment. It works!
> * Also, fixed some of the TAB characters (replaced with SPACE to look nice)
> 
> 
> Thanks,
> 
> Selvamohan Neethiraj
> 
>

Re: Review Request 71587: RANGER-2606: added module to sign-artifacts profile to enable publish of all modules

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71587/
---

(Updated Oct. 7, 2019, 10 p.m.)


Review request for ranger, Colm O hEigeartaigh, Abhay Kulkarni, Ramesh Mani, 
and Velmurugan Periasamy.


Changes
---

uploaded the diff file for the master branch


Bugs: RANGER-2606
https://issues.apache.org/jira/browse/RANGER-2606


Repository: ranger


Description
---

Added all modules to the sign-artifacts profile to fix this issue ...


Diffs (updated)
-

  pom.xml bb2e84728 


Diff: https://reviews.apache.org/r/71587/diff/2/

Changes: https://reviews.apache.org/r/71587/diff/1-2/


Testing
---

Ran it from v2.0 release codebase to check if it is able to upload as part of 
the deployment. It works!
* Also, fixed some of the TAB characters (replaced with SPACE to look nice)


Thanks,

Selvamohan Neethiraj

[REPORT] Apache Ranger - Sep-2019

[Selvamohan Neethiraj]

Apache Ranger PMC: 
 
Could you please review draft board report below and provide your feedback.
 

Thanks,
Selva-


## Description:
 - Apache Ranger is a framework to enable, monitor and manage comprehensive
   data security across the Hadoop platform

## Issues:
 - There are no issues requiring board attention at this time

## Activity:
 - Community has just released a major release - 2.0.0 and working on 2.1.0 
release.
 - Jira: has usual amount of activities in the community. +100(added)
   -72(resolved) over last 3 months

## Health report:
- Completed release of Apache Ranger 2.0.0 with major upgrade to support latest 
release of Hive, HBase and Hadoop.  
- Community is working on 2.1.0 release with
   - minor Fixes to 2.0.0 releases
   - Java 11 support
   - able to specify multiple ranger host (w/o load balancer)
   - siwtch logging framework to slf4j
 - Also, discussing new features for next major releases
   - authorization plugin for sparkSQL, ElasticSearch and Druid

## PMC changes:
 - Currently 20 PMC members
 - Sailaja Polavarapu was added to the PMC on 2019-09-18.

## Committer base changes:
 - Currently 29 committers
 - Nikhil Purbhe was added as a committer on Wed May 22 2019

## Releases:
 - Apache Ranger 2.0.0 was released on 2019-08-07.
 - Apache Ranger 1.2.0 was released on 2018-10-04.
 - Apache Ranger 1.1.0 was released on 2018-07-09.

## Mailing list activity:
 - Regular activity continues.
 - dev@ranger.apache.org:
- 1216 emails sent to list (905 in previous quarter)
 - u...@ranger.apache.org:
- 15 emails sent to list (43 in previous quarter)

## JIRA activity:
 - 100 JIRA tickets created in the last 3 months
 - 72 JIRA tickets closed/resolved in the last 3 months

[REPORT] Apache Ranger - Jan 2020

[Selvamohan Neethiraj]

All:

Here is the report for the Apache Board for the last quarter ending
Dec-2019.

Thanks,
Selva-

==>

## Description:
 - Apache Ranger is a framework to enable, monitor and manage comprehensive
   data security across the Hadoop platform

## Issues:
 - There are no issues requiring board attention at this time

## Activity:
 - Community has been working on 2.1.0 release

## Health report:
- Community is working on 2.1.0 release with
   - minor Fixes to 2.0.0 releases
   - performance improvements,
   - support for Hive 3.1.2
   - support for knox proxy for all plugins.

## PMC changes:
 - Currently 20 PMC members
 - No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.

## Committer base changes:
 - Currently 29 committers
 - No new committers. Last addition was Nikhil Purbhe on 2019-05-22.

## Releases:
 - Apache Ranger 2.0.0 was released on 2019-08-07.
 - Apache Ranger 1.2.0 was released on 2018-10-04.
 - Apache Ranger 1.1.0 was released on 2018-07-09.

## Mailing list activity:
 - Regular activity continues.
 - dev@ranger.apache.org:
    - 879 emails sent to list (1106 in previous quarter)
 - u...@ranger.apache.org:
    - 16 emails sent to list (15 in previous quarter)

## JIRA activity:
 - 65 JIRA tickets created in the last 3 months
 - 57 JIRA tickets closed/resolved in the last 3 months

[REPORT] Apache Ranger - April 2020

[Selvamohan Neethiraj]

All:

Here is the report for the Apache Board for the last quarter ending
April-2020.

Thanks,
Selva-

>

## Description:
 - Apache Ranger is a framework to enable, monitor and manage comprehensive
   data security across the Hadoop platform

## Issues:
 - There are no issues requiring board attention at this time

## Activity:
 - As we are working through the end of 2.1.0 release cycle, there are
lot of testings and bug fix activities in the community.
 - Planning activities for the next major release should begin in the
upcoming quarter along with the release of 2.1.0.

## Health report:
- Community is working on 2.1.0 release with
   - support for Documentation level authorization for Apache Solr
   - support for escrow of Apache Ranger KMS keys in external valut
   - 50+ new improvements
   - minor Fixes to 2.0.0 releases
   - support for Hive 3.1.2
   - added knox proxy support for all plugins.

## PMC changes:
 - Currently 20 PMC members
 - No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.

## Committer base changes:
 - Currently 29 committers
 - No new committers. Last addition was Nikhil Purbhe on 2019-05-22.

## Releases:
 - Apache Ranger 2.0.0 was released on 2019-08-07.
 - Apache Ranger 1.2.0 was released on 2018-10-04.
 - Apache Ranger 1.1.0 was released on 2018-07-09.

## Mailing list activity:
 - Regular activity continues.
 - dev@ranger.apache.org:
- 937 emails sent to list (833 in previous quarter)
 - u...@ranger.apache.org:
- 17 emails sent to list (23 in previous quarter)

## JIRA activity:
 - 89 JIRA tickets created in the last 3 months
 - 62 JIRA tickets closed/resolved in the last 3 months

## Commit activity:
 - 75 commits in the last 3 months
 - 19 active code contributors in the last 3 months

>

Re: [VOTE] Apache Ranger 2.1.0 rc0

[Selvamohan Neethiraj]

+1

Thanks Madhan for driving the release of Apache Ranger 2.1.0
* Downloaded source and build successfully.

Thanks,
Selva-

On 8/30/20 5:37 PM, Madhan Neethiraj wrote:
> Rangers,
> 
> Apache Ranger 2.1.0 release candidate #0 is now available for a vote within 
> dev community. Links to the release artifacts are given below. Please review 
> and vote.
> 
> The vote will be open for at least 72 hours or until necessary votes are 
> reached.
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove (and reason why)
> 
> Regards,
> Madhan
> 
> List of all issues addressed in this release: 
> https://issues.apache.org/jira/issues/?jql=project=RANGER AND status=Resolved 
> AND fixVersion=2.1.0 ORDER BY key DESC
> 
> Git tag for the release: 
> https://github.com/apache/ranger/tree/release-2.1.0-rc0
> Sources for the release: 
> https://dist.apache.org/repos/dist/dev/ranger/2.1.0-rc0/apache-ranger-2.1.0.tar.gz
> 
> Source release verification:
>   PGP Signature: 
> https://dist.apache.org/repos/dist/dev/ranger/2.1.0-rc0/apache-ranger-2.1.0.tar.gz.asc
>   SHA256 Hash:   
> https://dist.apache.org/repos/dist/dev/ranger/2.1.0-rc0/apache-ranger-2.1.0.tar.gz.sha256
>   SHA512 Hash:   
> https://dist.apache.org/repos/dist/dev/ranger/2.1.0-rc0/apache-ranger-2.1.0.tar.gz.sha512
> 
> Keys to verify the signature of the release artifacts are available at: 
> https://dist.apache.org/repos/dist/release/ranger/KEYS
> 
> New features/enhancements:
>   - Hive plugin enhancement to authorize based on database/table owners
>   - Solr plugin enhancement to support document level authorization
>   - Kafka plugin enhancement to support authorization on consumer-groups
>   - Presto plugin enhancements to support row-filtering and column-masking
>   - Atlas plugin enhancements to support authorization for new operations and 
> resources
>   - Plugins enhancement to support Ranger HA without requiring a load-balancer
>   - Plugins enhancements to support incremental tag updates
>   - Plugins enhancements to support super-users and super-groups
>   - Plugins enhancements to support audit excluded-users
>   - Added support for Elastic Search as audit store
>   - Ranger Admin UI improvements
>   - Performance improvement in bulk create/update of policies
>   - Ranger KMS enhancement to support Azure Key Vault
>   - Java client library to access Ranger REST APIs
>   - Python client library to access Ranger REST APIs
>   - Added docker setup to build, deploy Apache Ranger along with Ranger 
> authorization enabled HDFS/YARN/HBase/Kafka services
>   - updated versions of dependent libraries/components
> 
> 
> 

Re: Review Request 72778: RANGER-2927: added packaging for Python client

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72778/#review221601
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Aug. 16, 2020, 12:39 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72778/
> ---
> 
> (Updated Aug. 16, 2020, 12:39 p.m.)
> 
> 
> Review request for ranger, Abhishek  Kumar, Don Bosco Durai, Abhay Kulkarni, 
> Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2927
> https://issues.apache.org/jira/browse/RANGER-2927
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Added packaging for Python client. Once Ranger Python client is registered 
> with pypi.org, users can access the library with the following:
>  $ pip install apache-ranger
>  $ python3 -q
> >>> from apache_ranger.client.ranger_client import RangerClient
> >>> client = RangerClient('http://localhost:6180', 'username', 'password')
> >>> client.get_policies_in_service('prod_hive')
> 
> 
> Diffs
> -
> 
>   intg/src/main/python/LICENSE PRE-CREATION 
>   intg/src/main/python/README.md PRE-CREATION 
>   intg/src/main/python/__init__.py  
>   intg/src/main/python/ranger/client/__init__.py  
>   intg/src/main/python/ranger/client/ranger_client.py 319261d82 
>   intg/src/main/python/ranger/model/__init__.py  
>   intg/src/main/python/ranger/model/grant_revoke_role_request.py  
>   intg/src/main/python/ranger/model/ranger_base.py  
>   intg/src/main/python/ranger/model/ranger_policy.py 9195f4b79 
>   intg/src/main/python/ranger/model/ranger_role.py aa0521639 
>   intg/src/main/python/ranger/model/ranger_security_zone.py 40a52093f 
>   intg/src/main/python/ranger/model/ranger_service.py 637c38f1b 
>   intg/src/main/python/ranger/model/ranger_service_def.py 8cd47570f 
>   intg/src/main/python/setup.py PRE-CREATION 
>   intg/src/main/resources/logging.conf  
>   ranger-examples/sample-client/src/main/python/sample_client.py 7ff6e709b 
> 
> 
> Diff: https://reviews.apache.org/r/72778/diff/1/
> 
> 
> Testing
> ---
> 
> Registered Ranger Python client with test.pypi.org, and verified that the 
> library could be installed and accessed with:
> 
>   $ pip install -i https://test.pypi.org/simple/ apache-ranger-madhan==0.0.5
>   $ python3 -q
> >>> from apache_ranger.client.ranger_client import RangerClient
> >>> client = RangerClient('http://localhost:6180', 'username', 'password')
> >>> client.get_policies_in_service('prod_hive')
>  
>  $ python3 -q src/main/python/sample_client.py --url https://localhost:6182 
> --username username --password password
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 72795: RANGER-2960: Dockerfile to build Apache Ranger

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72795/#review221680
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Aug. 21, 2020, 2:41 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72795/
> ---
> 
> (Updated Aug. 21, 2020, 2:41 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Mehul Parikh, 
> Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2960
> https://issues.apache.org/jira/browse/RANGER-2960
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Added a docker file and script to build Ranger in a container that runs 
> Ubuntu. The docker file supports following volumns:
>  - .m2: if provided, build uses the give .m2 directory, which can help 
> avoid large downloads
>  - dist:archives from the build will be copied into this volumn
>  - scripts: build scripts in the local directory will be made available in 
> the container
> 
> 
> Diffs
> -
> 
>   dev-support/ranger-docker/.dockerignore PRE-CREATION 
>   dev-support/ranger-docker/.gitignore PRE-CREATION 
>   dev-support/ranger-docker/Dockerfile.build-ubuntu PRE-CREATION 
>   dev-support/ranger-docker/README.md PRE-CREATION 
>   dev-support/ranger-docker/scripts/ranger-build.sh PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/72795/diff/4/
> 
> 
> Testing
> ---
> 
> Using the instructions in README.md, successfully created docker image 
> 'ranger-build-ubuntu', and built latest master branch with a container of the 
> created image.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Review Request 72796: RANGER-2958: modified docker build to fix ranger build issues - fixed to install new version of maven, jdk, python"

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72796/
---

Review request for ranger, Don Bosco Durai, Madhan Neethiraj, and Velmurugan 
Periasamy.


Bugs: RANGER-2958
https://issues.apache.org/jira/browse/RANGER-2958


Repository: ranger


Description
---

Fixed build script - was using centos with older version of maven,jdk, ; 
fixed to install new version of maven, jdk, python


Diffs
-

  build_ranger_using_docker.sh cf8cf1329 


Diff: https://reviews.apache.org/r/72796/diff/1/


Testing
---

Tested on my Mac and is able to build successfully.
Commands to run:
$ docker images  | grep ranger_dev
$ docker rmi ranger_dev
$ ./build_ranger_using_docker.sh


Thanks,

Selvamohan Neethiraj

Re: Review Request 72797: RANGER-2961: Docker setup to run Ranger admin

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72797/#review221685
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Aug. 23, 2020, 12:37 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72797/
> ---
> 
> (Updated Aug. 23, 2020, 12:37 a.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Kishor Gollapalliwar, Abhay 
> Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
> Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2961
> https://issues.apache.org/jira/browse/RANGER-2961
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> - added docker files and instructions to run Ranger Admin and its dependent 
> services (PostgreSQL, Solr) in containers
> - added docker-compose files to build and deploy Apache Ranger in containers
> 
> 
> Diffs
> -
> 
>   dev-support/ranger-docker/.dockerignore 72e8ffc0d 
>   dev-support/ranger-docker/.gitignore a375c4c92 
>   dev-support/ranger-docker/Dockerfile.ranger-base-ubuntu 19cf4f0cf 
>   dev-support/ranger-docker/Dockerfile.ranger-build PRE-CREATION 
>   dev-support/ranger-docker/Dockerfile.ranger-build-ubuntu 54b750fb3 
>   dev-support/ranger-docker/README.md 90c63bb6e 
>   dev-support/ranger-docker/config/solr-ranger_audits/managed-schema 
> PRE-CREATION 
>   dev-support/ranger-docker/config/solr-ranger_audits/solrconfig.xml 
> PRE-CREATION 
>   dev-support/ranger-docker/dist/.gitignore PRE-CREATION 
>   dev-support/ranger-docker/docker-compose.ranger-build.yml PRE-CREATION 
>   dev-support/ranger-docker/docker-compose.ranger.yml PRE-CREATION 
>   dev-support/ranger-docker/scripts/ranger-admin-install.properties 
> PRE-CREATION 
>   dev-support/ranger-docker/scripts/ranger-build.sh a89ea2aa1 
>   dev-support/ranger-docker/scripts/ranger.sh PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/72797/diff/2/
> 
> 
> Testing
> ---
> 
> Build and deployed Ranger with following commands:
>  docker-compose -f docker-compose.ranger-build.yml up
>  docker-compose -f docker-compose.ranger.yml up -d
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Apache Ranger - Release 2.1.0 - release date soon ?

[Selvamohan Neethiraj]

All Rangers:

Currently we have around 316 issues resolved in Version 2.1.0.

Can we quickly do a release of version 2.1.0 ?

Any PMC member or committer interested in being a release coordinator
for Ranger Release 2.1.0 ?

Thanks,
Selva-

[REPORT] Apache Ranger - Quarterly Report - Period ending Jul-2020

[Selvamohan Neethiraj]

All:

Here is the report for the Apache Board for the last quarter ending
Jul-2020.

Thanks,
Selva-

=

## Description:
 - Apache Ranger is a framework to enable, monitor and manage comprehensive
   data security across the Hadoop platform

## Issues:
 - There are no issues requiring board attention at this time

## Activity:
 - Completed the coding and testing activities on version 2.1.0 and
initiated a process to kick-off the release of 2.1.0 and the release
should go to the community within a month.
 - Migration of build process to the new infrastructure (ci-builds.a.o)
has been completed.
 - As the ranger dev community is growing, we see more JIRA(s) are being
created by non-committers (60% by non-committers)
   - 80 by non-committers, 53 by committers
 - Also, significant amount of JIRA(s) are being resolved by
non-committers (35%)
   - 34 by non-committers, 62 by committers

## Health report:
- Community is working on 2.1.0 release
- Significant work is being done by new/non-committers and should be
getting more committers to the projects

## PMC changes:
 - Currently 20 PMC members
 - No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.

## Committer base changes:
 - Currently 29 committers
 - No new committers. Last addition was Nikhil Purbhe on 2019-05-22.

## Releases:
 - Apache Ranger 2.0.0 was released on 2019-08-07.
 - Apache Ranger 1.2.0 was released on 2018-10-04.
 - Apache Ranger 1.1.0 was released on 2018-07-09.

## Mailing list activity:
 - Regular activity continues.
 - dev@ranger.apache.org:
- 1237 emails sent to list in the last 3 months (+36%)
 - u...@ranger.apache.org:
- 13 emails sent to list in the last 3 months (-24%)

## JIRA activity:
 - 116 JIRA tickets created in the last 3 months (+17%)
 - 113 JIRA tickets closed/resolved in the last 3 months (+39%)

## Commit activity:
 - 90 commits in the last 3 months (+9%)
 - 21 active code contributors in the last 3 months (+5%)

=

Review Request 72705: RANGER-2907: modified to use default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72705/
---

Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Pradeep Agrawal, 
Ramesh Mani, and Velmurugan Periasamy.


Bugs: RANGER-2907
https://issues.apache.org/jira/browse/RANGER-2907


Repository: ranger


Description
---

When the policymgr-ssl.xml does not have trustmanager file info, currently it 
fails with an assertion failure. Added to get default JVM trustmanager when the 
trustmanager is not specified for ranger-policymgr-ssl.xml file.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTClient.java 
1c02d3d35 


Diff: https://reviews.apache.org/r/72705/diff/1/


Testing
---

tested locally on linux box with no ranger-policymgr-ssl.xml entries.


Thanks,

Selvamohan Neethiraj

Re: Review Request 73674: RANGER-2994 : kylin library specified in the ranger pom.xml is no longer available for build and is failing (unless it is already download) - is fixed

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73674/
---

(Updated Oct. 30, 2021, 4:27 a.m.)


Review request for ranger, Madhan Neethiraj, Ramesh Mani, and Velmurugan 
Periasamy.


Bugs: RANGER-2994
https://issues.apache.org/jira/browse/RANGER-2994


Repository: ranger


Description (updated)
---

kylin version is upgraded from 2.6.4 to 3.1.2


Diffs
-

  pom.xml 2937f0894 


Diff: https://reviews.apache.org/r/73674/diff/1/


Testing
---

After applying patch, I was succesfully able to build the ranger.


Thanks,

Selvamohan Neethiraj

Review Request 73674: RANGER-2994 : kylin library specified in the ranger pom.xml is no longer available for build and is failing (unless it is already download) - is fixed

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73674/
---

Review request for ranger, Madhan Neethiraj, Ramesh Mani, and Velmurugan 
Periasamy.


Bugs: RANGER-2994
https://issues.apache.org/jira/browse/RANGER-2994


Repository: ranger


Description
---

kylin version is upgraded from 2.6.4 to 3.12


Diffs
-

  pom.xml 2937f0894 


Diff: https://reviews.apache.org/r/73674/diff/1/


Testing
---

After applying patch, I was succesfully able to build the ranger.


Thanks,

Selvamohan Neethiraj

Re: Review Request 73775: RANGER-3560: Upgrade kylin version to 2.6.6

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73775/#review223943
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Dec. 22, 2021, 10:50 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73775/
> ---
> 
> (Updated Dec. 22, 2021, 10:50 a.m.)
> 
> 
> Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
> Kulkarni, Madhan Neethiraj, Mehul Parikh, Ramesh Mani, Selvamohan Neethiraj, 
> Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3560
> https://issues.apache.org/jira/browse/RANGER-3560
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> kylin version can be upgraded from 2.6.4 to 2.6.6
> 
> **Note:** If calcite libraries are removed from ~/.m2/repository/ then ranger 
> build fails, as dependent library calcite-linq4j version 1.16.0-kylin-r2 is 
> no more available. hence available library version 1.16.0 can be used. 
> calcite-linq4j is required during compile time only and will not be shipped.
> 
> Please refer RANGER-2994 and RANGER-2999 for more details about the build 
> failure.
> 
> 
> Diffs
> -
> 
>   plugin-kylin/pom.xml 9e6b0c970 
>   pom.xml f9c46f669 
>   ranger-kylin-plugin-shim/pom.xml 65410fd5d 
> 
> 
> Diff: https://reviews.apache.org/r/73775/diff/1/
> 
> 
> Testing
> ---
> 
> I am able to build ranger successfully with this patch.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 74582: RANGER-4398: security-zone API enhancements to support incremental updates and resource pagination

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74582/#review225749
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Sept. 8, 2023, 12:28 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74582/
> ---
> 
> (Updated Sept. 8, 2023, 12:28 p.m.)
> 
> 
> Review request for ranger, Anand Nadar, Abhay Kulkarni, Mehul Parikh, Monika 
> Kachhadiya, Pradeep Agrawal, Ramesh Mani, Subhrat Chaudhary, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-4398
> https://issues.apache.org/jira/browse/RANGER-4398
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> - updated RangerSecurityZone with additional of following fields for each 
> resource: id, createdBy/Time, updatedBy/Time
> - introduced RangerSecurityZoneV2, a wrapper over RangerSecurityZone, to 
> support partial updates
> - added following REST APIs and corresponding Python APIs:
> -- POST   /service/public/v2/api/zones-v2
> -- PUT/service/public/v2/api/zones-v2/{id}
> -- PUT/service/public/v2/api/zones-v2/{id}/partial
> -- GET/service/public/v2/api/zones-v2
> -- GET/service/public/v2/api/zones-v2/name/{name}
> -- GET/service/public/v2/api/zones-v2/{id}
> -- GET/service/public/v2/api/zones-v2/name/{name}/resources/{serviceName}
> -- GET/service/public/v2/api/zones-v2/{id}/resources/{serviceName}
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPrincipal.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerSecurityZone.java
>  71d64ca83 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerSecurityZoneV2.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerSecurityZoneHelper.java
>  PRE-CREATION 
>   intg/src/main/python/apache_ranger/client/ranger_client.py 484a42128 
>   intg/src/main/python/apache_ranger/model/ranger_base.py 2111534d0 
>   intg/src/main/python/apache_ranger/model/ranger_principal.py PRE-CREATION 
>   intg/src/main/python/apache_ranger/model/ranger_security_zone.py 6faa15744 
>   intg/src/main/python/setup.py 0a4b1c66e 
>   ranger-examples/sample-client/src/main/python/security_zone_v2.py 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/rest/PublicAPIsv2.java 
> cd906ed22 
>   security-admin/src/main/java/org/apache/ranger/rest/SecurityZoneREST.java 
> 55d6aaac5 
> 
> 
> Diff: https://reviews.apache.org/r/74582/diff/4/
> 
> 
> Testing
> ---
> 
> - verified that new REST APIs work correctly using Python scripts (included 
> in this patch)
> - verified that all existing tests pass successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74597: RANGER-4403: security-zone validation updated to prevent duplicate resource entries

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74597/#review225750
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Sept. 11, 2023, 8:08 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74597/
> ---
> 
> (Updated Sept. 11, 2023, 8:08 p.m.)
> 
> 
> Review request for ranger, Anand Nadar, Abhay Kulkarni, Mehul Parikh, Monika 
> Kachhadiya, Pradeep Agrawal, Ramesh Mani, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4403
> https://issues.apache.org/jira/browse/RANGER-4403
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> updated security zone validation to prevent duplicate resource entries
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/errors/ValidationErrorCode.java
>  d8c214c0f 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicyResourceSignature.java
>  c14811867 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerSecurityZoneValidator.java
>  970055511 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/model/validation/RangerSecurityZoneValidatorTest.java
>  1a1c30517 
> 
> 
> Diff: https://reviews.apache.org/r/74597/diff/1/
> 
> 
> Testing
> ---
> 
> - added unit tests
> - verified that all existing tests pass successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

[DRAFT][REPORT] Apache Ranger - Quarterly period ending August 2023

[Selvamohan Neethiraj]

Rangers:

Here is the board report of Apache Ranger for the period, Quarter ending 
August-31-2023:


Please review and let me know if you want me to add/change anything.
Thanks,
Selva-


## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive 
data

security - consistently across various data processing services.

## Issues:
There are no issues requiring board attention at this time

## Membership Data:
- Apache Ranger was founded 2017-01-17 (6 years ago).
- There are 32 committers and 18 PMC members in this project.
- The Committer-to-PMC ratio is roughly 8:5.

##Community changes, past quarter:
- No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.
- Last addition to Committer was Dineshkumar Yadav on 2023-02-06.
- One PMC member has resigned (Allan Gates) on 2023-04-05.

## Project Activity:
- Working on ranger 3.0.0 version features and bugfixes.
- Updated ranger website with new look and feel.
- Working to move ranger docs (ranger website content) from ranger 
source repo to ranger-site repo.
- Generally, less activities in the community after our 2.4.0 release; 
After we publish the release plan for 3.0.0, community activities will 
increase.


## Community Health:
-1105 emails in dev@ranger.apache.org in this quarter  (-26% change from 
past quarter)
-   7 emails in u...@ranger.apache.org in this quarter (-59% change from 
past quarter)
- 112 issues opened in JIRA in this quarter(-16% change from 
past quarter)
-  78 issues closed in JIRA in this quarter(-30% change from 
past quarter)
-  92 commits in this  quarter (-46% change from 
past quarter)
-  22 code contributors in this quarter(-26% change from 
past quarter)
-  16 PRs opened on GitHub in this quarter (-50% change from 
past quarter)
-  10 PRs closed on GitHub in this quarter (-58% change from 
past quarter)


## Most Recent releases:
- Apache Ranger 2.4.0 was released on 2023-03-30
- Apache Ranger 2.3.0 was released on 2022-07-06
- Apache Ranger 2.2.0 was released on 2021-11-01

Re: Review Request 74722: RANGER-4516: moved getResourceACLs() implementation from RangerPolicyEngine to RangerPolicyEvaluator

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74722/#review225948
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Nov. 7, 2023, 8:06 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74722/
> ---
> 
> (Updated Nov. 7, 2023, 8:06 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Kishor 
> Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Monika Kachhadiya, Pradeep 
> Agrawal, Ramesh Mani, Selvamohan Neethiraj, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4516
> https://issues.apache.org/jira/browse/RANGER-4516
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> updated getResourceACLs() implementation to move evaluator specific code from 
> RangerPolicyEngine to RangerPolicyEvaluator
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyEngineImpl.java
>  12f8a1705 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerAbstractPolicyEvaluator.java
>  5650b9ea8 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerPolicyEvaluator.java
>  0d4886c57 
> 
> 
> Diff: https://reviews.apache.org/r/74722/diff/1/
> 
> 
> Testing
> ---
> 
> - verified that all exists unit tests pass successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: [VOTE] Release Apache Ranger version 2.3.0 - rc3

[Selvamohan Neethiraj]

+1

 * verified signature
 * Builds successfully

Thanks Ramesh for driving the release.

Selva-

On 6/25/22 3:00 AM, Ramesh Mani wrote:

Dear Rangers,

Apache Ranger 2.3.0 release candidate #3 is now available for 
a vote within the dev community. Links to the release artifacts are 
given below. Please review and vote.


The vote will be open for at least 72 hours or until 
necessary votes are reached.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)

Thanks,
Ramesh

List of all issues / improvements addressed in this release:
https://issues.apache.org/jira/issues/?jql=project=RANGER AND 
status=Resolved AND fixVersion=2.3.0 ORDER BY key DESC


Git tag for the release: 
https://github.com/apache/ranger/tree/release-2.3.0-rc3


Sources for the release: 
https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc3/apache-ranger-2.3.0.tar.gz


Source release verification:
  PGP Signature: 
https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc3/apache-ranger-2.3.0.tar.gz.asc
  SHA256 Hash: 
https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc3/apache-ranger-2.3.0.tar.gz.sha256
  SHA512 Hash: 
https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc3/apache-ranger-2.3.0.tar.gz.sha512


Keys to verify the signature of the release artifacts are available 
at: https://dist.apache.org/repos/dist/release/ranger/KEYS


New features/enhancements:

RANGER-2846 Add support for resource[volume, bucket, key] look up in 
ozone plugin

RANGER-2967 Add support for Amazon CloudWatch Logs as an Audit Store
RANGER-3023 Permission tab takes longer time to load with large number 
of users and group_users data

RANGER-3030 Replace Findbugs with Spotbugs maven plugin
RANGER-3182 Prestosql is renamed to Trino
RANGER-3221 Improve logging in Presto plugin
RANGER-3276 Remove duplicate code from buildks.java
RANGER-3290 ArrayIndexOutOfBoundsException if solr is down
RANGER-3299 Upgrading the bouncycastle version for bcprov-jdk15on
RANGER-3298 Add coarse URI check for Hive Agent
RANGER-3389 Swagger UI Support for Ranger REST API
RANGER-3435 Add unique index on guid, service and zone_id column of 
x_policy table

RANGER-3439 Add rest api to get or delete ranger policy based on guid
RANGER-3455 [Logout-Ranger] Should either be disabled/ should redirect 
to knox logout page

RANGER-3459 Upgrade Ranger's Kafka dependency to 2.8
RANGER-3475 Promote TagRest endpoints to /public/v2
RANGER-3487 Update underscore js with latest version.
RANGER-3493 Add unique index on service and resource_signature column 
of x_policy table

RANGER-3498 RANGER : Remove log4j1 dependencies.
RANGER-3504 Create framework to execute DB patch dependent on Java patch.
RANGER-3510 Ranger upgrade spring framework version to 5.3.12
RANGER-3511 Create Java patch to update policy resource-signature to 
unique value.

RANGER-3512 Create Java patch to update policy guid to unique value.
RANGER-3515 Enhance Ranger Java client SSL config to be configured 
using serviceType and AppId

RANGER-3518 Limit the query size stored in Audit logs
RANGER-3521 Ranger KMS IS NOT ENFORCING HSTS ON SSL PORT DEFINED BY 
RFC 6797
RANGER-3526 policy evaluation ordering to use name as secondary 
sorting key
RANGER-3533 Provide sorting on columns throughout the audits result 
set and policy listing page.
RANGER-3538 Reduce the granularity of locking when building/retrieving 
a policy-engine within Ranger admin service

RANGER-3539 Add jacoco-maven-plugin for code coverage
RANGER-3540 Add support to read audit logs from Amazon CloudWatch
RANGER-3545 Remove Logger Checks for Info Enabled
RANGER-3548 Update performance engine test scripts
RANGER-3550 support for using user/tag attributes in row-filter 
expressions and conditions

RANGER-3551 Analyze & optimize module permissions related API
RANGER-3553 Unit test coverage for XUserMgr and UserMgr class
RANGER-3556 Ranger tagsync logs unnecessary messages
RANGER-3561 Upgrade Storm version to 1.2.4
RANGER-3562 Redesign post commit tasks for updating ref-tables when 
policy/role is updated

RANGER-3565 RangerRESTClient to support retry
RANGER-3567 support for use of user attributes in policy resources
RANGER-3569 Support Ranger KMS integration with Google cloud HSM
RANGER-3573 Add vim in docker base image
RANGER-3577 RANGER : Upgrade POI version to 5.1.0
RANGER-3578 Simplify code for policy label creation
RANGER-3580 Support Ranger KMS integration with TencentKMS
RANGER-3585 Docker setup to run Ranger usersync and tagsync
RANGER-3586 Script condition expression to support csv of group/tag 
attributes

RANGER-3595 Tar of KMS contains rubbish files
RANGER-3597 User role should not be able to modify the Policy
RANGER-3600 Ranger service tags import request failure
RANGER-3603 HDFS audit files rollover improvement to trigger rollover 
in monitoring thread

RANGER-3605 Support macros in row-filter/condition expressions
RANGER-3606 remove unnecessary static members from plugin class loaders
RANGER-3609 option to add user group enricher 

Re: Review Request 74099: RANGER-3866 : Docker based build script fails due to incorrect maven link and other script issues.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74099/
---

(Updated Aug. 24, 2022, 11:23 p.m.)


Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Ramesh Mani, and 
Velmurugan Periasamy.


Changes
---

Updated diff file after removing some debug code.


Bugs: RANGER-3866
https://issues.apache.org/jira/browse/RANGER-3866


Repository: ranger


Description
---

Restructured to have its own Dockerfile and also updated centos, maven versions 
to latest.


Diffs (updated)
-

  Dockerfile PRE-CREATION 
  build_ranger_using_docker.sh 9aadfb5f72d2662eff648c52ec6e7df52d7d2e12 
  docker-mvn.sh PRE-CREATION 


Diff: https://reviews.apache.org/r/74099/diff/2/

Changes: https://reviews.apache.org/r/74099/diff/1-2/


Testing
---

Tested on Ubuntu Docker and also on Mac M2 Docker.

I am able to build ranger without any issue after applying the patch.


Thanks,

Selvamohan Neethiraj

Review Request 74099: RANGER-3866 : Docker based build script fails due to incorrect maven link and other script issues.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74099/
---

Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Ramesh Mani, and 
Velmurugan Periasamy.


Bugs: RANGER-3866
https://issues.apache.org/jira/browse/RANGER-3866


Repository: ranger


Description
---

Restructured to have its own Dockerfile and also updated centos, maven versions 
to latest.


Diffs
-

  Dockerfile PRE-CREATION 
  build_ranger_using_docker.sh 9aadfb5f7 
  docker-mvn.sh PRE-CREATION 


Diff: https://reviews.apache.org/r/74099/diff/1/


Testing
---

Tested on Ubuntu Docker and also on Mac M2 Docker.

I am able to build ranger without any issue after applying the patch.


Thanks,

Selvamohan Neethiraj

Re: Review Request 74153: RANGER-3796: updated policy change logs to handle additionalResources field

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74153/#review224752
---



Reviewed ; Ship It!

- Selvamohan Neethiraj


On Oct. 3, 2022, 3:33 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74153/
> ---
> 
> (Updated Oct. 3, 2022, 3:33 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Kishor Gollapalliwar, Abhay 
> Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, 
> Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3796
> https://issues.apache.org/jira/browse/RANGER-3796
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Updated policy change logs to handle additionalResources field
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java
>  92aaaebdc 
> 
> 
> Diff: https://reviews.apache.org/r/74153/diff/1/
> 
> 
> Testing
> ---
> 
> - validated that admin audits generated during policy create/update captures 
> changes in policy.additionalResources
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74153: RANGER-3796: updated policy change logs to handle additionalResources field

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74153/#review224753
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Oct. 3, 2022, 3:33 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74153/
> ---
> 
> (Updated Oct. 3, 2022, 3:33 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Kishor Gollapalliwar, Abhay 
> Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, 
> Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3796
> https://issues.apache.org/jira/browse/RANGER-3796
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Updated policy change logs to handle additionalResources field
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java
>  92aaaebdc 
> 
> 
> Diff: https://reviews.apache.org/r/74153/diff/1/
> 
> 
> Testing
> ---
> 
> - validated that admin audits generated during policy create/update captures 
> changes in policy.additionalResources
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74155: RANGER-3941: optimize cache refresh in RangerUserStoreCache

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74155/#review224754
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Oct. 4, 2022, 6:36 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74155/
> ---
> 
> (Updated Oct. 4, 2022, 6:36 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Kishor Gollapalliwar, Abhay 
> Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, 
> Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3941
> https://issues.apache.org/jira/browse/RANGER-3941
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> updated RangerUserStoreCache to load from database only if cached version is 
> different from the version in the database
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerUserStore.java
>  97e05d150 
>   security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java 04968ecc5 
>   
> security-admin/src/main/java/org/apache/ranger/common/RangerUserStoreCache.java
>  fd53bae45 
>   security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java 
> 2b9df4946 
>   security-admin/src/test/java/org/apache/ranger/biz/TestXUserMgr.java 
> 5ebd42eef 
> 
> 
> Diff: https://reviews.apache.org/r/74155/diff/2/
> 
> 
> Testing
> ---
> 
> - verified that RangerUserStoreCache refreshes its cache only when the cached 
> version is different from the database
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Add me to Apache Ranger Community

[Selvamohan Neethiraj]

Thanks Himanshu for interest in Apache Ranger Contribution.

To add you as a contributor, please create a JIRA account in Apache JIRA 
(https://issues.apache.org/jira/) and provide your login name to JIRA 
system.


Thanks,
Selva-


On 12/26/22 9:55 AM, Himanshu Maurya wrote:

Hi Team,

I would like to contribute to the Apache Ranger project, Can you please add
me as a contributor to the project?

Github Username: himanshumaurya09876

Re: Review Request 74259: RANGER-3998: Support Ranger KMS integration with AWS KMS

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74259/#review225026
---




kms/scripts/install.properties
Lines 135 (patched)
<https://reviews.apache.org/r/74259/#comment313826>

Please remove the actual credential from here and provide comments as how 
it needs to be filled in. The credential seems to be actual AWS keys and works 
when I issue aws cli command to list-keys.


- Selvamohan Neethiraj


On Dec. 19, 2022, 2:49 a.m., Kirby Zhou wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74259/
> ---
> 
> (Updated Dec. 19, 2022, 2:49 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Gautam Borad, 
> Jayendra Parab, Kishor Gollapalliwar, Abhay Kulkarni, Mateen Mansoori, Mehul 
> Parikh, Pradeep Agrawal, VaradreawiZTV VaradreawiZTV, Vishal Suvagia, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: ranger-3998
> https://issues.apache.org/jira/browse/ranger-3998
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> AWS KMS is widely used by many customers.
> Therefore, RangerKMS should support hosting MasterKey to AWS KMS.
> 
> 
> Diffs
> -
> 
>   distro/src/main/assembly/kms.xml 4b4a2ac8e 
>   kms/config/kms-webapp/dbks-site.xml 258d331d8 
>   kms/pom.xml e97b993d7 
>   kms/scripts/install.properties 0e5da3c75 
>   kms/scripts/setup.sh f723e09bb 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerAWSKMSProvider.java 
> PRE-CREATION 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStoreProvider.java 
> cb5739f61 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/RangerTencentKMSProvider.java 
> 1f0125967 
> 
> 
> Diff: https://reviews.apache.org/r/74259/diff/4/
> 
> 
> Testing
> ---
> 
> Tested under macos-13 and centos-8
> 
> 
> Thanks,
> 
> Kirby Zhou
> 
>

Re: Add me to Apache Ranger Community

[Selvamohan Neethiraj]

Hi,

I see that your Jira ID is already added as a Contributor to the Apache 
Ranger JIRA system.

Please let me know if you have any trouble in assigning Ranger JIRA to you.

Thanks,
Selva-

On 12/27/22 6:17 AM, KirbY ZhoU wrote:


Please add me by the way.
My Jira ID is kirbyzhou.


在 2022/12/27 14:10，“Selvamohan Neethiraj”mailto:sneet...@apache.org>> 写入:


Thanks Himanshu for interest in Apache Ranger Contribution.


To add you as a contributor, please create a JIRA account in Apache JIRA
(https://issues.apache.org/jira/ <https://issues.apache.org/jira/>) and provide 
your login name to JIRA
system.


Thanks,
Selva-




On 12/26/22 9:55 AM, Himanshu Maurya wrote:

Hi Team,

I would like to contribute to the Apache Ranger project, Can you please add
me as a contributor to the project?

Github Username: himanshumaurya09876

Re: Add me to Apache Ranger Community

[Selvamohan Neethiraj]

Hi,

Welcome to Apache Ranger developer Community.

Your JIRA id has been added as a Contributor to the Apache Ranger. You 
can use the following link to get quick understanding on how to 
contribute to Apache Ranger: https://cwiki.apache.org/confluence/x/jIpJAw


Also, you can post your questions here <mailto:dev@ranger.apache.org> to 
get Apache Ranger Community help!


Thanks,
Selva-

On 12/27/22 1:44 AM, Himanshu Maurya wrote:

Hi Selvamohan Neethiraj,

Thank you for your email.
Apache Jira Username - hmaurya
GitHub Username - himanshumaurya09876

Thanks & Regards

On Tue, 27 Dec, 2022, 11:40 am Selvamohan Neethiraj, 
 wrote:


Thanks Himanshu for interest in Apache Ranger Contribution.

To add you as a contributor, please create a JIRA account in
Apache JIRA
(https://issues.apache.org/jira/) and provide your login name to JIRA
system.

Thanks,
Selva-


On 12/26/22 9:55 AM, Himanshu Maurya wrote:
> Hi Team,
>
> I would like to contribute to the Apache Ranger project, Can you
please add
> me as a contributor to the project?
>
> Github Username: himanshumaurya09876
>

Re: Assignment to open Ranger Jira tickets submitted

[Selvamohan Neethiraj]

Neil,

As requested, these two JIRAs have been assigned to you.

Thanks,
Selva-

On 12/20/22 2:07 PM, Neil Joshi wrote:

Hi all,

I'm an Apache Ozone committer that has submitted a few Ranger Jiras to
support the ozone ranger plugin and integration.  I would like to be
assigned those tickets,

Jiras: RANGER-3922 and RANGER-3896

Username: Neil Joshi

Please assign these tickets to me, Neil Joshi.

Thanks!  Look forward to contributing to the Ranger community.

Best Regards,
Neil
Neil Joshi
ne...@apache.org

Re: Request to be a contributor in Apache Ranger

[Selvamohan Neethiraj]

To add you as a contributor, please create a JIRA account in Apache JIRA 
https://issues.apache.org/jira/ and provide your login name to JIRA

system.

Thanks,
Selva-

On 12/22/22 4:03 AM, Sanket Shelar wrote:

Hi Team,

I would like to contribute to the Apache Ranger project, Can you please add
me as a contributor to the project?

Github Username: sanket-shelar-dev

Thanks
Sanket Shelar

Re: Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/
---

(Updated Dec. 16, 2022, 11:37 a.m.)


Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
and Velmurugan Periasamy.


Bugs: RANGER-4017
https://issues.apache.org/jira/browse/RANGER-4017


Repository: ranger


Description
---

RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
by executing a single command (& within few minutes)


Diffs
-

  README.txt fce972ab1 
  ranger_in_docker PRE-CREATION 


Diff: https://reviews.apache.org/r/74253/diff/1/


Testing
---

Tested the script in Mac (M2) and Linux (Ubundu) 
Documented the execution steps in README.txt


File Attachments (updated)


Added another Patch to address KMS start and Ranger build using Docker
  
https://reviews.apache.org/media/uploaded/files/2022/12/16/951fd94c-c528-4ec5-a6ec-4e2b905b411f__0001-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch


Thanks,

Selvamohan Neethiraj

Re: Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

> On Dec. 15, 2022, 12:32 a.m., Madhan Neethiraj wrote:
> > ranger_in_docker
> > Lines 132 (patched)
> > <https://reviews.apache.org/r/74253/diff/1/?file=2272801#file2272801line132>
> >
> > How about leveraging docker to build Ranger as well, using the 
> > following command?
> >   docker-compose -f docker-compose.ranger-base.yml -f 
> > docker-compose.ranger-build.yml up

Addressed in the 2nd patch.


> On Dec. 15, 2022, 12:32 a.m., Madhan Neethiraj wrote:
> > ranger_in_docker
> > Lines 166 (patched)
> > <https://reviews.apache.org/r/74253/diff/1/?file=2272801#file2272801line166>
> >
> > Consider deploying KMS as well, with docker-compose.ranger-kms.yml

Addressed in the 2nd patch.


- Selvamohan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/#review225000
-------


On Dec. 16, 2022, 11:37 a.m., Selvamohan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74253/
> ---
> 
> (Updated Dec. 16, 2022, 11:37 a.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4017
> https://issues.apache.org/jira/browse/RANGER-4017
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
> by executing a single command (& within few minutes)
> 
> 
> Diffs
> -
> 
>   README.txt fce972ab1 
>   ranger_in_docker PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/74253/diff/1/
> 
> 
> Testing
> ---
> 
> Tested the script in Mac (M2) and Linux (Ubundu) 
> Documented the execution steps in README.txt
> 
> 
> File Attachments
> 
> 
> Added another Patch to address KMS start and Ranger build using Docker
>   
> https://reviews.apache.org/media/uploaded/files/2022/12/16/951fd94c-c528-4ec5-a6ec-4e2b905b411f__0001-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch
> 
> 
> Thanks,
> 
> Selvamohan Neethiraj
> 
>

Re: Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/
---

(Updated Dec. 18, 2022, 4:35 p.m.)


Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
and Velmurugan Periasamy.


Bugs: RANGER-4017
https://issues.apache.org/jira/browse/RANGER-4017


Repository: ranger


Description
---

RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
by executing a single command (& within few minutes)


Diffs
-

  README.txt fce972ab1 
  ranger_in_docker PRE-CREATION 


Diff: https://reviews.apache.org/r/74253/diff/1/


Testing
---

Tested the script in Mac (M2) and Linux (Ubundu) 
Documented the execution steps in README.txt


Thanks,

Selvamohan Neethiraj

Re: Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/
---

(Updated Dec. 18, 2022, 4:38 p.m.)


Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
and Velmurugan Periasamy.


Changes
---

Added fixes to start KMS service and build using Docker.


Bugs: RANGER-4017
https://issues.apache.org/jira/browse/RANGER-4017


Repository: ranger


Description
---

RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
by executing a single command (& within few minutes)


Diffs (updated)
-

  README.txt fce972ab1b986e7f1d28cf4e35f086929cf9169a 
  dev-support/ranger-docker/Dockerfile.ranger-base 
a4bb9008ff6e0d16784e286d22ab353e26be811c 
  dev-support/ranger-docker/docker-compose.ranger-build.yml 
f0b5b05e0cb696722297a83b7a507dc954f43398 
  ranger_in_docker PRE-CREATION 


Diff: https://reviews.apache.org/r/74253/diff/2/

Changes: https://reviews.apache.org/r/74253/diff/1-2/


Testing
---

Tested the script in Mac (M2) and Linux (Ubundu) 
Documented the execution steps in README.txt


Thanks,

Selvamohan Neethiraj

Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/
---

Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
and Velmurugan Periasamy.


Bugs: RANGER-4017
https://issues.apache.org/jira/browse/RANGER-4017


Repository: ranger


Description
---

RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
by executing a single command (& within few minutes)


Diffs
-

  README.txt fce972ab1 
  ranger_in_docker PRE-CREATION 


Diff: https://reviews.apache.org/r/74253/diff/1/


Testing
---

Tested the script in Mac (M2) and Linux (Ubundu) 
Documented the execution steps in README.txt


Thanks,

Selvamohan Neethiraj

Re: Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/
---

(Updated Dec. 20, 2022, 9:43 p.m.)


Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
and Velmurugan Periasamy.


Changes
---

(1) Removed the trailing spaces and tab characters in the script. (2) provided 
an Environment variable - ENABLED_RANGER_SERVICES to optionally start services: 
tagsync,hadoop,hbase,kafka,hive,knox,kms


Bugs: RANGER-4017
https://issues.apache.org/jira/browse/RANGER-4017


Repository: ranger


Description
---

RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
by executing a single command (& within few minutes)


Diffs (updated)
-

  README.txt fce972ab1b986e7f1d28cf4e35f086929cf9169a 
  dev-support/ranger-docker/Dockerfile.ranger-base 
a4bb9008ff6e0d16784e286d22ab353e26be811c 
  dev-support/ranger-docker/docker-compose.ranger-build.yml 
f0b5b05e0cb696722297a83b7a507dc954f43398 
  ranger_in_docker PRE-CREATION 


Diff: https://reviews.apache.org/r/74253/diff/3/

Changes: https://reviews.apache.org/r/74253/diff/2-3/


Testing
---

Tested the script in Mac (M2) and Linux (Ubundu) 
Documented the execution steps in README.txt


Thanks,

Selvamohan Neethiraj

Re: Review Request 74253: This script will help anyone to setup ranger within few minutes of downloading Apache Ranger Repo.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74253/
---

(Updated Dec. 20, 2022, 9:50 p.m.)


Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
and Velmurugan Periasamy.


Changes
---

Removed trailing space and replaced TAB chars in README.txt file.


Bugs: RANGER-4017
https://issues.apache.org/jira/browse/RANGER-4017


Repository: ranger


Description
---

RANGER-4017: Able to run Apache Ranger after downloading the source from REPO 
by executing a single command (& within few minutes)


Diffs (updated)
-

  README.txt fce972ab1b986e7f1d28cf4e35f086929cf9169a 
  dev-support/ranger-docker/Dockerfile.ranger-base 
a4bb9008ff6e0d16784e286d22ab353e26be811c 
  dev-support/ranger-docker/docker-compose.ranger-build.yml 
f0b5b05e0cb696722297a83b7a507dc954f43398 
  ranger_in_docker PRE-CREATION 


Diff: https://reviews.apache.org/r/74253/diff/4/

Changes: https://reviews.apache.org/r/74253/diff/3-4/


Testing
---

Tested the script in Mac (M2) and Linux (Ubundu) 
Documented the execution steps in README.txt


Thanks,

Selvamohan Neethiraj

Re: Review Request 74255: RANGER-3978: Docker setup fixes - incorrect mysql path in KMS, incorrect service-config

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74255/#review225019
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Dec. 15, 2022, 4:14 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74255/
> ---
> 
> (Updated Dec. 15, 2022, 4:14 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Ramesh Mani, and Selvamohan 
> Neethiraj.
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> updated Docker setup to fix the following:
> - updated version of HBase and Kafka to be in sync with pom.xml
> - fixed docker build image to recognize PROFILE in .env
> - incorrect mysql path in KMS setup
> - updated READMe.md to include KMS in docker command to build and run
> - incorrect service config for Hive, HBase and Knox services
> 
> 
> Diffs
> -
> 
>   dev-support/ranger-docker/.env 020798132 
>   dev-support/ranger-docker/Dockerfile.ranger-kms 4cf8b9d73 
>   dev-support/ranger-docker/README.md e18b0e7ff 
>   dev-support/ranger-docker/docker-compose.ranger-build.yml f0b5b05e0 
>   dev-support/ranger-docker/scripts/create-ranger-services.py 1b2bcafd2 
> 
> 
> Diff: https://reviews.apache.org/r/74255/diff/2/
> 
> 
> Testing
> ---
> 
> verified that docker build completes successfully and services startup
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74092: [RANGER-3863] Update dependencies to support macOS aarch64 M1 (Apple Silicon) environment

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74092/#review224931
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On Dec. 1, 2022, 7:20 p.m., ziyue yang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74092/
> ---
> 
> (Updated Dec. 1, 2022, 7:20 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-3863
> https://issues.apache.org/jira/browse/RANGER-3863
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> [JIRA LInk](https://issues.apache.org/jira/browse/RANGER-3863)
> 
> This Pr is to update dependencies to support macOS aarch64 devices.
> 
> We'll see the `UnsatisfiedLinkError` like below:
> 
> ```plain
> Exception in thread "main" java.lang.UnsatisfiedLinkError: 
> /Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp:
>  
> dlopen(/Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp,
>  1): no suitable image found.  Did find:
>   
> /Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp:
>  no matching architecture in universal wrapper
>   
> /Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp:
>  no matching architecture in universal wrapper
>   at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> ```
> 
> This is because the dependencies wasn't updated to the version which supports 
> M1.
> 
> Maven repo link:
> 1. [Java Native 
> Access](https://mvnrepository.com/artifact/net.java.dev.jna/jna/5.7.0), 
> [changelog](https://github.com/java-native-access/jna/blob/master/CHANGES.md#release-570)
> 2. 
> [gethostname4j](https://mvnrepository.com/artifact/com.kstruct/gethostname4j),
>  [related PR](https://github.com/mattsheppard/gethostname4j/pull/8)
> 
> 
> Diffs
> -
> 
>   pom.xml 7b0dd14c5 
>   security-admin/pom.xml 5e24dd846 
> 
> 
> Diff: https://reviews.apache.org/r/74092/diff/2/
> 
> 
> Testing
> ---
> 
> Run maven test on both intel x86 and M1 machine, succeeded
> 
> 
> Thanks,
> 
> ziyue yang
> 
>

Re: Review Request 74092: [RANGER-3863] Update dependencies to support macOS aarch64 M1 (Apple Silicon) environment

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74092/#review224928
---



This patch does not work in Apple M2. However, with the following additional 
change, I am able to successfully build on my Mac M2.

diff --git a/security-admin/pom.xml b/security-admin/pom.xml
index 5e24dd846..54bd231d8 100644
--- a/security-admin/pom.xml
+++ b/security-admin/pom.xml
@@ -928,7 +928,7 @@
 
 com.github.eirslett
 frontend-maven-plugin
-1.6
+1.12.1
 
 
${project.build.directory}
 
${project.build.directory}

- Selvamohan Neethiraj


On Aug. 22, 2022, 8:31 a.m., ziyue yang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74092/
> ---
> 
> (Updated Aug. 22, 2022, 8:31 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-3863
> https://issues.apache.org/jira/browse/RANGER-3863
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> [JIRA LInk](https://issues.apache.org/jira/browse/RANGER-3863)
> 
> This Pr is to update dependencies to support macOS aarch64 devices.
> 
> We'll see the `UnsatisfiedLinkError` like below:
> 
> ```plain
> Exception in thread "main" java.lang.UnsatisfiedLinkError: 
> /Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp:
>  
> dlopen(/Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp,
>  1): no suitable image found.  Did find:
>   
> /Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp:
>  no matching architecture in universal wrapper
>   
> /Users/USERNAME/Library/Caches/JetBrains/IntelliJIdea2020.3/tmp/jna6890631648374949923.tmp:
>  no matching architecture in universal wrapper
>   at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> ```
> 
> This is because the dependencies wasn't updated to the version which supports 
> M1.
> 
> Maven repo link:
> 1. [Java Native 
> Access](https://mvnrepository.com/artifact/net.java.dev.jna/jna/5.7.0), 
> [changelog](https://github.com/java-native-access/jna/blob/master/CHANGES.md#release-570)
> 2. 
> [gethostname4j](https://mvnrepository.com/artifact/com.kstruct/gethostname4j),
>  [related PR](https://github.com/mattsheppard/gethostname4j/pull/8)
> 
> 
> Diffs
> -
> 
>   pom.xml 8698e67e5 
> 
> 
> Diff: https://reviews.apache.org/r/74092/diff/1/
> 
> 
> Testing
> ---
> 
> Run maven test on both intel x86 and M1 machine, succeeded
> 
> 
> Thanks,
> 
> ziyue yang
> 
>

Planning for Apache Ranger 2.4.0 release

[Selvamohan Neethiraj]

Dear Ranger Community members, There are various features and critical 
bug fixes done in the Apache Ranger project since the release of Apache 
Ranger 2.3.0. Around 3 New Features, 34 improvements and 60 bug fixes 
were made from the last release. Now with that Ranger community is 
expecting a release to adapt those changes and hence planning this 
release. Please review and provide your opinion.


Thanks, Selva-

_*Improvements & New Features addressed in 2.4.0*_

Improvement,RANGER-2928,[Ranger Zone REST API] Resources data is missing 
in XML format Improvement,RANGER-3165,Upgrade Elasticsearch version in 
Ranger to Elasticsearch 7.10.2 Improvement,RANGER-3534,Review of 
RangerHiveAuditHandler Improvement,RANGER-3623,Add ability to enable 
anonymous download of policy/role/tag Improvement,RANGER-3633,Remove 
eclipse .project file from git Improvement,RANGER-3664,Ranger KMS : Add 
refresh functionality on kms key listing page. 
Improvement,RANGER-3763,The max limit of the requested entities is not 
configurable in tagsync Improvement,RANGER-3767,Add text message in HDFS 
and YARN policy pages to highlight the fallback ACL option 
Improvement,RANGER-3787,Non-daemon threads started by 
ElasticSearchAuditDestination cause Spark application hanging 
Improvement,RANGER-3794,Improve performance of delete users/groups 
utility Improvement,RANGER-3796,Enhancement to support multiple resource 
sets in a policy Improvement,RANGER-3818,Upgrade Solr to 8.11.2 
Improvement,RANGER-3822,RangerService outputs password information in 
plaintext Improvement,RANGER-3837,"Allow Ranger non-admins to get, 
create, edit and delete roles" Improvement,RANGER-3856,Ranger admin 
client option to work with non-kerberized server 
Improvement,RANGER-3865,support for using user attributes in masking 
expressions Improvement,RANGER-3900,"Roles deletion Takes time in Apache 
Ranger when there are more users,groups,roles" 
Improvement,RANGER-3902,dbLoadTime is not added correctly in 
RangerServicePoliciesCache Improvement,RANGER-3910,API Documentation is 
broken for knox sso Improvement,RANGER-3934,improve tag cache handling 
to reduce resource usage Improvement,RANGER-3940,"Add javascript 
includes(), intersects() polyfills for array prototype to 
RangerCommonConstants" Improvement,RANGER-3948,update serialization to 
skip empty values Improvement,RANGER-3951,optimize memory used for tags 
in plugins and server Improvement,RANGER-3955,optimization to reduce 
duplicate strings Improvement,RANGER-3973,LDAP incremental search not 
always available Improvement,RANGER-3978,Docker setup to run Ranger KMS 
Improvement,RANGER-3982,Python client for Ranger KMS REST APIs 
Improvement,RANGER-3983,Support getColumnMasks and getRowFilters in 
Trino SPI 376+ Improvement,RANGER-3985,Trino plugin: Check table name 
when creating tables Improvement,RANGER-3986,Upgrade trino guice 
dependency to 5.1.0 Improvement,RANGER-3988,Trino plugin should 
differntiate between views and tables Improvement,RANGER-3997,option to 
use default value when user/group/tag does not have the attribute 
Improvement,RANGER-4004,"During the service deletion also, we can clear 
the in-memory cache for that service which got deleted on the ranger 
side" Improvement,RANGER-4011,option to disable creation of default 
policies per hierarchy New Feature,RANGER-3852,Performance and 
scalability analyzer tool for Ranger New 
Feature,RANGER-3855,RangerExternalUserStoreRetriever class New 
Feature,RANGER-4028,Ranger - Upgrade bootbox.js.


_*BUGS addressed in 2.4.0*_

Bug,RANGER-2737,Ranger REST API returns different infomation when GET 
user by id and by name Bug,RANGER-3080,"A service administrator should 
be allowed to set ""excludes"" flag for a policy resource" 
Bug,RANGER-3108,NPE in RangerPolicyRepository.init 
Bug,RANGER-3387,Ranger Admin Header Validation. Bug,RANGER-3394,Too much 
`varchar(4000)` causes table to exceed ROW SIZE limit in MySQL 
Bug,RANGER-3500,Ranger policy list doesn't support sorting by field 
Bug,RANGER-3670,Policy update creates unnecessary entries in transaction 
log table Bug,RANGER-3680,mysql ErrorCode:1118 when Importing DB schema 
to database Bug,RANGER-3719,Can not create mysql table with charset 
utf8mb4. Bug,RANGER-3775,Logback.xml has been incorrectly modified by 
RANGER-3704. Bug,RANGER-3789,Upgrade Handlebars version to 4.7.7 
Bug,RANGER-3790,Ranger tagsync module should not depend on kafka server 
Bug,RANGER-3798,"Ranger API Resource Metrics REST ""Up time of JVM"" 
does not update." Bug,RANGER-3806,Group's users mapping entry failing 
whenever primary key auto-increment is not set to 1 in db 
Bug,RANGER-3807,getUserRoles API gives 200 for non existing user passed 
to this API Bug,RANGER-3813,Fix ConcurrentModificationException in 
UnixUserGroupBuilder Bug,RANGER-3814,IS_IN_ROLE(roleName) condition 
always returns false Bug,RANGER-3816,update getResourceACLs() API to 
handle macros in resource names Bug,RANGER-3819,Upgrade springframework 

Review Request 74356: RANGER-4144 : Fixing test suite for kafka plugin

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74356/
---

Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Ramesh Mani, and 
Velmurugan Periasamy.


Bugs: RANGER-4144
https://issues.apache.org/jira/browse/RANGER-4144


Repository: ranger


Description
---

Changed version of curator test version from 2.12.0 to 5.4.0 & fixed Java 
Autoboxing issues


Diffs
-

  
plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
 d24ee1e57 
  pom.xml 1e77f5191 


Diff: https://reviews.apache.org/r/74356/diff/1/


Testing
---

1. Run Unit Test (as part of build) done on Linux Platform


Thanks,

Selvamohan Neethiraj

[VOTE] Apache Ranger 2.4.0 Release - rc1

[Selvamohan Neethiraj]

Rangers:
As a critical HBase Plugin issue was identified in the earlier release 
candidate, I am posting another release candidate (rc1) details below  for VOTE.

Apache Ranger 2.4.0 release candidate #1 is now available for a vote within the 
dev community. Links to the release artifacts are given below. Please review 
and vote.

The vote will be open for at least 72 hours or until necessary votes are 
reached. 
[   ] +1 approve 
[   ] +0 no opinion 
[   ] -1 disapprove (and reason why) 

Thanks, 
Selva- 
Ranger PMC
List of issues / improvements addressed in this release:  click-here 

 Git tag for the release:
https://github.com/apache/ranger/tree/release-2.4.0-rc1
Sources for the release: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz
 Source release verification: 

PGP Signature:   
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.asc

SHA256 Hash:
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.sha256

SHA512 Hash:
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.sha512

Keys to verify the signature:   
https://dist.apache.org/repos/dist/release/ranger/KEYS

 New features/enhancements: 

Issue Type
Issue key
Summary
Improvement
RANGER-4117
service-def option to include expression condition implictly
Improvement
RANGER-4114
Consistent use of plugin property prefix in context enrichers
Improvement
RANGER-4107
Upgrade EclipseLink
Improvement
RANGER-4101
Java client update to add missing security-zone APIs
Improvement
RANGER-4100
Efficient computation of the smallest set of evaluators returned by search of 
multiple Trie trees
Improvement
RANGER-4083
Tag-based policy UI to not show permissions in deny/exception for services that 
don't support deny/exception
Improvement
RANGER-4080
Python client update to add missing security-zone APIs
Improvement
RANGER-4071
Support for LDAP/AD usernames and group names with special chars
New Feature
RANGER-4028
Ranger - Upgrade bootbox.js.
Improvement
RANGER-4024
Adding requestId as part of Ranger logs via RangerMDCFilter when the request 
header contains request-Id
Improvement
RANGER-4012
getPolicyByName searches policy by serviceName, policyName simply by traverse 
all policies in RangerServicePoliciesCache instead of DB  
Improvement
RANGER-4011
option to disable creation of default policies per hierarchy
Improvement
RANGER-4004
During the service deletion also, we can clear the in-memory cache for that 
service which got deleted on the ranger side
Improvement
RANGER-3997
option to use default value when user/group/tag does not have the attribute
Improvement
RANGER-3986
Upgrade trino guice dependency to 5.1.0
Improvement
RANGER-3983
Support getColumnMasks and getRowFilters in Trino SPI 376+
Improvement
RANGER-3982
Python client for Ranger KMS REST APIs
Improvement
RANGER-3978
Docker setup to run Ranger KMS 
New Feature
RANGER-3971
Upgrade HBASE version to 2.4.6
Improvement
RANGER-3955
optimization to reduce duplicate strings
Improvement
RANGER-3951
optimize memory used for tags in plugins and server
Improvement
RANGER-3948
update serialization to skip empty values
Improvement
RANGER-3940
Add javascript includes(), intersects() polyfills for array prototype to 
RangerCommonConstants
Improvement
RANGER-3934
improve tag cache handling to reduce resource usage
Improvement
RANGER-3910
API Documentation is broken for knox sso
Improvement
RANGER-3903
Improvement in RangerPolicyDeltaUtil--> applyDeltas method
Improvement
RANGER-3902
dbLoadTime is not added correctly in RangerServicePoliciesCache
Improvement
RANGER-3900
Roles deletion Takes time in Apache Ranger when there are more 
users,groups,roles
Improvement
RANGER-3865
support for using user attributes in masking expressions
Improvement
RANGER-3856
Ranger admin client option to work with non-kerberized server
New Feature
RANGER-3855
RangerExternalUserStoreRetriever class
New Feature
RANGER-3852
Performance and scalability analyzer tool for Ranger
Improvement
RANGER-3837
Allow Ranger non-admins to get, create, edit and delete roles
New Feature
RANGER-3828
Fine-grained Access Control over nested structures
Improvement
RANGER-3822
RangerService outputs password information in plaintext
Improvement
RANGER-3818
Upgrade Solr to 8.11.2
Improvement
RANGER-3796
Enhancement to support multiple resource sets in a policy
Improvement
RANGER-3794
Improve performance of delete users/groups utility
Improvement
RANGER-3787
Non-daemon threads started by ElasticSearchAuditDestination cause Spark 
application hanging
Improvement
RANGER-3767
Add text message in HDFS and YARN policy pages to highlight the fallback ACL 
option
Improvement
RANGER-3763
The max limit 

Re: Review Request 74362: RANGER-4154: updated usersync to populate firstName for users

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74362/#review225298
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On March 24, 2023, 6:05 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74362/
> ---
> 
> (Updated March 24, 2023, 6:05 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Kishor Gollapalliwar, Abhay 
> Kulkarni, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Subhrat 
> Chaudhary.
> 
> 
> Bugs: RANGER-4154
> https://issues.apache.org/jira/browse/RANGER-4154
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> - updated usersync to populate firstName for users
> - added missing logback libraries in usersync and tagsync modules
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java e23fe6327 
>   tagsync/pom.xml 1434e27c0 
>   ugsync-util/src/main/java/org/apache/ranger/ugsyncutil/model/XUserInfo.java 
> 2a2e01e1a 
>   ugsync/pom.xml 91af4511e 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/process/PolicyMgrUserGroupBuilder.java
>  bca833d08 
> 
> 
> Diff: https://reviews.apache.org/r/74362/diff/1/
> 
> 
> Testing
> ---
> 
> - verified that users sent by usersync are recorded in Ranger
> - verified that usersync and tagsync modules generate log files correctly
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

[VOTE] Apache Ranger 2.4.0 Release - rc0

[Selvamohan Neethiraj]

Dear Rangers:

Thanks to all of the Rangers for your dedicated efforts to reach  "2.4.0 
release" milestone for Apache Ranger.


Apache Ranger 2.4.0 release candidate #0 is now available for a vote 
within the dev community. Links to the release artifacts are given 
below. Please review and vote.


The vote will be open for at least 72 hours or until necessary votes are 
reached. [   ] +1 approve [   ] +0 no opinion [   ] -1 disapprove (and 
reason why) Thanks, Selva- Ranger PMC


List of issues / improvements addressed in this release: click-here 



Git tag for the release: 
https://github.com/apache/ranger/tree/release-2.4.0-rc0


Sources for the 
release: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc0/apache-ranger-2.4.0.tar.gz 



Source release verification: PGP 
Signature:https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc0/apache-ranger-2.4.0.tar.gz.asc


SHA256 Hash: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc0/apache-ranger-2.4.0.tar.gz.sha256 



SHA512 Hash: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc0/apache-ranger-2.4.0.tar.gz.sha512 



Keys to verify the signature of the release artifacts are available at: 
https://dist.apache.org/repos/dist/release/ranger/KEYS


_*New features/enhancements: *_

Issue Type  Issue key   Summary
Improvement 	RANGER-4117 	service-def option to include expression 
condition implictly
Improvement 	RANGER-4114 	Consistent use of plugin property prefix in 
context enrichers

Improvement RANGER-4107 Upgrade EclipseLink
Improvement 	RANGER-4101 	Java client update to add missing 
security-zone APIs
Improvement 	RANGER-4100 	Efficient computation of the smallest set of 
evaluators returned by search of multiple Trie trees
Improvement 	RANGER-4083 	Tag-based policy UI to not show permissions in 
deny/exception for services that don't support deny/exception
Improvement 	RANGER-4080 	Python client update to add missing 
security-zone APIs
Improvement 	RANGER-4071 	Support for LDAP/AD usernames and group names 
with special chars

New Feature RANGER-4028 Ranger - Upgrade bootbox.js.
Improvement 	RANGER-4024 	Adding requestId as part of Ranger logs via 
RangerMDCFilter when the request header contains request-Id
Improvement 	RANGER-4012 	getPolicyByName searches policy by 
serviceName, policyName simply by traverse all policies in 
RangerServicePoliciesCache instead of DB
Improvement 	RANGER-4011 	option to disable creation of default policies 
per hierarchy
Improvement 	RANGER-4004 	During the service deletion also, we can clear 
the in-memory cache for that service which got deleted on the ranger side
Improvement 	RANGER-3997 	option to use default value when 
user/group/tag does not have the attribute

Improvement RANGER-3986 Upgrade trino guice dependency to 5.1.0
Improvement 	RANGER-3983 	Support getColumnMasks and getRowFilters in 
Trino SPI 376+

Improvement RANGER-3982 Python client for Ranger KMS REST APIs
Improvement RANGER-3978 Docker setup to run Ranger KMS
Improvement RANGER-3955 optimization to reduce duplicate strings
Improvement 	RANGER-3951 	optimize memory used for tags in plugins and 
server

Improvement RANGER-3948 update serialization to skip empty values
Improvement 	RANGER-3940 	Add javascript includes(), intersects() 
polyfills for array prototype to RangerCommonConstants
Improvement 	RANGER-3934 	improve tag cache handling to reduce resource 
usage

Improvement RANGER-3910 API Documentation is broken for knox sso
Improvement 	RANGER-3903 	Improvement in RangerPolicyDeltaUtil--> 
applyDeltas method
Improvement 	RANGER-3902 	dbLoadTime is not added correctly in 
RangerServicePoliciesCache
Improvement 	RANGER-3900 	Roles deletion Takes time in Apache Ranger 
when there are more users,groups,roles
Improvement 	RANGER-3865 	support for using user attributes in masking 
expressions
Improvement 	RANGER-3856 	Ranger admin client option to work with 
non-kerberized server

New Feature RANGER-3855 RangerExternalUserStoreRetriever class
New Feature 	RANGER-3852 	Performance and scalability analyzer tool for 
Ranger
Improvement 	RANGER-3837 	Allow Ranger non-admins to get, create, edit 
and delete roles
New Feature 	RANGER-3828 	Fine-grained Access Control over nested 
structures
Improvement 	RANGER-3822 	RangerService outputs password information in 
plaintext

Improvement RANGER-3818 Upgrade Solr to 8.11.2
Improvement 	RANGER-3796 	Enhancement to support multiple 

Re: Review Request 74416: RANGER-4209: blog: adventures in abac - part-1

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74416/#review225426
---




docs/src/site/xdoc/blogs.xml
Lines 24 (patched)
<https://reviews.apache.org/r/74416/#comment314043>

@Madhan -  This should open in a new Tab/Window. Please add target="_blank" 
on the href to avoid closing the ranger site.


- Selvamohan Neethiraj


On April 25, 2023, 6:27 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74416/
> ---
> 
> (Updated April 25, 2023, 6:27 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Barbara Eckman, Don Bosco Durai, 
> Abhay Kulkarni, Monika Kachhadiya, Ramesh Mani, Selvamohan Neethiraj, Sailaja 
> Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4209
> https://issues.apache.org/jira/browse/RANGER-4209
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Blog exploring choices for setting up access control based on sensitivity 
> level and content of the data, and attributes of the user
> 
> 
> Diffs
> -
> 
>   docs/pom.xml 023fbbc32 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig01-policy_ussales_rib.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig02-policy_globalsales_highly_sensitive.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig03-policy_globalsales_sensitive.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig04-policy_globalsales_non_sensitive.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig05-policy_globalsales_row_filter_sales_region.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig06-roles_capturing_sl_sr.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig07-policy_ussales_tag_attribute_based.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig08-policy_tag_based_sl.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig09-policy_globalsales_row_filter_sr_roles.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig10-roles_capturing_sl_sr_sp.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig11-policy_globalsalespartners_row_filter_sr_sp.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/table_globalsales.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/table_globalsalespartners.jpg
>  PRE-CREATION 
>   docs/src/site/resources/blogs/adventures_in_abac_1.files/table_ussales.jpg 
> PRE-CREATION 
>   docs/src/site/resources/blogs/adventures_in_abac_1.html PRE-CREATION 
>   docs/src/site/site.xml 02247d478 
>   docs/src/site/xdoc/blogs.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/74416/diff/1/
> 
> 
> Testing
> ---
> 
> - Built docs directory contents using: mvn clean site:run
> - verified blogs list is rendered in localhost:8080/blogs.html
> - verified this blog is rendered in 
> http://localhost:8080/blogs/adventures_in_abac_1.html
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74416: RANGER-4209: blog: adventures in abac - part-1

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74416/#review225427
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On April 29, 2023, 1:14 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74416/
> ---
> 
> (Updated April 29, 2023, 1:14 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Barbara Eckman, Don Bosco Durai, 
> Abhay Kulkarni, Monika Kachhadiya, Ramesh Mani, Selvamohan Neethiraj, Sailaja 
> Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4209
> https://issues.apache.org/jira/browse/RANGER-4209
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Blog exploring choices for setting up access control based on sensitivity 
> level and content of the data, and attributes of the user
> 
> 
> Diffs
> -
> 
>   docs/pom.xml 023fbbc32 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig01-policy_ussales_rib.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig02-policy_globalsales_highly_sensitive.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig03-policy_globalsales_sensitive.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig04-policy_globalsales_non_sensitive.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig05-policy_globalsales_row_filter_sales_region.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig06-roles_capturing_sl_sr.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig07-policy_ussales_tag_attribute_based.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig08-policy_tag_based_sl.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig09-policy_globalsales_row_filter_sr_roles.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig10-roles_capturing_sl_sr_sp.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/fig11-policy_globalsalespartners_row_filter_sr_sp.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/table_globalsales.jpg
>  PRE-CREATION 
>   
> docs/src/site/resources/blogs/adventures_in_abac_1.files/table_globalsalespartners.jpg
>  PRE-CREATION 
>   docs/src/site/resources/blogs/adventures_in_abac_1.files/table_ussales.jpg 
> PRE-CREATION 
>   docs/src/site/resources/blogs/adventures_in_abac_1.html PRE-CREATION 
>   docs/src/site/site.xml 02247d478 
>   docs/src/site/xdoc/blogs.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/74416/diff/2/
> 
> 
> Testing
> ---
> 
> - Built docs directory contents using: mvn clean site:run
> - verified blogs list is rendered in localhost:8080/blogs.html
> - verified this blog is rendered in 
> http://localhost:8080/blogs/adventures_in_abac_1.html
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Review Request 74410: RANGER-4198: fix to do SHAPSHOT deploy for - [BUILD] [JDK11] - Added Unix Native Authenticator' as part of jdk11 profile in pom.xml.

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74410/
---

Review request for ranger, Ankita Sinha, Don Bosco Durai, Abhay Kulkarni, 
Madhan Neethiraj, Ramesh Mani, and Velmurugan Periasamy.


Bugs: RANGER-4198
https://issues.apache.org/jira/browse/RANGER-4198


Repository: ranger


Description
---

Added Unix Native Authenticator' as part of jdk11 profile in pom.xml and tested 
via ci-builds.apache.org


Diffs
-

  pom.xml a2cf8a639 


Diff: https://reviews.apache.org/r/74410/diff/1/


Testing
---

tested via 
https://ci-builds.apache.org/job/Ranger/job/ranger-master-snapshot-publish/774/


Thanks,

Selvamohan Neethiraj

[RESULT] [VOTE] Apache Ranger 2.4.0 Release - rc2

[Selvamohan Neethiraj]

Dear Rangers,

Thanks for taking time to verify, giving the feedback and voting on Apache 
Ranger 2.4.0 release candidate #2.

More than 72 hours have passed since the email to VOTE for the release; the 
vote is now closed. 

The vote passes with Nineteen(19)  +1 votes & no 0 vote & no  -1 vote.

Here are the vote details:

Seven  +1 votes from the following PMC members:
- Alok Lal
- Balaji Ganesan
- Don Bosco Durai
- Madhan Neethiraj
- Ramesh Mani
- Selvamohan Neethiraj
- Velmurugan Periasamy

Twelve  +1 votes from the following committers/contributors:
- Ankita Sinha
- Bhavik Patel
- Nitin Galave
- Mehul Parikh
- Dharmesh Makwana
- Jai Patel
- KirbY ZhoU 
- Nixon Rodrigues
- Ramachandran Krishnan
- Subhrat Chaudhary
- Vishal Suvagia
- Vishal Gupta

Voting thread: https://lists.apache.org/thread/xol021mowq1z2zd862r24b86yc3r4fhf

I will begin the process of publishing the release artifacts for Apache Ranger 
2.4.0.


Thanks,
Selva-
Apache Ranger PMC


> On Mar 27, 2023, at 11:40 PM, Selvamohan Neethiraj  
> wrote:
> 
> Rangers:
> 
> Apache Ranger 2.4.0 release candidate #2 is now available for a vote within 
> the dev community.
> Links to the release artifacts are given below. Please review and vote.
> 
> The vote will be open for at least 72 hours or until necessary votes are 
> reached.
> [   ] +1 approve
> [   ] +0 no opinion
> [   ] -1 disapprove (and reason why)
> 
> Thanks,
> Selva-
> Ranger PMC 
> 
> List of issues / improvements addressed in this release:  click-here 
> <https://issues.apache.org/jira/browse/RANGER-4154?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20ORDER%20BY%20key%20desc>
> 
> Git tag for the release: 
> https://github.com/apache/ranger/tree/release-2.4.0-rc2
> Sources for the release:   
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> 
> Source release verification:
> PGP Signature:   
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> SHA256 Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> SHA512 Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
> 
> Keys to verify the signature:
> https://dist.apache.org/repos/dist/release/ranger/KEYS
> 
> Click Here 
> <https://issues.apache.org/jira/issues/?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20and%20type%20in%20(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc>
>  to view New Features/Enhancements in this release.
> 
> 
> 
> 
> 

[ANNOUNCE] Apache Ranger 2.4.0 released

[Selvamohan Neethiraj]

Hi,

Apache Ranger team is happy to announce the release of Apache Ranger 2.4.0.

Apache Ranger is a framework to enable, monitor and manage comprehensive data 
security across big-data and cloud platforms and beyond. 
Apache Ranger 2.4.0 contains a number of new features, improvements and bug 
fixes. 
Release details can be found in the release notes at 
https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.4.0+-+Release+Notes
 
The release artifacts are available at: 
https://ranger.apache.org/download.html. The binary artifacts are available 
from Maven central and its mirrors. 
When downloading binaries from the site, please remember to verify the 
downloads using signatures found at: https://www.apache.org/dist/ranger/KEYS 

Additional details about Apache Ranger can be found at: 
https://ranger.apache.org  

We thank everyone who made this release possible. 

Thanks, 
Apache Ranger team

Re: Review Request 74294: RANGER-4068: Ranger usersync needs dnsjava library

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74294/#review225330
---



Can you please document the testing and also the errors (before the fix) and 
the after-fix results ?

- Selvamohan Neethiraj


On Feb. 4, 2023, 2:13 a.m., Yubi Lee wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74294/
> ---
> 
> (Updated Feb. 4, 2023, 2:13 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-4068
> https://issues.apache.org/jira/browse/RANGER-4068
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> After I set `hadoop.security.token.service.use_ip=false` in core-site.xml, I 
> found `java.lang.NoClassDefFoundError: org/xbill/DNS/ResolverConfig` in 
> usersync log.
> I found that it is caused by missing dnsjava library in ranger usersync jar 
> as dependency.
> Ranger usersync should have `dnsjava` library.
> 
> ```
> 28 Jan 2023 00:50:18 DEBUG o.a.h.s.SecurityUtil [UnixUserSyncThread] - 
> Setting hadoop.security.token.service.use_ip to false
> 28 Jan 2023 00:50:18 ERROR o.a.r.u.UserGroupSync [UnixUserSyncThread] - 
> Failed to initialize UserGroup source/sink. Will retry after 6 
> milliseconds. Error details:
> java.lang.NoClassDefFoundError: org/xbill/DNS/ResolverConfig
> at 
> org.apache.hadoop.security.SecurityUtil$QualifiedHostResolver.(SecurityUtil.java:592)
> at 
> org.apache.hadoop.security.SecurityUtil.setTokenServiceUseIp(SecurityUtil.java:129)
> at 
> org.apache.hadoop.security.SecurityUtil.setConfigurationInternal(SecurityUtil.java:102)
> at 
> org.apache.hadoop.security.SecurityUtil.(SecurityUtil.java:88)
> at 
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:312)
> at 
> org.apache.hadoop.security.UserGroupInformation.ensureInitialized(UserGroupInformation.java:300)
> at 
> org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:567)
> at 
> org.apache.hadoop.fs.FileSystem$Cache$Key.(FileSystem.java:3614)
> at 
> org.apache.hadoop.fs.FileSystem$Cache$Key.(FileSystem.java:3604)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3441)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:524)
> at org.apache.hadoop.fs.Path.getFileSystem(Path.java:365)
> at 
> org.apache.hadoop.security.alias.JavaKeyStoreProvider.initFileSystem(JavaKeyStoreProvider.java:89)
> at 
> org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.(AbstractJavaKeyStoreProvider.java:85)
> at 
> org.apache.hadoop.security.alias.JavaKeyStoreProvider.(JavaKeyStoreProvider.java:49)
> at 
> org.apache.hadoop.security.alias.JavaKeyStoreProvider.(JavaKeyStoreProvider.java:41)
> at 
> org.apache.hadoop.security.alias.JavaKeyStoreProvider$Factory.createProvider(JavaKeyStoreProvider.java:100)
> at 
> org.apache.hadoop.security.alias.CredentialProviderFactory.getProviders(CredentialProviderFactory.java:73)
> at 
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:74)
> at 
> org.apache.ranger.unixusersync.config.UserGroupSyncConfig.getSSLKeyStorePathPassword(UserGroupSyncConfig.java:439)
> at 
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.init(PolicyMgrUserGroupBuilder.java:216)
> at 
> org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:49)
> ```
> 
> 
> Diffs
> -
> 
>   distro/src/main/assembly/usersync.xml 187d535e4 
>   ugsync/pom.xml 12801d4e2 
> 
> 
> Diff: https://reviews.apache.org/r/74294/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Yubi Lee
> 
>

Review Request 74378: RANGER-4167: fixes to kafka test suite issues

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74378/
---

Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
Ramesh Mani, and Velmurugan Periasamy.


Bugs: RANGER-4167
https://issues.apache.org/jira/browse/RANGER-4167


Repository: ranger


Description
---

When running with -DskipTests=false, the kafka test suite failing (see below 
for the errors)


Diffs
-

  plugin-kafka/pom.xml 75db9e9de 
  
plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
 1060c4d78 
  pom.xml 3a039565d 


Diff: https://reviews.apache.org/r/74378/diff/1/


Testing
---

Command used to build: 
$ mvn -Pall -pl plugin-kafka -am -DskipTests=false clean package install

Run build before the change:

[WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.033 
s - in 
org.apache.ranger.authorization.kafka.authorizer.KafkaRangerAuthorizerSASLSSLTest
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Errors: 
[ERROR]   KafkaRangerAuthorizerGSSTest.setup:149 » ZooKeeperClientTimeout Timed 
out waiting for connection while in state: CONNECTING
[ERROR]   KafkaRangerAuthorizerTest.setup:140 » ZooKeeperClientTimeout Timed 
out waiting for connection while in state: CONNECTING
[ERROR]   KafkaRangerTopicCreationTest.setup:129 » ZooKeeperClientTimeout Timed 
out waiting for connection while in state: CONNECTING
[INFO] 
[ERROR] Tests run: 4, Failures: 0, Errors: 3, Skipped: 1
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 

Run build after the change:

[INFO] ranger . SUCCESS [  2.913 s]
[INFO] Credential Support . SUCCESS [  7.440 s]
[INFO] Audit Component  SUCCESS [  9.794 s]
[INFO] ranger-plugin-classloader .. SUCCESS [  3.524 s]
[INFO] Common library for Plugins . SUCCESS [ 26.835 s]
[INFO] Credential Builder . SUCCESS [  5.497 s]
[INFO] KAFKA Security Plugin .. SUCCESS [ 47.131 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 



Thanks,

Selvamohan Neethiraj

Re: [VOTE] Apache Ranger 2.4.0 Release - rc1

[Selvamohan Neethiraj]

Due to the issues posted here, I am cancelling VOTE for the Ranger 2.4.0 
Release candidate #1.


Thanks,
Selva-

On 3/24/23 1:16 PM, Madhan Neethiraj wrote:

Selva,

Thank you for Apache Ranger 2.4.0 rc1.

- verified signature
- verified 2.4.0-rc1 builds successfully
- installed Ranger with Postgres database; verified startup of 
admin/usersync/tagsync services
- created services, policies, security zones
- sanity testing of HDFS/Hive/HBase/Kafka/YARN plugins
- verified tag-based policies and {OWNER} macro in Hive
- verified audit logs from plugins, audit-filters

Found following issues:
- usersync and tagsync services don't generate log files, due to missing 
logback libraries in deployment
- users sent by usersync module are ignored by Ranger admin, due to a 
regression introduced in RANGER-4055

I filed RANGER-4154 to track above issues; fix is in review. This fix needs to 
be included in 2.4.0 release.

Thanks,
Madhan




On 3/23/23, 3:44 PM, "Selvamohan Neethiraj" mailto:sneet...@apache.org>> wrote:


Rangers:
As a critical HBase Plugin issue was identified in the earlier release 
candidate, I am posting another release candidate (rc1) details below for VOTE.


Apache Ranger 2.4.0 release candidate #1 is now available for a vote within the 
dev community. Links to the release artifacts are given below. Please review 
and vote.


The vote will be open for at least 72 hours or until necessary votes are 
reached.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Thanks,
Selva-
Ranger PMC
List of issues / improvements addressed in this release: 
click-here<https://issues.apache.org/jira/issues/?jql=project%3DRANGER%20and%20fixVersion%20%20%3D%202.4.0%20and%20status%20%3D%20Resolved%20ORDER%20BY%20key%20desc>
  
<https://issues.apache.org/jira/issues/?jql=project%3DRANGER%20and%20fixVersion%20%20%3D%202.4.0%20and%20status%20%3D%20Resolved%20ORDER%20BY%20key%20desc;>
Git tag for the release:https://github.com/apache/ranger/tree/release-2.4.0-rc1  
<https://github.com/apache/ranger/tree/release-2.4.0-rc1>
Sources for the 
release:https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz
  
<https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz>
Source release verification:


PGP 
Signature:https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.asc
  
<https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.asc>


SHA256 
Hash:https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.sha256
  
<https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.sha256>


SHA512 
Hash:https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.sha512
  
<https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc1/apache-ranger-2.4.0.tar.gz.sha512>


Keys to verify the signature:https://dist.apache.org/repos/dist/release/ranger/KEYS  
<https://dist.apache.org/repos/dist/release/ranger/KEYS>


New features/enhancements:


Issue Type
Issue key
Summary
Improvement
RANGER-4117
service-def option to include expression condition implictly
Improvement
RANGER-4114
Consistent use of plugin property prefix in context enrichers
Improvement
RANGER-4107
Upgrade EclipseLink
Improvement
RANGER-4101
Java client update to add missing security-zone APIs
Improvement
RANGER-4100
Efficient computation of the smallest set of evaluators returned by search of 
multiple Trie trees
Improvement
RANGER-4083
Tag-based policy UI to not show permissions in deny/exception for services that 
don't support deny/exception
Improvement
RANGER-4080
Python client update to add missing security-zone APIs
Improvement
RANGER-4071
Support for LDAP/AD usernames and group names with special chars
New Feature
RANGER-4028
Ranger - Upgrade bootbox.js.
Improvement
RANGER-4024
Adding requestId as part of Ranger logs via RangerMDCFilter when the request 
header contains request-Id
Improvement
RANGER-4012
getPolicyByName searches policy by serviceName, policyName simply by traverse 
all policies in RangerServicePoliciesCache instead of DB
Improvement
RANGER-4011
option to disable creation of default policies per hierarchy
Improvement
RANGER-4004
During the service deletion also, we can clear the in-memory cache for that 
service which got deleted on the ranger side
Improvement
RANGER-3997
option to use default value when user/group/tag does not have the attribute
Improvement
RANGER-3986
Upgrade trino guice dependency to 5.1.0
Improvement
RANGER-3983
Support getColumnMasks and getRowFilters in Trino SPI 376+
Improvement
RANGER-3982
Python client for Ranger KMS REST APIs
Improvement
RANGER-3978
Docker setup to run Ranger KMS
New Feature
RANGER-3971
Upgrade HBASE version to 2.4.6
Improvement
RANGER-3955
optimization to reduce duplicate strings
Improvement
RANGER-3951
optimize memory used for tags in plugins and s

[VOTE] Apache Ranger 2.4.0 Release - rc2

[Selvamohan Neethiraj]

Rangers:

Apache Ranger 2.4.0 release candidate #2 is now available for a vote within the 
dev community.
Links to the release artifacts are given below. Please review and vote.

The vote will be open for at least 72 hours or until necessary votes are 
reached.
[   ] +1 approve
[   ] +0 no opinion
[   ] -1 disapprove (and reason why)

Thanks,
Selva-
Ranger PMC 

List of issues / improvements addressed in this release:  click-here 


Git tag for the release: 
https://github.com/apache/ranger/tree/release-2.4.0-rc2
Sources for the release:   
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz

Source release verification:
PGP Signature:   
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
SHA256 Hash:
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
SHA512 Hash:
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512

Keys to verify the signature:
https://dist.apache.org/repos/dist/release/ranger/KEYS

Click Here 

 to view New Features/Enhancements in this release.

Re: Request to add as contributor to Apache Ranger

[Selvamohan Neethiraj]

Welcome to Ranger Community. I have added you as a Apache Ranger Contributor. 

Thanks,
Selva-

On 2023/03/07 07:47:54 Lei Yao wrote:
> Hi community, 
> I would like to contribute to the Apache Ranger project, please add me as a 
> contributor.My JIra User Id is yaolei
> 
> Thanks and Regards

Re: Review Request 74356: RANGER-4144 : Fixing test suite for kafka plugin

[Selvamohan Neethiraj]

> On March 21, 2023, 6:21 p.m., Don Bosco Durai wrote:
> > plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
> > Lines 110 (patched)
> > <https://reviews.apache.org/r/74356/diff/1/?file=2275157#file2275157line110>
> >
> > Is this message misleading? Even line 106 will through exception. Would 
> > it be the same reason for port not available?

Bosco, Thanks for the review. The IOException Catch was to cover the exception 
from the Constructor of ServerSocket call (in line number 105) - where it will 
never reach the line 106. Line number 106 and 108 throws AssertionError (not an 
IOException) and is handled by JUNIT testing framework.


- Selvamohan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74356/#review225288
-------


On March 20, 2023, 3:43 p.m., Selvamohan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74356/
> ---
> 
> (Updated March 20, 2023, 3:43 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Ramesh Mani, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4144
> https://issues.apache.org/jira/browse/RANGER-4144
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Changed version of curator test version from 2.12.0 to 5.4.0 & fixed Java 
> Autoboxing issues
> 
> 
> Diffs
> -
> 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
>  d24ee1e57 
>   pom.xml 1e77f5191 
> 
> 
> Diff: https://reviews.apache.org/r/74356/diff/1/
> 
> 
> Testing
> ---
> 
> 1. Run Unit Test (as part of build) done on Linux Platform
> 
> 
> Thanks,
> 
> Selvamohan Neethiraj
> 
>

Re: Review Request 74434: DOC SITE : Recent revamp of doc site has some issues when accessed via mobile or ipad

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74434/#review225495
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On May 17, 2023, 12:56 a.m., stalin nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74434/
> ---
> 
> (Updated May 17, 2023, 12:56 a.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Dharmesh Makwana, 
> Nitin Galave, and Selvamohan Neethiraj.
> 
> 
> Bugs: RANGER-4233
> https://issues.apache.org/jira/browse/RANGER-4233
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The documentation website has recently undergone a revamp, but it seems to 
> have some issues when accessed via mobile devices or iPads. The issues could 
> be related to the website's layout making it difficult for users to access 
> the site's content or navigate through it on smaller screens.
> 
> 
> Diffs
> -
> 
>   docs/src/site/resources/css/custom.css a0592ced5 
> 
> 
> Diff: https://reviews.apache.org/r/74434/diff/1/
> 
> 
> Testing
> ---
> 
> I have used the Chrome Developer Tools to simulate accessing the website on 
> different screen sizes, including those of mobile phones and tablets.
> 
> 
> Thanks,
> 
> stalin nadar
> 
>

Re: Review Request 74530: RANGER-4336: added configurations to enable status logging in audit framework

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74530/#review225622
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On July 27, 2023, 8:07 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74530/
> ---
> 
> (Updated July 27, 2023, 8:07 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Monika 
> Kachhadiya, Pradeep Agrawal, Ramesh Mani, Siddhesh Phatak, and Subhrat 
> Chaudhary.
> 
> 
> Bugs: RANGER-4336
> https://issues.apache.org/jira/browse/RANGER-4336
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> - added configurations to enable status logging in audit framework
> - audit status are logged at INFO level
> - updated unit test to avoid retaining of unncessary objects in memory
> 
> 
> Diffs
> -
> 
>   
> agents-audit/src/main/java/org/apache/ranger/audit/provider/BaseAuditHandler.java
>  8511ce9cb 
>   
> agents-audit/src/main/java/org/apache/ranger/audit/queue/AuditAsyncQueue.java 
> 68527d37d 
>   security-admin/src/test/java/org/apache/ranger/audit/TestConsumer.java 
> 579485663 
> 
> 
> Diff: https://reviews.apache.org/r/74530/diff/1/
> 
> 
> Testing
> ---
> 
> - verified that audit status is logged when 
> xasecure.audit.log.status.log.enabled is set to true
> - verified that all unit tests pass successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74427: RANGER-4231: blog: Apache Ranger Policy Model

[Selvamohan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74427/#review225448
---


Ship it!




Ship It!

- Selvamohan Neethiraj


On May 8, 2023, 9:21 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74427/
> ---
> 
> (Updated May 8, 2023, 9:21 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Abhay Kulkarni, Ramesh Mani, 
> Selvamohan Neethiraj, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4231
> https://issues.apache.org/jira/browse/RANGER-4231
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Created HTML version of existing blog at 
> https://blogs.apache.org/ranger/entry/apache-ranger-policy-model
> 
> 
> Diffs
> -
> 
>   docs/src/site/resources/blogs/policy_model.html PRE-CREATION 
>   docs/src/site/xdoc/blogs.xml 0b302c117 
> 
> 
> Diff: https://reviews.apache.org/r/74427/diff/1/
> 
> 
> Testing
> ---
> 
> - built and ran docs using mvn site:run
> - verified the blog the browser
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>