Re: Review Request 69864: RANGER-1935:Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On Feb. 13, 2019, 10:31 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69864/
> ---
> 
> (Updated Feb. 13, 2019, 10:31 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Colm O hEigeartaigh, Gautam 
> Borad, Abhay Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, 
> Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1935
> https://issues.apache.org/jira/browse/RANGER-1935
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-1935:Upgrade Ranger to support Apache Hadoop 3.0.0
> 
> 
> Diffs
> -
> 
>   
> agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
>  0f29138 
>   credentialbuilder/pom.xml 461dcd0 
>   hbase-agent/pom.xml c044ef0 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/AuthorizationSession.java
>  9a83bc7 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/HbaseAuthUtilsImpl.java
>  01e0af2 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/HbaseUserUtilsImpl.java
>  23cd5fc 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
>  ddb6d9b 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessorBase.java
>  1062c9e 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationFilter.java
>  4006afc 
>   
> hbase-agent/src/main/java/org/apache/ranger/services/hbase/client/HBaseClient.java
>  e74c3e5 
>   
> hbase-agent/src/test/java/org/apache/ranger/authorization/hbase/HBaseRangerAuthorizationTest.java
>  f1cd893 
>   
> hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
> a7215ce 
>   hive-agent/pom.xml 0a091b2 
>   
> hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizerBase.java
>  c313870 
>   
> hive-agent/src/main/java/org/apache/ranger/services/hive/client/HiveClient.java
>  bf1bc1d 
>   
> hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
>  7dc5c54 
>   kms/pom.xml 043c67f 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
>  f853a84 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java be3700f 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
>  ada9a56 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
> b2540cb 
>   knox-agent/pom.xml 0c45c84 
>   
> plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  a4de016 
>   pom.xml 2a2540a 
>   ranger-examples/plugin-sampleapp/pom.xml bef0f5c 
>   
> ranger-hbase-plugin-shim/src/main/java/com/xasecure/authorization/hbase/XaSecureAuthorizationCoprocessor.java
>  1afe0ba 
>   
> ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
>  87c6586 
>   ranger-storm-plugin-shim/pom.xml 89efe34 
>   
> ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  7b7f1f3 
>   security-admin/pom.xml 479f46d 
>   src/main/assembly/admin-web.xml 8ea728b 
>   src/main/assembly/hbase-agent.xml 3ebc334 
>   src/main/assembly/hdfs-agent.xml 561d137 
>   src/main/assembly/hive-agent.xml 03bd31a 
>   src/main/assembly/kms.xml 3adc55c 
>   src/main/assembly/knox-agent.xml 8357d49 
>   src/main/assembly/plugin-atlas.xml 35096d0 
>   src/main/assembly/plugin-kafka.xml 7c55128 
>   src/main/assembly/plugin-kms.xml 53cf302 
>   src/main/assembly/plugin-kylin.xml f4e0820 
>   src/main/assembly/plugin-solr.xml f5fb0a7 
>   src/main/assembly/plugin-sqoop.xml d2bd69a 
>   src/main/assembly/plugin-yarn.xml c6a48e8 
>   src/main/assembly/ranger-tools.xml 249de9a 
>   src/main/assembly/storm-agent.xml fdaf678 
>   src/main/assembly/tagsync.xml 0b6596f 
>   src/main/assembly/usersync.xml d170d8c 
>   storm-agent/pom.xml a084e68 
>   
> storm-agent/src/test/java/org/apache/ranger/authorization/storm/StormRangerAuthorizerTest.java
>  2e72193 
&g

[jira] [Commented] (RANGER-2148) Update Ranger Hive dependency version to 3.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-2148:
-

The patch for RANGER-1935 should be applied to master soon.

> Update Ranger Hive dependency version to 3.0 
> -
>
> Key: RANGER-2148
> URL: https://issues.apache.org/jira/browse/RANGER-2148
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Ramesh Mani
>Assignee: Colm O hEigeartaigh
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch
>
>
> Update Ranger Hive dependency version to 3.0 



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

Re: Review Request 69864: RANGER-1935:Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

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



Please update the version of Jackson in the root pom to 2.9.8 - 2.9.5 contains 
a number of known CVEs.

- Colm O hEigeartaigh


On Jan. 30, 2019, 10:43 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69864/
> ---
> 
> (Updated Jan. 30, 2019, 10:43 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Colm O hEigeartaigh, Gautam 
> Borad, Abhay Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, 
> Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1935
> https://issues.apache.org/jira/browse/RANGER-1935
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-1935:Upgrade Ranger to support Apache Hadoop 3.0.0
> 
> 
> Diffs
> -
> 
>   
> agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
>  0f29138 
>   credentialbuilder/pom.xml 461dcd0 
>   hbase-agent/pom.xml c044ef0 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/AuthorizationSession.java
>  9a83bc7 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/HbaseAuthUtilsImpl.java
>  01e0af2 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/HbaseUserUtilsImpl.java
>  23cd5fc 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
>  ddb6d9b 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessorBase.java
>  1062c9e 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationFilter.java
>  4006afc 
>   
> hbase-agent/src/main/java/org/apache/ranger/services/hbase/client/HBaseClient.java
>  e74c3e5 
>   
> hbase-agent/src/test/java/org/apache/ranger/authorization/hbase/HBaseRangerAuthorizationTest.java
>  f1cd893 
>   
> hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
> a7215ce 
>   hive-agent/pom.xml 0a091b2 
>   
> hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizerBase.java
>  c313870 
>   
> hive-agent/src/main/java/org/apache/ranger/services/hive/client/HiveClient.java
>  bf1bc1d 
>   
> hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
>  7dc5c54 
>   kms/pom.xml 043c67f 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
>  f853a84 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java be3700f 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
>  ada9a56 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
> b2540cb 
>   knox-agent/pom.xml 0c45c84 
>   
> plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  a4de016 
>   pom.xml 2a2540a 
>   ranger-examples/plugin-sampleapp/pom.xml bef0f5c 
>   
> ranger-hbase-plugin-shim/src/main/java/com/xasecure/authorization/hbase/XaSecureAuthorizationCoprocessor.java
>  1afe0ba 
>   
> ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
>  87c6586 
>   ranger-storm-plugin-shim/pom.xml 89efe34 
>   
> ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  7b7f1f3 
>   security-admin/pom.xml 479f46d 
>   src/main/assembly/admin-web.xml 8ea728b 
>   src/main/assembly/hbase-agent.xml 3ebc334 
>   src/main/assembly/hdfs-agent.xml 561d137 
>   src/main/assembly/hive-agent.xml 03bd31a 
>   src/main/assembly/kms.xml 3adc55c 
>   src/main/assembly/knox-agent.xml 8357d49 
>   src/main/assembly/plugin-atlas.xml 35096d0 
>   src/main/assembly/plugin-kafka.xml 7c55128 
>   src/main/assembly/plugin-kms.xml 53cf302 
>   src/main/assembly/plugin-kylin.xml f4e0820 
>   src/main/assembly/plugin-solr.xml f5fb0a7 
>   src/main/assembly/plugin-sqoop.xml d2bd69a 
>   src/main/assembly/plugin-yarn.xml c6a48e8 
>   src/main/assembly/ranger-tools.xml 249de9a 
>   src/main/assembly/storm-agent.xml fdaf678 
>   src/main/assembly/tagsync.xml 0b6596f 
>   src/main/assembly/usersync.xml d170d8c 
>   storm-agent/pom.xml a084e68 
>   tagsync/pom.xml e98cf63 
>   ug

Re: Review Request 69740: RANGER-2322 - Use "TLS" in SSLContext.getInstance

[Colm O hEigeartaigh]

> On Jan. 16, 2019, 4:26 p.m., Zsombor Gegesy wrote:
> > What about changing to "TLSv1.2"?

I think it's better just to leave it as "TLS", and leave the protocol specifics 
to the version of Java that is installed.


- Colm


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


On Jan. 14, 2019, 11:20 a.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69740/
> ---
> 
> (Updated Jan. 14, 2019, 11:20 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-2322
> https://issues.apache.org/jira/browse/RANGER-2322
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> There are a few instances in the code of SSLContext.getInstance("SSL"). 
> Instead we should use "TLS".
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTClient.java
>  f592ed4e7 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerSslHelper.java
>  2036661e8 
>   
> ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapPolicyMgrUserGroupBuilder.java
>  f653b81f3 
>   
> ugsync/src/main/java/org/apache/ranger/unixusersync/process/PolicyMgrUserGroupBuilder.java
>  cb9b51c95 
> 
> 
> Diff: https://reviews.apache.org/r/69740/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

Review Request 69740: RANGER-2322 - Use "TLS" in SSLContext.getInstance

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

There are a few instances in the code of SSLContext.getInstance("SSL"). Instead 
we should use "TLS".


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTClient.java 
f592ed4e7 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerSslHelper.java 
2036661e8 
  
ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapPolicyMgrUserGroupBuilder.java
 f653b81f3 
  
ugsync/src/main/java/org/apache/ranger/unixusersync/process/PolicyMgrUserGroupBuilder.java
 cb9b51c95 


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


Testing
-------


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2322) Use "TLS" in SSLContext.getInstance

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2322:

Attachment: RANGER-2322.patch

> Use "TLS" in SSLContext.getInstance
> ---
>
> Key: RANGER-2322
> URL: https://issues.apache.org/jira/browse/RANGER-2322
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins, usersync
>Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: RANGER-2322.patch
>
>
> There are a few instances in the code of SSLContext.getInstance("SSL"). 
> Instead we should use "TLS".



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

[jira] [Created] (RANGER-2322) Use "TLS" in SSLContext.getInstance

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2322:
---

 Summary: Use "TLS" in SSLContext.getInstance
 Key: RANGER-2322
 URL: https://issues.apache.org/jira/browse/RANGER-2322
 Project: Ranger
  Issue Type: Improvement
  Components: plugins, usersync
Affects Versions: 2.0.0
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh


There are a few instances in the code of SSLContext.getInstance("SSL"). Instead 
we should use "TLS".



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

Re: Public groups in default policies

[Colm O hEigeartaigh]

Hi Ramesh,

No I don't have a patch for this, please feel free to create one.

Thanks,

Colm.

On Fri, Oct 26, 2018 at 7:53 PM Ramesh Mani  wrote:

> +1 for this.
>
> We need to create default policy for admin users only. User ³kafka² ( part
> of the service config) would be the user in that case.
>
> Colm, do you have a patch for it? If not I can provide one.
>
> Thanks,
> Ramesh
>
>
> On 10/17/18, 9:18 AM, "Colm O hEigeartaigh"  wrote:
>
> >Hi all,
> >
> >I was testing the new support for Kafka 2.0.0 in the Ranger master code -
> >I
> >was surprised to see that when you create a new Kafka resource, that the
> >default policies all are associated with the "public" group. That means
> >that using the default policies anyone is authorized to publish/consumer
> >from a topic, etc.
> >
> >I think it would be more secure if the default policies we associate with
> >a
> >resource are associated only with the admin user specified when creating
> >the resource, and not the public group.
> >
> >Colm.
> >
> >
> >--
> >Colm O hEigeartaigh
> >
> >Talend Community Coder
> >http://coders.talend.com
>
>

-- 
Colm O hEigeartaigh

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

[jira] [Updated] (RANGER-2256) Grammatical error in UI

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2256:

Attachment: 0001-RANGER-2256-Grammatical-error-in-UI.patch

> Grammatical error in UI
> ---
>
> Key: RANGER-2256
> URL: https://issues.apache.org/jira/browse/RANGER-2256
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: 0001-RANGER-2256-Grammatical-error-in-UI.patch
>
>
> There's a grammatical error in the UI when looking at the users of an empty 
> group.



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

Review Request 69065: RANGER-2256 - Grammatical error in UI

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

There's a grammatical error in the UI when looking at the users of an empty 
group.


Diffs
-

  security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
99cbf55e9 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Created] (RANGER-2256) Grammatical error in UI

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2256:
---

 Summary: Grammatical error in UI
 Key: RANGER-2256
 URL: https://issues.apache.org/jira/browse/RANGER-2256
 Project: Ranger
  Issue Type: Task
  Components: admin
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 2.0.0


There's a grammatical error in the UI when looking at the users of an empty 
group.



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

Re: Review Request 67697: RANGER-2140: Upgrade spring and guava libraries

[Colm O hEigeartaigh]

> On Oct. 2, 2018, 9:06 p.m., Velmurugan Periasamy wrote:
> > knox-agent/src/test/java/org/apache/ranger/services/knox/KnoxRangerTest.java
> > Lines 46 (patched)
> > 
> >
> > Upgrading to 25.1-jre is a good idea. 
> > 
> > Instead of ignoring the test, my suggestion is to fix the issue.
> > 
> > Also if this JIRA is going to be used only for Guava upgrade, please 
> > update the description in RR and JIRA. For spring version upgrade, please 
> > create a new JIRA. Thanks.

+1 to fixiing the issue. Weirdly, just uncommenting 
"ranger.root.logger=WARN,console" in src/test/resources/log4j.properties makes 
the tests pass, so I guess thre is some sort of timing issue.


- Colm


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


On June 25, 2018, 10:26 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67697/
> ---
> 
> (Updated June 25, 2018, 10:26 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2140
> https://issues.apache.org/jira/browse/RANGER-2140
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Here I am proposing to change Guava version to only 17.0, currently there are 
> three different version are being used. Also proposing to change Spring 
> Security to 4.2.7 and Spring Framework to 4.3.18.
> 
> 
> Diffs
> -
> 
>   kms/pom.xml 6fc190f35 
>   
> knox-agent/src/test/java/org/apache/ranger/services/knox/KnoxRangerTest.java 
> 764192172 
>   plugin-atlas/pom.xml fcc037f93 
>   pom.xml e6695b440 
>   src/main/assembly/kms.xml 7fbc1410c 
>   src/main/assembly/plugin-atlas.xml 8f4a64cb6 
>   src/main/assembly/plugin-kms.xml 6d15f2a10 
>   src/main/assembly/plugin-solr.xml de30bfb13 
>   ugsync/pom.xml f4c24e739 
>   unixauthclient/pom.xml cd3d15604 
>   unixauthservice/pom.xml 2c0ed2eef 
> 
> 
> Diff: https://reviews.apache.org/r/67697/diff/3/
> 
> 
> Testing
> ---
> 
> Tested Ranger admin installation, user login, usersync and other crud 
> operations on service, policy, user and group module.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 68871: RANGER-2238 String comparison should not use ‘==’ in ServiceUtil.java

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On Sept. 28, 2018, 3:20 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68871/
> ---
> 
> (Updated Sept. 28, 2018, 3:20 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, Mehul Parikh, Nitin Galave, 
> pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, sam  rome, 
> Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2238
> https://issues.apache.org/jira/browse/RANGER-2238
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Here is related code:
> 
> for(RangerPolicy.RangerPolicyItemCondition condition : 
> policyItem.getConditions()) {
> if(condition.getType() == "ipaddress") {
> 
> equals() should be used to compare Strings.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/common/ServiceUtil.java 
> 0292881b4 
> 
> 
> Diff: https://reviews.apache.org/r/68871/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Review Request 68894: RANGER-2239 - Update to surefire 2.21.0

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

To support newer Java versions, we need to update surefire.


Diffs
-

  pom.xml e0df461e9 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2239) Update to surefire 2.21.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2239:

Attachment: 0001-RANGER-2239-Update-to-surefire-2.21.0.patch

> Update to surefire 2.21.0
> -
>
> Key: RANGER-2239
> URL: https://issues.apache.org/jira/browse/RANGER-2239
> Project: Ranger
>  Issue Type: Task
>  Components: build-infra
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 0001-RANGER-2239-Update-to-surefire-2.21.0.patch
>
>
> To support newer Java versions, we need to update surefire.



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

[jira] [Created] (RANGER-2239) Update to surefire 2.21.0

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2239:
---

 Summary: Update to surefire 2.21.0
 Key: RANGER-2239
 URL: https://issues.apache.org/jira/browse/RANGER-2239
 Project: Ranger
  Issue Type: Task
  Components: build-infra
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 2.0.0


To support newer Java versions, we need to update surefire.



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

Re: [VOTE] Apache Ranger Release 1.2.0-rc1

[Colm O hEigeartaigh]

+1.

I think the "mds" digests file is not necessary - simply adding the
standalone sha files is enough.

Colm.

On Mon, Oct 1, 2018 at 3:05 PM PradeeP AgrawaL 
wrote:

> +1 for the release of 1.2.0-rc1
> Able to download the source and build with unit test cases
> Able to install, setup and start Ranger
> Able to do CRUD operation on service, policy, user, and groups.
>
> Thanks, Vel for putting Ranger 1.2.0 for release.
>
> Regards,
> Pradeep
>
> On Mon, 1 Oct 2018 at 11:27, Nixon Rodrigues <
> nixon.rodrig...@freestoneinfotech.com> wrote:
>
> > +1 for release of 1.2.0-rc1,
> >
> > Thanks Vel for putting Ranger 1.2.0 for release
> >
> > Nixon Rodrigues
> >
> > On Mon, Oct 1, 2018 at 8:01 AM Koji Kawamura 
> > wrote:
> >
> > > +1
> > >
> > > verified build & signature
> > >
> > > Thanks,
> > > Koji
> > > On Mon, Oct 1, 2018 at 8:58 AM Selvamohan Neethiraj <
> sneet...@apache.org
> > >
> > > wrote:
> > > >
> > > > +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
> > > > >>
> > > > >
> > > >
> > >
> >
>


-- 
Colm O hEigeartaigh

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

[jira] [Updated] (RANGER-2231) Upgrade to Knox 1.1.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2231:

Attachment: (was: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch)

> Upgrade to Knox 1.1.0
> -
>
> Key: RANGER-2231
> URL: https://issues.apache.org/jira/browse/RANGER-2231
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch
>
>
> Upgrade to Knox 1.1.0.



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

Re: Review Request 68796: RANGER-2231 - Upgrade to Knox 1.1.0

[Colm O hEigeartaigh]

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

(Updated Sept. 26, 2018, 11:09 p.m.)


Review request for ranger.


Summary (updated)
-

RANGER-2231 - Upgrade to Knox 1.1.0


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


Repository: ranger


Description
---

Upgrade to Knox 1.1.0


Diffs (updated)
-

  pom.xml e6695b440 


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

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


Testing
---

Tested authorization with Knox + also Knox SSO.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2231) Upgrade to Knox 1.1.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2231:

Attachment: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch

> Upgrade to Knox 1.1.0
> -
>
> Key: RANGER-2231
> URL: https://issues.apache.org/jira/browse/RANGER-2231
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch
>
>
> Upgrade to Knox 1.1.0.



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

Review Request 68796: KNOX-2231 - Upgrade to Knox 1.1.0

[Colm O hEigeartaigh]

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

Review request for ranger.


Bugs: KNOX-2231
https://issues.apache.org/jira/browse/KNOX-2231


Repository: ranger


Description
---

Upgrade to Knox 1.1.0


Diffs
-

  pom.xml ebf5d4806 


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


Testing
---

Tested authorization with Knox + also Knox SSO.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2231) Upgrade to Knox 1.1.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2231:

Attachment: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch

> Upgrade to Knox 1.1.0
> -
>
> Key: RANGER-2231
> URL: https://issues.apache.org/jira/browse/RANGER-2231
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch
>
>
> Upgrade to Knox 1.1.0.



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

[jira] [Created] (RANGER-2231) Upgrade to Knox 1.1.0

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2231:
---

 Summary: Upgrade to Knox 1.1.0
 Key: RANGER-2231
 URL: https://issues.apache.org/jira/browse/RANGER-2231
 Project: Ranger
  Issue Type: Task
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 2.0.0


Upgrade to Knox 1.1.0.



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

Re: Atlas version

[Colm O hEigeartaigh]

Sure, that makes sense to me.

Colm.

On Tue, Sep 18, 2018 at 5:04 PM Velmurugan Periasamy  wrote:

> Thank you Colm. My suggestion is to release Ranger 1.2.0 with Atlas
> version 1.1.0 (which just got released).
>
> Master can continue tracking Atlas 2.0.0-SNAPSHOT, and 1.1+ lines can be
> updated to Atlas 1.1.0.
>
> Thoughts?
>
> ________
> From: Colm O hEigeartaigh 
> Sent: Tuesday, September 18, 2018 11:44 AM
> To: dev@ranger.apache.org
> Subject: Atlas version
>
> Hi all,
>
> I'm wondering if there's a reason that we rely on Atlas 2.0.0-SNAPSHOT
> instead of 1.1.0? The build works fine with Atlas 1.1.0. In particular, we
> released Ranger 1.1.0 with a dependency on an atlas SNAPSHOT which is not
> great.
>
> Colm.
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
>

-- 
Colm O hEigeartaigh

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

Atlas version

[Colm O hEigeartaigh]

Hi all,

I'm wondering if there's a reason that we rely on Atlas 2.0.0-SNAPSHOT
instead of 1.1.0? The build works fine with Atlas 1.1.0. In particular, we
released Ranger 1.1.0 with a dependency on an atlas SNAPSHOT which is not
great.

Colm.


-- 
Colm O hEigeartaigh

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

[jira] [Updated] (RANGER-2190) Auto populate the relationship ends when relationship type is selected.

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2190:

Fix Version/s: (was: 1.1.0)

> Auto populate the relationship ends when relationship type is selected.
> ---
>
> Key: RANGER-2190
> URL: https://issues.apache.org/jira/browse/RANGER-2190
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 1.1.0
>Reporter: Ayub Pathan
>Priority: Critical
>
> Currently relationship ends need to be manually populated by user and this 
> can be auto-populated whenever a relationship type is selected. 



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

[jira] [Updated] (RANGER-2226) Define explicit (test) dependency on json-smart in the Knox agent

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2226:

Fix Version/s: (was: 1.1.0)

> Define explicit (test) dependency on json-smart in the Knox agent
> -
>
> Key: RANGER-2226
> URL: https://issues.apache.org/jira/browse/RANGER-2226
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2226-Define-explicit-test-dependency-on-json-.patch
>
>
> The build is currently failing for me with:
> Failed to read artifact descriptor for 
> net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact 
> net.minidev:json-smart:pom:2.3-SNAPSHOT from/to dynamodb-local-oregon 
> (https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied 
> to: 
> https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom
>  , ReasonPhrase:Forbidden. -> [Help 1]
> The fix is to declare an explicit (test) dependency on json-smart in the Knox 
> module.
> See: https://issues.apache.org/jira/browse/KNOX-1275



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

Re: Review Request 68715: RANGER-2226 - Define explicit (test) dependency on json-smart in the Knox agent

[Colm O hEigeartaigh]

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

(Updated Sept. 17, 2018, 9:56 a.m.)


Review request for ranger.


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


Repository: ranger


Description
---

The build is currently failing for me with:

Failed to read artifact descriptor for net.minidev:json-smart:jar:2.3-SNAPSHOT: 
Could not transfer artifact net.minidev:json-smart:pom:2.3-SNAPSHOT from/to 
dynamodb-local-oregon 
(https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied to: 
https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom
 , ReasonPhrase:Forbidden. -> [Help 1]

The fix is to declare an explicit (test) dependency on json-smart in the Knox 
module.

See: https://issues.apache.org/jira/browse/KNOX-1275


Diffs
-

  knox-agent/pom.xml 1d8fdae62 
  pom.xml ae3f4be4c 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2226) Define explicit (test) dependency on json-smart in the Knox agent

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2226:

Attachment: 0001-RANGER-2226-Define-explicit-test-dependency-on-json-.patch

> Define explicit (test) dependency on json-smart in the Knox agent
> -
>
> Key: RANGER-2226
> URL: https://issues.apache.org/jira/browse/RANGER-2226
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: 
> 0001-RANGER-2226-Define-explicit-test-dependency-on-json-.patch
>
>
> The build is currently failing for me with:
> Failed to read artifact descriptor for 
> net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact 
> net.minidev:json-smart:pom:2.3-SNAPSHOT from/to dynamodb-local-oregon 
> (https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied 
> to: 
> https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom
>  , ReasonPhrase:Forbidden. -> [Help 1]
> The fix is to declare an explicit (test) dependency on json-smart in the Knox 
> module.
> See: https://issues.apache.org/jira/browse/KNOX-1275



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

Review Request 68715: RANGER-2226 - Define explicit (test) dependency on json-smart in the Knox agent

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

The build is currently failing for me with:

Failed to read artifact descriptor for net.minidev:json-smart:jar:2.3-SNAPSHOT: 
Could not transfer artifact net.minidev:json-smart:pom:2.3-SNAPSHOT from/to 
dynamodb-local-oregon 
(https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied to: 
https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom
 , ReasonPhrase:Forbidden. -> [Help 1]

The fix is to declare an explicit (test) dependency on json-smart in the Knox 
module.

See: https://issues.apache.org/jira/browse/KNOX-1275


Diffs
-

  knox-agent/pom.xml 1d8fdae62 
  pom.xml ae3f4be4c 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Created] (RANGER-2226) Define explicit (test) dependency on json-smart in the Knox agent

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2226:
---

 Summary: Define explicit (test) dependency on json-smart in the 
Knox agent
 Key: RANGER-2226
 URL: https://issues.apache.org/jira/browse/RANGER-2226
 Project: Ranger
  Issue Type: Task
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 2.0.0, 1.1.0


The build is currently failing for me with:

Failed to read artifact descriptor for net.minidev:json-smart:jar:2.3-SNAPSHOT: 
Could not transfer artifact net.minidev:json-smart:pom:2.3-SNAPSHOT from/to 
dynamodb-local-oregon 
(https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied to: 
https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom
 , ReasonPhrase:Forbidden. -> [Help 1]

The fix is to declare an explicit (test) dependency on json-smart in the Knox 
module.

See: https://issues.apache.org/jira/browse/KNOX-1275



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

Re: Review Request 68428: RANGER-1935/RANGER-1738 - Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

> On Sept. 5, 2018, 11:09 p.m., Ramesh Mani wrote:
> > security-admin/pom.xml
> > Line 263 (original), 263 (patched)
> > <https://reviews.apache.org/r/68428/diff/3/?file=2082396#file2082396line263>
> >
> > why using hadoop.2.7 version for ranger secuirty-admin?

As I said in the description above, if the Admin service uses the new Hadoop 
jars, when you click on the users part of the Admin UI, no users appear. I'm 
not expert enough with the UI to figure out why, so I left the admin service 
using the old hadoop jars in the patch, and planned to create a separate JIRA 
to upgrade the admin service afterwards.


- Colm


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


On Sept. 5, 2018, 1:22 p.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68428/
> ---
> 
> (Updated Sept. 5, 2018, 1:22 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1935
> https://issues.apache.org/jira/browse/RANGER-1935
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Ranger to use Apache Hadoop 3.0.0. Some comments:
> 
> - KMS reencryptEncryptedKey not implemented.
> - HDFS unit test - HDFSContentSummaryTest test failing. @Ignore'd for now, 
> I'll create a separate JIRA for this.
> - Hive tests commented out - waiting for Hive upgrade task.
> - Admin service users not appearing so in the patch it's using the old Hadoop 
> jars. I'll create a separate JIRA for this to upgrade it as well.
> 
> 
> Diffs
> -
> 
>   
> agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
>  0f291389f 
>   credentialbuilder/pom.xml 461dcd0b6 
>   
> hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
> a7215ce92 
>   
> hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
>  7dc5c54b0 
>   kms/pom.xml 6fc190f35 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
>  f853a844b 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java 
> be3700ffa 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
>  ada9a56f4 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
> b2540cb42 
>   knox-agent/pom.xml 1d8fdae62 
>   
> plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  a4de016ea 
>   pom.xml ae3f4be4c 
>   ranger-examples/plugin-sampleapp/pom.xml bef0f5c1f 
>   ranger-storm-plugin-shim/pom.xml 89efe34de 
>   
> ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  7b7f1f303 
>   security-admin/pom.xml 84bbd6650 
>   src/main/assembly/hbase-agent.xml 3ebc334d1 
>   src/main/assembly/hdfs-agent.xml 561d13737 
>   src/main/assembly/hive-agent.xml 03bd31a55 
>   src/main/assembly/kms.xml 7fbc1410c 
>   src/main/assembly/knox-agent.xml 8357d4989 
>   src/main/assembly/plugin-atlas.xml 8f4a64cb6 
>   src/main/assembly/plugin-kafka.xml 97ff8ad1b 
>   src/main/assembly/plugin-kms.xml 6d15f2a10 
>   src/main/assembly/plugin-kylin.xml f4e082007 
>   src/main/assembly/plugin-solr.xml de30bfb13 
>   src/main/assembly/plugin-sqoop.xml d2bd69ab3 
>   src/main/assembly/plugin-yarn.xml c6a48e888 
>   src/main/assembly/ranger-tools.xml 249de9a2d 
>   src/main/assembly/storm-agent.xml fdaf67863 
>   src/main/assembly/tagsync.xml d1b83df42 
>   src/main/assembly/usersync.xml d170d8c1c 
>   storm-agent/pom.xml a084e6891 
>   tagsync/pom.xml e98cf63dc 
>   ugsync/ldapconfigchecktool/ldapconfigcheck/pom.xml d49001a65 
>   
> ugsync/ldapconfigchecktool/ldapconfigcheck/src/main/java/org/apache/ranger/ldapconfigcheck/LdapConfig.java
>  9a77cedf7 
>   ugsync/pom.xml f4c24e739 
>   unixauthclient/pom.xml cd3d15604 
>   unixauthservice/pom.xml 2c0ed2eef 
> 
> 
> Diff: https://reviews.apache.org/r/68428/diff/3/
> 
> 
> Testing
> ---
> 
> Tested plugins: HDFS, Yarn, Storm (uses Hadoop 2.7.1), Knox, HBase, KMS, 
> Sqoop, Kafka, Solr, usersync. Test admin service works OK.
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

Re: Review Request 68428: RANGER-1935/RANGER-1738 - Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

> On Sept. 5, 2018, 11:53 a.m., Mehul Parikh wrote:
> > @colm : your patch is not getting applied on latest master branch. Can you 
> > please rebase your patch?

OK please try again...


- Colm


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


On Sept. 5, 2018, 1:22 p.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68428/
> ---
> 
> (Updated Sept. 5, 2018, 1:22 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1935
> https://issues.apache.org/jira/browse/RANGER-1935
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Ranger to use Apache Hadoop 3.0.0. Some comments:
> 
> - KMS reencryptEncryptedKey not implemented.
> - HDFS unit test - HDFSContentSummaryTest test failing. @Ignore'd for now, 
> I'll create a separate JIRA for this.
> - Hive tests commented out - waiting for Hive upgrade task.
> - Admin service users not appearing so in the patch it's using the old Hadoop 
> jars. I'll create a separate JIRA for this to upgrade it as well.
> 
> 
> Diffs
> -
> 
>   
> agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
>  0f291389f 
>   credentialbuilder/pom.xml 461dcd0b6 
>   
> hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
> a7215ce92 
>   
> hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
>  7dc5c54b0 
>   kms/pom.xml 6fc190f35 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
>  f853a844b 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java 
> be3700ffa 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
>  ada9a56f4 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
> b2540cb42 
>   knox-agent/pom.xml 1d8fdae62 
>   
> plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  a4de016ea 
>   pom.xml ae3f4be4c 
>   ranger-examples/plugin-sampleapp/pom.xml bef0f5c1f 
>   ranger-storm-plugin-shim/pom.xml 89efe34de 
>   
> ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
>  7b7f1f303 
>   security-admin/pom.xml 84bbd6650 
>   src/main/assembly/hbase-agent.xml 3ebc334d1 
>   src/main/assembly/hdfs-agent.xml 561d13737 
>   src/main/assembly/hive-agent.xml 03bd31a55 
>   src/main/assembly/kms.xml 7fbc1410c 
>   src/main/assembly/knox-agent.xml 8357d4989 
>   src/main/assembly/plugin-atlas.xml 8f4a64cb6 
>   src/main/assembly/plugin-kafka.xml 97ff8ad1b 
>   src/main/assembly/plugin-kms.xml 6d15f2a10 
>   src/main/assembly/plugin-kylin.xml f4e082007 
>   src/main/assembly/plugin-solr.xml de30bfb13 
>   src/main/assembly/plugin-sqoop.xml d2bd69ab3 
>   src/main/assembly/plugin-yarn.xml c6a48e888 
>   src/main/assembly/ranger-tools.xml 249de9a2d 
>   src/main/assembly/storm-agent.xml fdaf67863 
>   src/main/assembly/tagsync.xml d1b83df42 
>   src/main/assembly/usersync.xml d170d8c1c 
>   storm-agent/pom.xml a084e6891 
>   tagsync/pom.xml e98cf63dc 
>   ugsync/ldapconfigchecktool/ldapconfigcheck/pom.xml d49001a65 
>   
> ugsync/ldapconfigchecktool/ldapconfigcheck/src/main/java/org/apache/ranger/ldapconfigcheck/LdapConfig.java
>  9a77cedf7 
>   ugsync/pom.xml f4c24e739 
>   unixauthclient/pom.xml cd3d15604 
>   unixauthservice/pom.xml 2c0ed2eef 
> 
> 
> Diff: https://reviews.apache.org/r/68428/diff/3/
> 
> 
> Testing
> ---
> 
> Tested plugins: HDFS, Yarn, Storm (uses Hadoop 2.7.1), Knox, HBase, KMS, 
> Sqoop, Kafka, Solr, usersync. Test admin service works OK.
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1935:

Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1935:

Attachment: (was: 
0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch)

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

Re: Review Request 68428: RANGER-1935/RANGER-1738 - Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

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

(Updated Sept. 5, 2018, 1:22 p.m.)


Review request for ranger.


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


Repository: ranger


Description
---

Upgrade Ranger to use Apache Hadoop 3.0.0. Some comments:

- KMS reencryptEncryptedKey not implemented.
- HDFS unit test - HDFSContentSummaryTest test failing. @Ignore'd for now, I'll 
create a separate JIRA for this.
- Hive tests commented out - waiting for Hive upgrade task.
- Admin service users not appearing so in the patch it's using the old Hadoop 
jars. I'll create a separate JIRA for this to upgrade it as well.


Diffs (updated)
-

  
agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
 0f291389f 
  credentialbuilder/pom.xml 461dcd0b6 
  hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
a7215ce92 
  
hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
 7dc5c54b0 
  kms/pom.xml 6fc190f35 
  
kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
 f853a844b 
  kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java be3700ffa 
  
kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
 ada9a56f4 
  kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
b2540cb42 
  knox-agent/pom.xml 1d8fdae62 
  
plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
 a4de016ea 
  pom.xml ae3f4be4c 
  ranger-examples/plugin-sampleapp/pom.xml bef0f5c1f 
  ranger-storm-plugin-shim/pom.xml 89efe34de 
  
ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
 7b7f1f303 
  security-admin/pom.xml 84bbd6650 
  src/main/assembly/hbase-agent.xml 3ebc334d1 
  src/main/assembly/hdfs-agent.xml 561d13737 
  src/main/assembly/hive-agent.xml 03bd31a55 
  src/main/assembly/kms.xml 7fbc1410c 
  src/main/assembly/knox-agent.xml 8357d4989 
  src/main/assembly/plugin-atlas.xml 8f4a64cb6 
  src/main/assembly/plugin-kafka.xml 97ff8ad1b 
  src/main/assembly/plugin-kms.xml 6d15f2a10 
  src/main/assembly/plugin-kylin.xml f4e082007 
  src/main/assembly/plugin-solr.xml de30bfb13 
  src/main/assembly/plugin-sqoop.xml d2bd69ab3 
  src/main/assembly/plugin-yarn.xml c6a48e888 
  src/main/assembly/ranger-tools.xml 249de9a2d 
  src/main/assembly/storm-agent.xml fdaf67863 
  src/main/assembly/tagsync.xml d1b83df42 
  src/main/assembly/usersync.xml d170d8c1c 
  storm-agent/pom.xml a084e6891 
  tagsync/pom.xml e98cf63dc 
  ugsync/ldapconfigchecktool/ldapconfigcheck/pom.xml d49001a65 
  
ugsync/ldapconfigchecktool/ldapconfigcheck/src/main/java/org/apache/ranger/ldapconfigcheck/LdapConfig.java
 9a77cedf7 
  ugsync/pom.xml f4c24e739 
  unixauthclient/pom.xml cd3d15604 
  unixauthservice/pom.xml 2c0ed2eef 


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

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


Testing
---

Tested plugins: HDFS, Yarn, Storm (uses Hadoop 2.7.1), Knox, HBase, KMS, Sqoop, 
Kafka, Solr, usersync. Test admin service works OK.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1935:

Attachment: (was: 
0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch)

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1935:

Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

Re: Review Request 68428: RANGER-1935/RANGER-1738 - Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

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

(Updated Sept. 5, 2018, 8:56 a.m.)


Review request for ranger.


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


Repository: ranger


Description
---

Upgrade Ranger to use Apache Hadoop 3.0.0. Some comments:

- KMS reencryptEncryptedKey not implemented.
- HDFS unit test - HDFSContentSummaryTest test failing. @Ignore'd for now, I'll 
create a separate JIRA for this.
- Hive tests commented out - waiting for Hive upgrade task.
- Admin service users not appearing so in the patch it's using the old Hadoop 
jars. I'll create a separate JIRA for this to upgrade it as well.


Diffs (updated)
-

  
agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
 0f291389f 
  credentialbuilder/pom.xml 461dcd0b6 
  hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
a7215ce92 
  
hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
 7dc5c54b0 
  kms/pom.xml 6fc190f35 
  
kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
 f853a844b 
  kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java be3700ffa 
  
kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
 ada9a56f4 
  kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
b2540cb42 
  knox-agent/pom.xml 1d8fdae62 
  
plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
 a4de016ea 
  pom.xml 8d7ea131e 
  ranger-examples/plugin-sampleapp/pom.xml bef0f5c1f 
  ranger-storm-plugin-shim/pom.xml 89efe34de 
  
ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
 7b7f1f303 
  security-admin/pom.xml 84bbd6650 
  src/main/assembly/hbase-agent.xml 3ebc334d1 
  src/main/assembly/hdfs-agent.xml 561d13737 
  src/main/assembly/hive-agent.xml 03bd31a55 
  src/main/assembly/kms.xml 7fbc1410c 
  src/main/assembly/knox-agent.xml 8357d4989 
  src/main/assembly/plugin-atlas.xml 8f4a64cb6 
  src/main/assembly/plugin-kafka.xml 97ff8ad1b 
  src/main/assembly/plugin-kms.xml 6d15f2a10 
  src/main/assembly/plugin-kylin.xml f4e082007 
  src/main/assembly/plugin-solr.xml de30bfb13 
  src/main/assembly/plugin-sqoop.xml d2bd69ab3 
  src/main/assembly/plugin-yarn.xml c6a48e888 
  src/main/assembly/ranger-tools.xml 249de9a2d 
  src/main/assembly/storm-agent.xml fdaf67863 
  src/main/assembly/tagsync.xml bc6e28b94 
  src/main/assembly/usersync.xml a6bad1dec 
  storm-agent/pom.xml a084e6891 
  tagsync/pom.xml e98cf63dc 
  ugsync/ldapconfigchecktool/ldapconfigcheck/pom.xml d49001a65 
  
ugsync/ldapconfigchecktool/ldapconfigcheck/src/main/java/org/apache/ranger/ldapconfigcheck/LdapConfig.java
 9a77cedf7 
  ugsync/pom.xml f4c24e739 
  unixauthclient/pom.xml cd3d15604 
  unixauthservice/pom.xml 2c0ed2eef 


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

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


Testing
---

Tested plugins: HDFS, Yarn, Storm (uses Hadoop 2.7.1), Knox, HBase, KMS, Sqoop, 
Kafka, Solr, usersync. Test admin service works OK.


Thanks,

Colm O hEigeartaigh

Review Request 68499: RANGER-2198 - Remove deprecated client API from HBase plugin

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

This task is to replace the deprecated client API from the HBase plugin. This 
will make migrating to HBase 2.0.0 a bit easier.


Diffs
-

  
hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerHBaseResource.java
 105561846 
  
hbase-agent/src/main/java/org/apache/ranger/services/hbase/client/HBaseClient.java
 8c47b57eb 


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


Testing
---

Tested that the Ranger Admin service can connect OK to HBase, retrieve column 
families etc.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2198) Remove deprecated client API from HBase plugin

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2198:

Attachment: 0001-RANGER-2198-Remove-deprecated-client-API-from-HBase-.patch

> Remove deprecated client API from HBase plugin
> --
>
> Key: RANGER-2198
> URL: https://issues.apache.org/jira/browse/RANGER-2198
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2198-Remove-deprecated-client-API-from-HBase-.patch
>
>
> This task is to replace the deprecated client API from the HBase plugin. This 
> will make migrating to HBase 2.0.0 a bit easier.



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

[jira] [Created] (RANGER-2198) Remove deprecated client API from HBase plugin

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2198:
---

 Summary: Remove deprecated client API from HBase plugin
 Key: RANGER-2198
 URL: https://issues.apache.org/jira/browse/RANGER-2198
 Project: Ranger
  Issue Type: Task
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 2.0.0


This task is to replace the deprecated client API from the HBase plugin. This 
will make migrating to HBase 2.0.0 a bit easier.



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

[jira] [Commented] (RANGER-2148) Update Ranger Hive dependency version to 3.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-2148:
-

Patch included. It depends on the Hadoop 3.0.0 patch in RANGER-1935. Tested 
with Hadoop 3.0.0 + Hive 3.0.0.

> Update Ranger Hive dependency version to 3.0 
> -
>
> Key: RANGER-2148
> URL: https://issues.apache.org/jira/browse/RANGER-2148
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Ramesh Mani
>Assignee: Colm O hEigeartaigh
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch
>
>
> Update Ranger Hive dependency version to 3.0 



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

[jira] [Updated] (RANGER-2148) Update Ranger Hive dependency version to 3.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2148:

Attachment: 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch

> Update Ranger Hive dependency version to 3.0 
> -
>
> Key: RANGER-2148
> URL: https://issues.apache.org/jira/browse/RANGER-2148
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Ramesh Mani
>Assignee: Colm O hEigeartaigh
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch
>
>
> Update Ranger Hive dependency version to 3.0 



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

Review Request 68428: RANGER-1935/RANGER-1738 - Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

Upgrade Ranger to use Apache Hadoop 3.0.0. Some comments:

- KMS reencryptEncryptedKey not implemented.
- HDFS unit test - HDFSContentSummaryTest test failing. @Ignore'd for now, I'll 
create a separate JIRA for this.
- Hive tests commented out - waiting for Hive upgrade task.
- Admin service users not appearing so in the patch it's using the old Hadoop 
jars. I'll create a separate JIRA for this to upgrade it as well.


Diffs
-

  
agents-audit/src/main/java/org/apache/ranger/audit/utils/InMemoryJAASConfiguration.java
 0f291389f 
  credentialbuilder/pom.xml 461dcd0b6 
  hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/HDFSRangerTest.java 
a7215ce92 
  
hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java
 7dc5c54b0 
  kms/pom.xml 6fc190f35 
  
kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/EagerKeyGeneratorKeyProviderCryptoExtension.java
 f853a844b 
  kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java be3700ffa 
  
kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
 ada9a56f4 
  kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSWebApp.java 
b2540cb42 
  knox-agent/pom.xml 1d8fdae62 
  
plugin-yarn/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
 a4de016ea 
  pom.xml ae3f4be4c 
  ranger-examples/plugin-sampleapp/pom.xml bef0f5c1f 
  ranger-storm-plugin-shim/pom.xml 89efe34de 
  
ranger-yarn-plugin-shim/src/main/java/org/apache/ranger/authorization/yarn/authorizer/RangerYarnAuthorizer.java
 7b7f1f303 
  security-admin/pom.xml 84bbd6650 
  src/main/assembly/hbase-agent.xml 3ebc334d1 
  src/main/assembly/hdfs-agent.xml 561d13737 
  src/main/assembly/hive-agent.xml 03bd31a55 
  src/main/assembly/kms.xml 7fbc1410c 
  src/main/assembly/knox-agent.xml 8357d4989 
  src/main/assembly/plugin-atlas.xml 8f4a64cb6 
  src/main/assembly/plugin-kafka.xml 97ff8ad1b 
  src/main/assembly/plugin-kms.xml 6d15f2a10 
  src/main/assembly/plugin-kylin.xml f4e082007 
  src/main/assembly/plugin-solr.xml de30bfb13 
  src/main/assembly/plugin-sqoop.xml d2bd69ab3 
  src/main/assembly/plugin-yarn.xml c6a48e888 
  src/main/assembly/ranger-tools.xml 249de9a2d 
  src/main/assembly/storm-agent.xml fdaf67863 
  src/main/assembly/tagsync.xml d1b83df42 
  src/main/assembly/usersync.xml d170d8c1c 
  storm-agent/pom.xml a084e6891 
  tagsync/pom.xml e98cf63dc 
  ugsync/ldapconfigchecktool/ldapconfigcheck/pom.xml d49001a65 
  
ugsync/ldapconfigchecktool/ldapconfigcheck/src/main/java/org/apache/ranger/ldapconfigcheck/LdapConfig.java
 9a77cedf7 
  ugsync/pom.xml f4c24e739 
  unixauthclient/pom.xml cd3d15604 
  unixauthservice/pom.xml 2c0ed2eef 


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


Testing
---

Tested plugins: HDFS, Yarn, Storm (uses Hadoop 2.7.1), Knox, HBase, KMS, Sqoop, 
Kafka, Solr, usersync. Test admin service works OK.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1935:

Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch, 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

Re: Review Request 68083: RANGER-2167 - Upgrade to Apache parent pom version 20

[Colm O hEigeartaigh]

> On Aug. 1, 2018, 5:36 a.m., bhavik patel wrote:
> > @Colm Can you please verify some basic functionality of ranger kms?

Yes I've tested creating some encryption keys in HDFS and storing them in the 
Ranger KMS.


- Colm


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


On July 27, 2018, 3:28 p.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68083/
> ---
> 
> (Updated July 27, 2018, 3:28 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-2167
> https://issues.apache.org/jira/browse/RANGER-2167
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> This task is to upgrade to the Apache parent pom version 20. This 
> necessitates a PMD upgrade and quite a few fixes are required as a result. 
> One notable change is to switch the KMS Keystore implementation to use 
> ConcurrentHashMap instead of HashTable.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerValiditySchedule.java
>  55f787d23 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidator.java
>  ed5aa8d41 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidityScheduleValidator.java
>  f34d124d6 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceACLs.java
>  34098fab6 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
>  e16148d4b 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerValidityScheduleEvaluator.java
>  b48ff3b68 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/model/validation/TestRangerValidator.java
>  f9b342832 
>   dev-support/ranger-pmd-ruleset.xml f03cda371 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java 
> cd5a8c2a8 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java
>  262447857 
>   
> plugin-kms/src/main/java/org/apache/ranger/authorization/kms/authorizer/RangerKmsAuthorizer.java
>  c3d75a14d 
>   
> plugin-kms/src/main/java/org/apache/ranger/services/kms/client/KMSClient.java 
> af0ac71f0 
>   
> plugin-nifi/src/main/java/org/apache/ranger/services/nifi/client/NiFiConnectionMgr.java
>  739bef62c 
>   pom.xml 8d7ea131e 
>   
> ranger-tools/src/test/java/org/apache/ranger/policyengine/RangerPolicyEnginePerformanceTest.java
>  11af0a84d 
>   security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 
> e4449df2e 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerKRBAuthenticationFilter.java
>  b4a3f9355 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerKrbFilter.java
>  ca0d17eb6 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java
>  a3ff825dd 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceService.java
>  df3fdb57c 
>   security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java 
> b0b011022 
> 
> 
> Diff: https://reviews.apache.org/r/68083/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>

Review Request 68083: RANGER-2167 - Upgrade to Apache parent pom version 20

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

This task is to upgrade to the Apache parent pom version 20. This necessitates 
a PMD upgrade and quite a few fixes are required as a result. One notable 
change is to switch the KMS Keystore implementation to use ConcurrentHashMap 
instead of HashTable.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerValiditySchedule.java
 55f787d23 
  
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidator.java
 ed5aa8d41 
  
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidityScheduleValidator.java
 f34d124d6 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceACLs.java
 34098fab6 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
 e16148d4b 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerValidityScheduleEvaluator.java
 b48ff3b68 
  
agents-common/src/test/java/org/apache/ranger/plugin/model/validation/TestRangerValidator.java
 f9b342832 
  dev-support/ranger-pmd-ruleset.xml f03cda371 
  kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java cd5a8c2a8 
  
plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java
 262447857 
  
plugin-kms/src/main/java/org/apache/ranger/authorization/kms/authorizer/RangerKmsAuthorizer.java
 c3d75a14d 
  plugin-kms/src/main/java/org/apache/ranger/services/kms/client/KMSClient.java 
af0ac71f0 
  
plugin-nifi/src/main/java/org/apache/ranger/services/nifi/client/NiFiConnectionMgr.java
 739bef62c 
  pom.xml 8d7ea131e 
  
ranger-tools/src/test/java/org/apache/ranger/policyengine/RangerPolicyEnginePerformanceTest.java
 11af0a84d 
  security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 
e4449df2e 
  
security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerKRBAuthenticationFilter.java
 b4a3f9355 
  
security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerKrbFilter.java
 ca0d17eb6 
  
security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java 
a3ff825dd 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceService.java
 df3fdb57c 
  security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java 
b0b011022 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2167) Upgrade to Apache parent pom version 20

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2167:

Attachment: 0001-RANGER-2167-Upgrade-to-Apache-parent-pom-version-20.patch

> Upgrade to Apache parent pom version 20
> ---
>
> Key: RANGER-2167
> URL: https://issues.apache.org/jira/browse/RANGER-2167
> Project: Ranger
>  Issue Type: Task
>  Components: admin, plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2167-Upgrade-to-Apache-parent-pom-version-20.patch
>
>
> This task is to upgrade to the Apache parent pom version 20. This 
> necessitates a PMD upgrade and quite a few fixes are required as a result. 
> One notable change is to switch the KMS Keystore implementation to use 
> ConcurrentHashMap instead of HashTable.



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

[jira] [Commented] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-1935:
-

Yes, working on it at the moment.

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

[Colm O hEigeartaigh]

+1. (Minor thing - the NOTICE year needs to be updated).

Colm.

On Mon, Jul 9, 2018 at 3:16 PM, Nitin Galave  wrote:

> 1. Successfully extracted tar file.
> 2. Clean, build and test ran successfully.
>
> +1
>
> Thanks,
>
> Nitin Galave.
>
> On Mon, Jul 9, 2018 at 10:29 AM Bhavik Patel 
> wrote:
>
> > +1 for Apache Ranger 1.1.0 rc2.
> >
> > Regard,
> > Bhavik Patel
> >
> > On Sun, Jul 8, 2018 at 1:55 PM, Madhan Neethiraj 
> > wrote:
> >
> > > +1 for Apache Ranger 1.1.0 rc2.
> > >
> > > Thanks,
> > > Madhan
> > >
> > >
> > >
> > > On 7/5/18, 12:56 PM, "Velmurugan Periasamy"  wrote:
> > >
> > > Hello Rangers:
> > >
> > > Thank you for your contribution to Apache Ranger community. Apache
> > > Ranger 1.1.0 release candidate #2 is now available for a vote within
> dev
> > > community. Note: RC1 (
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-
> > > rc1/) is canceled due to
> > https://issues.apache.org/jira/browse/RANGER-1951.
> > >
> > >
> > > Links to RC2 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.1.0-rc2 (last
> commit
> > > id:  1732536f1de4ac3f1699f660e089385487004261)
> > >
> > >
> > > Sources for the release:
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz
> > >
> > >
> > > Source release verification:
> > >
> > > PGP Signature:
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.asc
> > >
> > > MD5/SHA Hashes:
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.mds
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.sha1
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.sha256
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.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.1.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,
> > > Vel
> > >
> > >
> > >
> > >
> > >
> >
>
>
> --
>
>
> *Thanks,Nitin Galave.*
>



-- 
Colm O hEigeartaigh

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

[jira] [Commented] (RANGER-2148) Update Ranger Hive dependency version to 3.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-2148:
-

Is this targeted for 2.0.0? I have some work done on this already - in 
conjunction with the upgrade to Hadoop 3.x

> Update Ranger Hive dependency version to 3.0 
> -
>
> Key: RANGER-2148
> URL: https://issues.apache.org/jira/browse/RANGER-2148
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Critical
> Fix For: master
>
>
> Update Ranger Hive dependency version to 3.0 



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

Re: Ranger 1.1 release

[Colm O hEigeartaigh]

+1.

Colm.

On Sun, Jun 24, 2018 at 9:18 PM, Zsombor Gegesy  wrote:

> +1 - I believe in the "release early release often" mantra :)
>
>
> Regards,
>  Zsombor
>
> On Sun, Jun 24, 2018 at 5:56 PM, Srikanth Venkat 
> wrote:
>
> > +1, it would be nice to have a Ranger release baseline that aligns with
> > Atlas 1.0.
> > Thanks Vel for taking the initiative!
> >
> > Thx
> > Srikanth Venkat
> > sven...@hortonworks.com
> >
> > On 6/22/18, 10:24 PM, "Balaji Ganesan" 
> > wrote:
> >
> > +1. Vel, thanks for taking the initiative.
> >
> > On Fri, Jun 22, 2018 at 7:51 PM Jianhua Peng  >
> > wrote:
> >
> > > +1
> > >
> > > Thank you,
> > > Jianhua Peng.
> > >
> > > On 2018/06/22 16:25:45, Velmurugan Periasamy 
> wrote:
> > > > Rangers:
> > > >
> > > > Now that support for Atlas 1.0 is added (
> > > https://issues.apache.org/jira/browse/RANGER-2136 <
> > > https://issues.apache.org/jira/browse/RANGER-2136>), I propose to
> > release
> > > Ranger 1.1 (tentative first week of July).
> > > >
> > > > I request the community to resolve open JIRA’s marked for 1.1 in
> > the
> > > next couple of weeks or move them to next release. My proposal is
> to
> > call
> > > next release 2.0 and update master to 2.0.0-SNAPSHOT.
> > > >
> > > > Thank you,
> > > > Vel
> > >
> >
> >
> >
>



-- 
Colm O hEigeartaigh

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

Review Request 67635: RANGER-2136 - Upgrade to the released version of Atlas 1.0.0

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

We should update to the released version of Atlas 1.0.0.


Diffs
-

  pom.xml 95ba4604b 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2136) Upgrade to the released version of Atlas 1.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2136:

Attachment: 0001-RANGER-2136-Upgrade-to-the-released-version-of-Atlas.patch

> Upgrade to the released version of Atlas 1.0.0
> --
>
> Key: RANGER-2136
> URL: https://issues.apache.org/jira/browse/RANGER-2136
> Project: Ranger
>  Issue Type: Task
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: 
> 0001-RANGER-2136-Upgrade-to-the-released-version-of-Atlas.patch
>
>
> We should update to the released version of Atlas 1.0.0.



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

[jira] [Created] (RANGER-2136) Upgrade to the released version of Atlas 1.0.0

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2136:
---

 Summary: Upgrade to the released version of Atlas 1.0.0
 Key: RANGER-2136
 URL: https://issues.apache.org/jira/browse/RANGER-2136
 Project: Ranger
  Issue Type: Task
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.1.0


We should update to the released version of Atlas 1.0.0.



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

Review Request 66690: RANGER-2072 - Update HBase to 1.3.2

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

This task is to upgrade the HBase dependency to 1.3.2.


Diffs
-

  
hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessorBase.java
 f34bc126 
  pom.xml bf363f8c 
  
ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
 6ab595a3 


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


Testing
---

Tested authorization works correctly with a HBase 1.3.2 distribution.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2072) Update HBase to 1.3.2

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2072:

Attachment: 0001-RANGER-2072-Update-HBase-to-1.3.2.patch

> Update HBase to 1.3.2
> -
>
> Key: RANGER-2072
> URL: https://issues.apache.org/jira/browse/RANGER-2072
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: 0001-RANGER-2072-Update-HBase-to-1.3.2.patch
>
>
> This task is to upgrade the HBase dependency to 1.3.2.



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

[jira] [Created] (RANGER-2072) Update HBase to 1.3.2

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2072:
---

 Summary: Update HBase to 1.3.2
 Key: RANGER-2072
 URL: https://issues.apache.org/jira/browse/RANGER-2072
 Project: Ranger
  Issue Type: Improvement
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.1.0


This task is to upgrade the HBase dependency to 1.3.2.



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

Re: Review Request 66079: RANGER-1808:Write unit test for RANGER-1672 kylin plugin

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On March 28, 2018, 8:46 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66079/
> ---
> 
> (Updated March 28, 2018, 8:46 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1808
> https://issues.apache.org/jira/browse/RANGER-1808
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Write unit test for RANGER-1672 kylin plugin
> 
> 
> Diffs
> -
> 
>   plugin-kylin/pom.xml bfce4c1 
>   
> plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java
>  PRE-CREATION 
>   
> plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizerTest.java
>  PRE-CREATION 
>   plugin-kylin/src/test/resources/applicationContext.xml PRE-CREATION 
>   plugin-kylin/src/test/resources/kylin-policies.json PRE-CREATION 
>   plugin-kylin/src/test/resources/kylin.properties PRE-CREATION 
>   plugin-kylin/src/test/resources/kylinSecurity.xml PRE-CREATION 
>   plugin-kylin/src/test/resources/log4j.properties PRE-CREATION 
>   plugin-kylin/src/test/resources/ranger-kylin-security.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66079/diff/3/
> 
> 
> Testing
> ---
> 
> Test
> 1.eclipse->Run as->Junit Test
> 2.mvn test
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

[jira] [Updated] (RANGER-1808) Write unit test for RANGER-1672

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1808:

Fix Version/s: 1.1.0

> Write unit test for RANGER-1672
> ---
>
> Key: RANGER-1808
> URL: https://issues.apache.org/jira/browse/RANGER-1808
> Project: Ranger
>  Issue Type: Sub-task
>  Components: plugins
>Affects Versions: master, 1.1.0
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
>  Labels: newbie, patch
> Fix For: 1.1.0
>
> Attachments: 
> 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, 
> kylin-policies.json
>
>
> Write unit test for RANGER-1672 kylin plugin



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

Re: Review Request 66275: Add hbase policy and click the 'Test Connection' button. Connection Failed.

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On March 26, 2018, 6:42 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66275/
> ---
> 
> (Updated March 26, 2018, 6:42 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2033
> https://issues.apache.org/jira/browse/RANGER-2033
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Clone the lastest code from 
> https://git-wip-us.apache.org/repos/asf/ranger.git. Build the source and 
> install Ranger. Then do as follows:
> 1. Add hbase policy;
> 2. Input right parameter;
> 3. Click the 'Test Connection' button.
> The error information is as follows:
> Unable to retrieve any files using given parameters, You can still save the 
> repository and start creating policies, but you would not be able to use 
> autocomplete for resource names. Check ranger_admin.log for more info.
> 
> java.lang.NoClassDefFoundError: 
> org/apache/hadoop/hbase/ZooKeeperConnectionException.
> org/apache/hadoop/hbase/ZooKeeperConnectionException.
> org.apache.hadoop.hbase.ZooKeeperConnectionException.
> 
> The reason for the error is that the hbase-client-1.2.6.jar file loss under 
> ./ews/webapp/WEB-INF/classes/ranger-plugins/hbase directory.
> 
> 
> Diffs
> -
> 
>   pom.xml 413c23b 
> 
> 
> Diff: https://reviews.apache.org/r/66275/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Review Request 66275: Add hbase policy and click the 'Test Connection' button. Connection Failed.

[Colm O hEigeartaigh]

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



Any reason not to apply it to the ranger-1.0 branch as well?

- Colm O hEigeartaigh


On March 26, 2018, 6:42 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66275/
> ---
> 
> (Updated March 26, 2018, 6:42 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2033
> https://issues.apache.org/jira/browse/RANGER-2033
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Clone the lastest code from 
> https://git-wip-us.apache.org/repos/asf/ranger.git. Build the source and 
> install Ranger. Then do as follows:
> 1. Add hbase policy;
> 2. Input right parameter;
> 3. Click the 'Test Connection' button.
> The error information is as follows:
> Unable to retrieve any files using given parameters, You can still save the 
> repository and start creating policies, but you would not be able to use 
> autocomplete for resource names. Check ranger_admin.log for more info.
> 
> java.lang.NoClassDefFoundError: 
> org/apache/hadoop/hbase/ZooKeeperConnectionException.
> org/apache/hadoop/hbase/ZooKeeperConnectionException.
> org.apache.hadoop.hbase.ZooKeeperConnectionException.
> 
> The reason for the error is that the hbase-client-1.2.6.jar file loss under 
> ./ews/webapp/WEB-INF/classes/ranger-plugins/hbase directory.
> 
> 
> Diffs
> -
> 
>   pom.xml 413c23b 
> 
> 
> Diff: https://reviews.apache.org/r/66275/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Review Request 66079: RANGER-1808:Write unit test for RANGER-1672 kylin plugin

[Colm O hEigeartaigh]

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



Can we re-use the value for ${springframework.security.version} as it's now 
4.2.4.RELEASE?

- Colm O hEigeartaigh


On March 19, 2018, 3:32 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66079/
> ---
> 
> (Updated March 19, 2018, 3:32 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1808
> https://issues.apache.org/jira/browse/RANGER-1808
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Write unit test for RANGER-1672 kylin plugin
> 
> 
> Diffs
> -
> 
>   plugin-kylin/pom.xml bfce4c1 
>   
> plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java
>  PRE-CREATION 
>   
> plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizerTest.java
>  PRE-CREATION 
>   plugin-kylin/src/test/resources/applicationContext.xml PRE-CREATION 
>   plugin-kylin/src/test/resources/kylin-policies.json PRE-CREATION 
>   plugin-kylin/src/test/resources/kylin.properties PRE-CREATION 
>   plugin-kylin/src/test/resources/kylinSecurity.xml PRE-CREATION 
>   plugin-kylin/src/test/resources/log4j.properties PRE-CREATION 
>   plugin-kylin/src/test/resources/ranger-kylin-security.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66079/diff/2/
> 
> 
> Testing
> ---
> 
> Test
> 1.eclipse->Run as->Junit Test
> 2.mvn test
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: [VOTE] Apache Ranger Release 1.0.0-rc1

[Colm O hEigeartaigh]

We are not conforming to the Apache release guidelines surrounding hashes:

http://www.apache.org/dev/release-distribution#sigs-and-sums

The names of signature and checksum files MUST be formed by adding to the
name of the artifact the following suffixes:

   - .asc for a (ASCII armored) PGP signature
   - .sha1 for a SHA-1 checksum
   - .sha256 for a SHA-256 checksum
   - .sha512 for a SHA-512 checksum
   - .md5 for a MD5 checksum

Is there time to fix it and call another vote? I don't really feel like
-1'ing it as the digests are already there, but we are violating the "MUST"
in the release policy.

Colm.

On Thu, Mar 15, 2018 at 2:40 PM, Ramesh Mani <rm...@hortonworks.com> wrote:

> +1 for Apache Ranger 1.0.0 rc1 release
>
> - verified the build
> - verified some source files
> - verified MD5/SHA and PGP signature.
>
>
> Thanks,
> Ramesh
>
> On 3/14/18, 6:27 PM, "Sailaja Polavarapu" <spolavar...@hortonworks.com>
> 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.
> >
>
>


-- 
Colm O hEigeartaigh

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

Re: Review Request 66079: RANGER-1808:Write unit test for RANGER-1672 kylin plugin

[Colm O hEigeartaigh]

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



Minor quibble - avoid creating unnecessary variables, e.g.:

> ProjectInstance project = getProjectInstance(name);
> return project;

could simply be:

return getProjectInstance(name);

Same goes for:

> ProjectInstance project = ProjectInstance.create(name, owner, description, 
> overrideProps, realizationEntries,
models);
>   return project;

- Colm O hEigeartaigh


On March 15, 2018, 6:55 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66079/
> ---
> 
> (Updated March 15, 2018, 6:55 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1808
> https://issues.apache.org/jira/browse/RANGER-1808
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Write unit test for RANGER-1672 kylin plugin
> 
> 
> Diffs
> -
> 
>   plugin-kylin/pom.xml bfce4c1 
>   
> plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java
>  PRE-CREATION 
>   
> plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizerTest.java
>  PRE-CREATION 
>   plugin-kylin/src/test/resources/applicationContext.xml PRE-CREATION 
>   plugin-kylin/src/test/resources/kylin-policies.json PRE-CREATION 
>   plugin-kylin/src/test/resources/kylin.properties PRE-CREATION 
>   plugin-kylin/src/test/resources/kylinSecurity.xml PRE-CREATION 
>   plugin-kylin/src/test/resources/log4j.properties PRE-CREATION 
>   plugin-kylin/src/test/resources/ranger-kylin-security.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66079/diff/1/
> 
> 
> Testing
> ---
> 
> Test
> 1.eclipse->Run as->Junit Test
> 2.mvn test
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Atlas policies to filter access

[Colm O hEigeartaigh]

I was able to get past the problems in the previous mail. I'm trying to use
the v2 API but authorization doesn't seem to kick in:

curl -v -u username:password
http://localhost:21000/api/atlas/v2/search/basic?typeName=hdfs_path

This call succeeds without the Ranger plugin being called. In
'conf/application.properties' I have "atlas.authorizer.impl = RANGER" and
there are no obvious errors in the logs. Is the Atlas authorization
framework integrated with the newer REST API yet?

Colm.

On Tue, Mar 13, 2018 at 5:49 PM, Colm O hEigeartaigh <cohei...@apache.org>
wrote:

> Thanks Madhan. Just to clarify - ATLAS-2459 is not yet applied, so do I
> have to apply this manually to get this to work?
>
> When trying to install the current Ranger 1.1.0-SNAPSHOT plugin with the
> latest Atlas SNAPSHOT distribution I see an error in application.log:
>
> java.lang.NoClassDefFoundError: org/codehaus/jackson/jaxrs/
> JacksonJsonProvider
> at org.apache.ranger.plugin.util.RangerRESTClient.buildClient(
> RangerRESTClient.java:209)
>
> I'm wondering if there is a conflict between the jackson-jaxrs-1.9.13.jar
> in the Atlas plugin lib and the version of Jackson used in Atlas?
>
> Colm.
>
> On Mon, Mar 12, 2018 at 9:14 PM, Madhan Neethiraj <mad...@apache.org>
> wrote:
>
>> Colm,
>>
>> Perhaps you are using the Atlas service-def from Ranger master, against
>> Atlas from branch-0.8 (or from master before ATLAS-2459)? Earlier Atlas
>> versions use a different authorization model, which don't allow access
>> controls at instance/type levels. Please try with Atlas from master branch.
>>
>> Hope this helps.
>>
>> Madhan
>>
>>
>>
>>
>> On 3/12/18, 11:16 AM, "Colm O hEigeartaigh" <cohei...@apache.org> wrote:
>>
>> Hi all,
>>
>> I'm using the Ranger plugin to secure access to Atlas. How can I
>> create a
>> policy in Ranger to allow a user access to a subset of the entities?
>> So for
>> example, I want to allow "alice" to "read" all entities that have a
>> given
>> type. I created an authorization policy of "type" "Table", but I get
>> the
>> following error:
>>
>> curl -u alice:password "http://localhost:21000/api/at
>> las/entities?type=Table
>> "
>> Error 403 {AuthorizationError:You are not
>> authorized for READ on [ENTITY] : *}
>>
>>     How can I allow authorization for a subset of the entities? I guess I
>> need
>> an authorization policy for "Entity" but it's not clear what values
>> apart
>> from "*" are supported here?
>>
>> 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

Some recent commits missing from master

[Colm O hEigeartaigh]

Hi all,

A few recent commits appear to have been made directly onto the 1.0 branch
instead of to master and then backporting

commit 3d341a4c2429cae259b831b112c6d65eaa12a2e1 (tag: release-1.0.0-rc0,
origin/ranger-1.0, ranger-1.0)
Author: pradeep <prad...@apache.org>
Date:   Sat Mar 10 15:28:40 2018 +0530

RANGER-1991: Import policy failure fix caused by static code analysis
fix

commit 79d177be7bc6d511e8902d963802c9550608bebf
Author: ni3galave <nitin.gal...@gmail.com>
Date:   Sat Mar 10 20:35:25 2018 +0530

RANGER-2014: Unable to see policy detail in view policy mode after
updating recursive flag

Signed-off-by: pradeep <prad...@apache.org>



-- 
Colm O hEigeartaigh

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

Review Request 66072: RANGER-2022 - Atlas plugin install.properties is missing component location

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

The Atlas plugin install.properties is missing the component location.


Diffs
-

  plugin-atlas/scripts/install.properties 0962ab07 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2022) Atlas plugin install.properties is missing component location

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2022:

Attachment: 0001-RANGER-2022-Atlas-plugin-install.properties-is-missi.patch

> Atlas plugin install.properties is missing component location
> -
>
> Key: RANGER-2022
> URL: https://issues.apache.org/jira/browse/RANGER-2022
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: 
> 0001-RANGER-2022-Atlas-plugin-install.properties-is-missi.patch
>
>
> The Atlas plugin install.properties is missing the component location.



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

[jira] [Created] (RANGER-2022) Atlas plugin install.properties is missing component location

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2022:
---

 Summary: Atlas plugin install.properties is missing component 
location
 Key: RANGER-2022
 URL: https://issues.apache.org/jira/browse/RANGER-2022
 Project: Ranger
  Issue Type: Improvement
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.1.0


The Atlas plugin install.properties is missing the component location.



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

Re: Atlas policies to filter access

[Colm O hEigeartaigh]

Thanks Madhan. Just to clarify - ATLAS-2459 is not yet applied, so do I
have to apply this manually to get this to work?

When trying to install the current Ranger 1.1.0-SNAPSHOT plugin with the
latest Atlas SNAPSHOT distribution I see an error in application.log:

java.lang.NoClassDefFoundError:
org/codehaus/jackson/jaxrs/JacksonJsonProvider
at
org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:209)

I'm wondering if there is a conflict between the jackson-jaxrs-1.9.13.jar
in the Atlas plugin lib and the version of Jackson used in Atlas?

Colm.

On Mon, Mar 12, 2018 at 9:14 PM, Madhan Neethiraj <mad...@apache.org> wrote:

> Colm,
>
> Perhaps you are using the Atlas service-def from Ranger master, against
> Atlas from branch-0.8 (or from master before ATLAS-2459)? Earlier Atlas
> versions use a different authorization model, which don't allow access
> controls at instance/type levels. Please try with Atlas from master branch.
>
> Hope this helps.
>
> Madhan
>
>
>
>
> On 3/12/18, 11:16 AM, "Colm O hEigeartaigh" <cohei...@apache.org> wrote:
>
> Hi all,
>
> I'm using the Ranger plugin to secure access to Atlas. How can I
> create a
> policy in Ranger to allow a user access to a subset of the entities?
> So for
> example, I want to allow "alice" to "read" all entities that have a
> given
> type. I created an authorization policy of "type" "Table", but I get
> the
> following error:
>
> curl -u alice:password "http://localhost:21000/api/
> atlas/entities?type=Table
> "
> Error 403 {AuthorizationError:You are not
> authorized for READ on [ENTITY] : *}
>
> How can I allow authorization for a subset of the entities? I guess I
> need
> an authorization policy for "Entity" but it's not clear what values
> apart
> from "*" are supported here?
>
> Colm.
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
>
>
>


-- 
Colm O hEigeartaigh

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

Atlas policies to filter access

[Colm O hEigeartaigh]

Hi all,

I'm using the Ranger plugin to secure access to Atlas. How can I create a
policy in Ranger to allow a user access to a subset of the entities? So for
example, I want to allow "alice" to "read" all entities that have a given
type. I created an authorization policy of "type" "Table", but I get the
following error:

curl -u alice:password "http://localhost:21000/api/atlas/entities?type=Table
"
Error 403 {AuthorizationError:You are not
authorized for READ on [ENTITY] : *}

How can I allow authorization for a subset of the entities? I guess I need
an authorization policy for "Entity" but it's not clear what values apart
from "*" are supported here?

Colm.


-- 
Colm O hEigeartaigh

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

Re: Review Request 61021: RANGER-1672:Ranger supports plugin to enable, monitor and manage apache kylin

[Colm O hEigeartaigh]

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



I haven't tested it as the setup is too complicated, but the UI changes look 
fine, so I would say to go ahead and merge.

- Colm O hEigeartaigh


On March 5, 2018, 8:23 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61021/
> ---
> 
> (Updated March 5, 2018, 8:23 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1672
> https://issues.apache.org/jira/browse/RANGER-1672
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger supports plugin to enable, monitor and manage apache kylin
> 
> 
> Diffs
> -
> 
>   agents-common/scripts/enable-agent.sh 7033f79 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java
>  899bcac 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/PasswordUtils.java 
> 6ba42d4 
>   agents-common/src/main/resources/service-defs/ranger-servicedef-kylin.json 
> PRE-CREATION 
>   plugin-kylin/.gitignore PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-audit-changes.cfg PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-audit.xml PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-security-changes.cfg PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-security.xml PRE-CREATION 
>   plugin-kylin/conf/ranger-policymgr-ssl-changes.cfg PRE-CREATION 
>   plugin-kylin/conf/ranger-policymgr-ssl.xml PRE-CREATION 
>   plugin-kylin/pom.xml PRE-CREATION 
>   plugin-kylin/scripts/install.properties PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizer.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/RangerServiceKylin.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/client/KylinClient.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/client/KylinResourceMgr.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/client/json/model/KylinProjectResponse.java
>  PRE-CREATION 
>   pom.xml 08593aa 
>   ranger-kylin-plugin-shim/.gitignore PRE-CREATION 
>   ranger-kylin-plugin-shim/pom.xml PRE-CREATION 
>   
> ranger-kylin-plugin-shim/src/main/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizer.java
>  PRE-CREATION 
>   src/main/assembly/admin-web.xml 29d728a 
>   src/main/assembly/plugin-kylin.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/61021/diff/4/
> 
> 
> Testing
> ---
> 
> Tested
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

[jira] [Commented] (RANGER-1326) Fix remaining licensing issues

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-1326:
-

Hi [~vperiasamy], we really need to get this done for 1.0.0 - we can't ship a 
1.0.0 product with licensing concerns IMO.

> Fix remaining licensing issues
> --
>
> Key: RANGER-1326
> URL: https://issues.apache.org/jira/browse/RANGER-1326
> Project: Ranger
>  Issue Type: Bug
>Affects Versions: 0.6.2
>    Reporter: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.1.0
>
>
> We need to fix the remaining licensing issues as raised by Jusin:
> For items not fixed please see [1][2][3].
> Also note that with json2.js license it seems a little unclear to me and may 
> be under the JSON license. It does have “public domain” in the code so it may 
> be OK, it still however needs to be added to LICENSE. Just be careful as the 
> JSON license no longer allowed in Apache software and it is considered 
> category X. [4] In this case you do have a few months grace to remove this 
> [5] but you need to call it out in NOTICE and it still needs to be removed by 
> end of April. [5]
> 1. 
> https://lists.apache.org/thread.html/6949e2f048b07478c861a675ad8e98d750e0f786b272a6afc69df78e@%3Cgeneral.incubator.apache.org%3E
> 2. 
> https://lists.apache.org/thread.html/9552c63b71a38ed75cd252463e788408aa4a9a05abeba36168df5a12@%3Cgeneral.incubator.apache.org%3E
> 3. 
> https://lists.apache.org/thread.html/de169a09f7527fbc3549518f0227ba40ee8524c6e60ba8105d82479b@%3Cgeneral.incubator.apache.org%3E
> 4. https://www.apache.org/legal/resolved#category-x
> 5. 
> https://lists.apache.org/thread.html/bb18f942ce7eb83c11438303c818b885810fb76385979490366720d5@%3Clegal-discuss.apache.org%3E



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

[jira] [Updated] (RANGER-2012) Update Apache parent pom version

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2012:

Priority: Trivial  (was: Major)

> Update Apache parent pom version
> 
>
> Key: RANGER-2012
> URL: https://issues.apache.org/jira/browse/RANGER-2012
> Project: Ranger
>  Issue Type: Improvement
>  Components: build-infra
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 1.1.0
>
> Attachments: 0001-RANGER-2012-Update-Apache-parent-pom-version.patch
>
>
> This task is to update the Apache parent pom version - see for example 
> https://issues.apache.org/jira/browse/MPOM-118



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

Review Request 65926: RANGER-2012 - Update Apache parent pom version

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

This task is to update the Apache parent pom version - see for example 
https://issues.apache.org/jira/browse/MPOM-118


Diffs
-

  pom.xml 08593aad 


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


Testing
---


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-2012) Update Apache parent pom version

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-2012:

Attachment: 0001-RANGER-2012-Update-Apache-parent-pom-version.patch

> Update Apache parent pom version
> 
>
> Key: RANGER-2012
> URL: https://issues.apache.org/jira/browse/RANGER-2012
> Project: Ranger
>  Issue Type: Improvement
>  Components: build-infra
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: 0001-RANGER-2012-Update-Apache-parent-pom-version.patch
>
>
> This task is to update the Apache parent pom version - see for example 
> https://issues.apache.org/jira/browse/MPOM-118



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

[jira] [Created] (RANGER-2012) Update Apache parent pom version

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-2012:
---

 Summary: Update Apache parent pom version
 Key: RANGER-2012
 URL: https://issues.apache.org/jira/browse/RANGER-2012
 Project: Ranger
  Issue Type: Improvement
  Components: build-infra
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.1.0


This task is to update the Apache parent pom version - see for example 
https://issues.apache.org/jira/browse/MPOM-118



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

Failing Ranger test on master

[Colm O hEigeartaigh]

We have a failing Ranger test on master:

[ERROR] Failures:
[ERROR]
TestPolicyEngine.testValiditySchedularApplicable:553->runValiditySchedulerTests:596
Applicable every Wednesday or Saturday or 1st of month starting at 10 past
noon hour PST for 2 days and 10 hours

The cause seems to be that it is dependent on the timezone - it works
correctly at PST but not at GMT.

Colm.


-- 
Colm O hEigeartaigh

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

Re: Review Request 61021: RANGER-1672:Ranger supports plugin to enable, monitor and manage apache kylin

[Colm O hEigeartaigh]

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



Could you put together some instructions as to how to test this with a sample 
deployment?

- Colm O hEigeartaigh


On March 5, 2018, 8:23 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61021/
> ---
> 
> (Updated March 5, 2018, 8:23 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1672
> https://issues.apache.org/jira/browse/RANGER-1672
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger supports plugin to enable, monitor and manage apache kylin
> 
> 
> Diffs
> -
> 
>   agents-common/scripts/enable-agent.sh 7033f79 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java
>  899bcac 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/PasswordUtils.java 
> 6ba42d4 
>   agents-common/src/main/resources/service-defs/ranger-servicedef-kylin.json 
> PRE-CREATION 
>   plugin-kylin/.gitignore PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-audit-changes.cfg PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-audit.xml PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-security-changes.cfg PRE-CREATION 
>   plugin-kylin/conf/ranger-kylin-security.xml PRE-CREATION 
>   plugin-kylin/conf/ranger-policymgr-ssl-changes.cfg PRE-CREATION 
>   plugin-kylin/conf/ranger-policymgr-ssl.xml PRE-CREATION 
>   plugin-kylin/pom.xml PRE-CREATION 
>   plugin-kylin/scripts/install.properties PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizer.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/RangerServiceKylin.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/client/KylinClient.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/client/KylinResourceMgr.java
>  PRE-CREATION 
>   
> plugin-kylin/src/main/java/org/apache/ranger/services/kylin/client/json/model/KylinProjectResponse.java
>  PRE-CREATION 
>   pom.xml 08593aa 
>   ranger-kylin-plugin-shim/.gitignore PRE-CREATION 
>   ranger-kylin-plugin-shim/pom.xml PRE-CREATION 
>   
> ranger-kylin-plugin-shim/src/main/java/org/apache/ranger/authorization/kylin/authorizer/RangerKylinAuthorizer.java
>  PRE-CREATION 
>   src/main/assembly/admin-web.xml 29d728a 
>   src/main/assembly/plugin-kylin.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/61021/diff/4/
> 
> 
> Testing
> ---
> 
> Tested
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Reviews

[Colm O hEigeartaigh]

Yes I ran into this issue before - you can explicitly ask for permission to
resolve RRs from INFRA. I resolved a bunch of outstanding issue there - the
easiest way to check is just to click on the JIRA link and see if it's
resolved or not.

Colm.

On Mon, Mar 5, 2018 at 10:02 AM, Zsombor <gzsom...@gmail.com> wrote:

> Hi Rangers,
>
>  Could you please mark your review requests as 'submitted' when it's
> merged into master ?
> It's not clear, if there are a separate admin privileges to mark
> someone else's RR - or at least I don't have that privileges.
> Currently, there are 53 open requests:
> https://reviews.apache.org/dashboard/?group=ranger=to-group and
> it's very hard to find which one is still open.
> I bet, at least 5, but it's hard to find the needle in the haystack.
>
>
> Thanks,
>  Zsombor
>



-- 
Colm O hEigeartaigh

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

Configuration fields in ranger-kafka-security.xml

[Colm O hEigeartaigh]

Hi all,

I noticed when installing the Kafka plugin from 1.0.0-SNAPSHOT, that it
adds the following in ranger-kafka-security.xml:



ranger.plugin.kafka.policy.rest.client.connection.timeoutMs
12

RangerRestClient Connection Timeout in Milli Seconds




ranger.plugin.kafka.policy.rest.client.read.timeoutMs
3

RangerRestClient read Timeout in Milli Seconds



ranger.policy.rest.client.connection.timeoutMs
12


ranger.policy.rest.client.read.timeoutMs
3


What is the difference between
"ranger.plugin.kafka.policy.rest.client.connection.timeoutMs" and
"ranger.policy.rest.client.connection.timeoutMs"?




-- 
Colm O hEigeartaigh

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

Re: Review Request 65777: RANGER-1967 - Kafka 1.0 support

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On Feb. 27, 2018, 11:17 a.m., Zsombor Gegesy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65777/
> ---
> 
> (Updated Feb. 27, 2018, 11:17 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1967
> https://issues.apache.org/jira/browse/RANGER-1967
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The API changes are not too big, however running Kafka in embedded mode 
> turned out to be a bit trickier beast. I had to add a couple of new flags, 
> otherwise it would wait for 2 other broker to join.
>  The commit also contains logging changes, even a test log4j configuration, 
> just to make the debugging easier.
> 
> 
> Diffs
> -
> 
>   agents-audit/pom.xml 4fa44c5f 
>   plugin-kafka/pom.xml f644646b 
>   
> plugin-kafka/src/main/java/org/apache/ranger/authorization/kafka/authorizer/RangerKafkaAuthorizer.java
>  b3d5a74d 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java
>  4ea39ed7 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerSASLSSLTest.java
>  fb541cd3 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
>  fb0a2c0f 
>   plugin-kafka/src/test/resources/log4j.properties PRE-CREATION 
>   pom.xml 294c422f 
>   ranger-kafka-plugin-shim/pom.xml f1aeee6f 
> 
> 
> Diff: https://reviews.apache.org/r/65777/diff/3/
> 
> 
> Testing
> ---
> 
> Unit & local tests
> 
> 
> Thanks,
> 
> Zsombor Gegesy
> 
>

Re: Review Request 65777: RANGER-1967 - Kafka 1.0 support

[Colm O hEigeartaigh]

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



Looks good, I tested Kerberos + Kafka 1.0.0 + Ranger authorization.

- Colm O hEigeartaigh


On Feb. 27, 2018, 11:17 a.m., Zsombor Gegesy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65777/
> ---
> 
> (Updated Feb. 27, 2018, 11:17 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1967
> https://issues.apache.org/jira/browse/RANGER-1967
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The API changes are not too big, however running Kafka in embedded mode 
> turned out to be a bit trickier beast. I had to add a couple of new flags, 
> otherwise it would wait for 2 other broker to join.
>  The commit also contains logging changes, even a test log4j configuration, 
> just to make the debugging easier.
> 
> 
> Diffs
> -
> 
>   agents-audit/pom.xml 4fa44c5f 
>   plugin-kafka/pom.xml f644646b 
>   
> plugin-kafka/src/main/java/org/apache/ranger/authorization/kafka/authorizer/RangerKafkaAuthorizer.java
>  b3d5a74d 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java
>  4ea39ed7 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerSASLSSLTest.java
>  fb541cd3 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
>  fb0a2c0f 
>   plugin-kafka/src/test/resources/log4j.properties PRE-CREATION 
>   pom.xml 294c422f 
>   ranger-kafka-plugin-shim/pom.xml f1aeee6f 
> 
> 
> Diff: https://reviews.apache.org/r/65777/diff/3/
> 
> 
> Testing
> ---
> 
> Unit & local tests
> 
> 
> Thanks,
> 
> Zsombor Gegesy
> 
>

Re: Review Request 65858: RANGER-2001:Similar to RANGER-1469, we should check whether the user or group has existed before the installer create a new user or group when user install usersync

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On March 1, 2018, 7:06 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65858/
> ---
> 
> (Updated March 1, 2018, 7:06 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2001
> https://issues.apache.org/jira/browse/RANGER-2001
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Similar to RANGER-1469, we should check whether the user or group has existed 
> before the installer create a new user or group when user install usersync
> 
> 
> Diffs
> -
> 
>   unixauthservice/scripts/setup.py 5ae9123 
> 
> 
> Diff: https://reviews.apache.org/r/65858/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

[jira] [Updated] (RANGER-1824) Upgrade Spring Framework to 3.2.18

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1824:

Fix Version/s: (was: 1.0.0)

> Upgrade Spring Framework to 3.2.18
> --
>
> Key: RANGER-1824
> URL: https://issues.apache.org/jira/browse/RANGER-1824
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Minor
> Attachments: 0001-RANGER-1824-Upgrade-Spring-Framework-to-3.2.18.patch
>
>
> When starting the Admin console, the following appears in the logs:
> 2017-10-02 10:00:35,651 [localhost-startStop-1] WARN  
> org.springframework.security.core.SpringSecurityCoreVersion 
> (SpringSecurityCoreVersion.java:60) -  You are advised to use Spring 
> 3.2.18.RELEASE or later with this version. You are running: 3.2.10.RELEASE
> We should update Spring to 3.2.18



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

[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1935:

Fix Version/s: (was: 1.0.0)

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

[jira] [Updated] (RANGER-1738) RangerYarnAuthorizer not compatible with Hadoop-3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1738:

Fix Version/s: (was: 1.0.0)

> RangerYarnAuthorizer not compatible with Hadoop-3.0.0
> -
>
> Key: RANGER-1738
> URL: https://issues.apache.org/jira/browse/RANGER-1738
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 0.7.1
>Reporter: Hong Shen
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Attachments: 
> 0001-RANGER-1738-RangerYarnAuthorizer-not-compatible-with.patch
>
>
> In the newest hadoop version 3.0.0, YarnAuthorizationProvider has changed.
> The new YarnAuthorizationProvider.java has change the methods checkPermission 
> and setPermission, 
> {code:title=YarnAuthorizationProvider.java|borderStyle=solid}
>   /**
>* Check if user has the permission to access the target object.
>* 
>* @param accessRequest
>*  the request object which contains all the access context info.
>* @return true if user can access the object, otherwise false.
>*/
>   public abstract boolean checkPermission(AccessRequest accessRequest);
>   /**
>* Set permissions for the target object.
>*
>* @param permissions
>*A list of permissions on the target object.
>* @param ugi User who sets the permissions.
>*/
>   public abstract void setPermission(List permissions,
>   UserGroupInformation ugi);
> {code}
> But the RangerYarnAuthorizer extends YarnAuthorizationProvider impletement 
> the old method.
> {code:title=RangerYarnAuthorizer.java|borderStyle=solid}
>   @Override
>   public void setPermission(PrivilegedEntity entity, Map<AccessType, 
> AccessControlList> permission, UserGroupInformation ugi) {
>...
>   @Override
>   public boolean checkPermission(AccessType accessType, PrivilegedEntity 
> entity, UserGroupInformation ugi) {
> {code}
> I think yarn plugin should also impletement the new method. I will add a 
> patch for it.



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

[jira] [Commented] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-1935:
-

Yes, can we add a 1.1.0 version that I can move it to?

> Upgrade Ranger to support Apache Hadoop 3.0.0
> -
>
> Key: RANGER-1935
> URL: https://issues.apache.org/jira/browse/RANGER-1935
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch
>
>
> This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some 
> notes about the upgrade:
> a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as 
> Hive only supports the older Hadoop version, so an exclusion and some 
> additional 3.0.0 dependencies need to be added.
> b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they 
> really should be renamed here). Therefore, we have no option but to package 
> Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the 
> Hadoop dependency.
> This is an initial patch to get some feedback. If there is broad agreement on 
> the upgrade I will test the distributions properly.



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

Re: Prep for ranger-1.0.0 release

[Colm O hEigeartaigh]

Thanks, please update the version on master to 1.1.0-SNAPSHOT as well when
you get a chance to avoid confusion.

Colm.

On Tue, Feb 27, 2018 at 11:50 PM, Sailaja Polavarapu <
spolavar...@hortonworks.com> wrote:

> FYI – ranger-1.0 branch is created with the pom files updated to 1.0.0
> version. From now on, only the patches that are required for 1.0.0 release
> should be cherry picked into this branch.
> Master branch is open for regular commits and will track for next release
> (1.1).
>
> Thanks,
> Sailaja.
>
> On 2/27/18, 1:48 PM, "Sailaja Polavarapu" <spolavar...@hortonworks.com>
> wrote:
>
> Thanks for all the feedback and +1s. I will be including latest
> version of kafka in ranger-1.0.0. But for Kylin, since there will be
> hadoop3 support release soon, it can be included in that.
> -Sailaja.
>
> On 2/23/18, 2:36 PM, "Zsombor Gegesy" <zsom...@apache.org> wrote:
>
> +1 for Ranger 1.0 !
>
> Regards,
>  Zsombor
>
> On Sat, Feb 24, 2018 at 5:03 AM, Velmurugan Periasamy <
> v...@apache.org>
> wrote:
>
> > +1 for Ranger 1.0 release.
> >
> > Thanks Sailaja for volunteering.
> >
> > From:  pengjianhua <35573...@qq.com>
> > Reply-To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
> > Date:  Friday, February 23, 2018 at 4:55 AM
> > To:  "dev@ranger.apache.org" <dev@ranger.apache.org>
> > Subject:  Re: Prep for ranger-1.0.0 release
> >
> > I agree with Colm's point of view. Zhangqiang am developing this
> issue
> > to upgrade Kafka whichwas delayed due to our Spring Festival.
> >
> > I also hope to merge the Apacke Kylin Plugin into the ranger
> 1.0.0. the
> > 2.3.0 version of the Apache kylin is being voted. The Apacke
> Kylin
> > Plugin of the ranger has been successfully applied in some
> business
> > projects.
> >
> >
> >
> > Jianhua Peng
> >
> > 在 2018年02月23日 17:36, Colm O hEigeartaigh 写道:
> > >  +1. It would be nice to get the Kafka upgrade in if possible,
> as
> > currently
> > >  we support a very old version of Kafka.
> > >
> > >  Colm.
> > >
> > >  On Fri, Feb 23, 2018 at 9:00 AM, Jianhua Peng <
> pengjian...@apache.org>
> > >  wrote:
> > >
> > >>  +1
> > >>
> > >>  On 2018/02/23 01:34:36, Sailaja Polavarapu <
> > spolavar...@hortonworks.com>
> > >>  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.
> > >>>
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>


-- 
Colm O hEigeartaigh

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

Re: Review Request 65777: RANGER-1967 - Kafka 1.0 support

[Colm O hEigeartaigh]

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



> JaasContext context = JaasContext.load(Type.SERVER, new 
> ListenerName("KafkaServer"), configs);

Should "KafkaServer" be configurable here?

Apart from that looks good to me - have you tested the plugin with a Kafka 
1.0.0 deployment?

- Colm O hEigeartaigh


On Feb. 24, 2018, 10:08 a.m., Zsombor Gegesy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65777/
> ---
> 
> (Updated Feb. 24, 2018, 10:08 a.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1967
> https://issues.apache.org/jira/browse/RANGER-1967
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The API changes are not too big, however running Kafka in embedded mode 
> turned out to be a bit trickier beast. I had to add a couple of new flags, 
> otherwise it would wait for 2 other broker to join.
>  The commit also contains logging changes, even a test log4j configuration, 
> just to make the debugging easier.
> 
> 
> Diffs
> -
> 
>   agents-audit/pom.xml 4fa44c5f 
>   plugin-kafka/pom.xml f644646b 
>   
> plugin-kafka/src/main/java/org/apache/ranger/authorization/kafka/authorizer/RangerKafkaAuthorizer.java
>  b3d5a74d 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java
>  4ea39ed7 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerSASLSSLTest.java
>  fb541cd3 
>   
> plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java
>  fb0a2c0f 
>   plugin-kafka/src/test/resources/log4j.properties PRE-CREATION 
>   pom.xml fa1d1c7b 
>   ranger-kafka-plugin-shim/pom.xml f1aeee6f 
> 
> 
> Diff: https://reviews.apache.org/r/65777/diff/2/
> 
> 
> Testing
> ---
> 
> Unit & local tests
> 
> 
> Thanks,
> 
> Zsombor Gegesy
> 
>

Re: Review Request 65793: RANGER-1991 : fix errors detected by static code analysis

[Colm O hEigeartaigh]

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



+   String key = (String) entry.getKey();
+   String value = (String) 
entry.getValue();
+   if (RANGER_SECTION_NAME.equals(value)) {
+   
rangerInternalPropertyKeys.add(key);
}

You could move the "key" part here into the if statement.

+   logger.error("Error creating user: 
"+vXUser.getName(),ex);

Add spaces around "=" and ","

- Colm O hEigeartaigh


On Feb. 24, 2018, 4:19 p.m., Zsombor Gegesy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65793/
> ---
> 
> (Updated Feb. 24, 2018, 4:19 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1991
> https://issues.apache.org/jira/browse/RANGER-1991
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> FindBugs/SpotBug detects a couple of problems with the code base:
> * Incorrect class casting - in XXServiceDef.equals
> * Unnecessary NPE checks - for variables which is known to be non-null (for 
> example, because in other places a method is called on that object). In 
> ServiceREST.java PublicAPIs.java, ServiceUtil.java and independently in 
> XUserMgr.java
> * Collection.contains method call which is never true - in 
> ServiceDBStore.validatePolicyItems for policyItem.getAccesses().contains("") 
> - because getAccesses doesn't store String objects
> * Making public partially initialized objects in 
> HadoopConfigHolder.initResourceMap()
> * Calling toString on array, which is not too readable
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/client/HadoopConfigHolder.java
>  fd925aa4 
>   
> hdfs-agent/src/test/java/org/apache/ranger/services/hdfs/RangerHdfsAuthorizerTest.java
>  46f92ecb 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
> 7aee4336 
>   security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java cecb3f8b 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 92b0e031 
>   security-admin/src/main/java/org/apache/ranger/common/ServiceUtil.java 
> e82d33d3 
>   security-admin/src/main/java/org/apache/ranger/entity/XXServiceDef.java 
> 3d496831 
>   security-admin/src/main/java/org/apache/ranger/rest/PublicAPIs.java 
> 7818eb59 
>   security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 
> 9e4d799b 
> 
> 
> Diff: https://reviews.apache.org/r/65793/diff/1/
> 
> 
> Testing
> ---
> 
> Tested locally
> 
> 
> Thanks,
> 
> Zsombor Gegesy
> 
>

[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-1967:
-

Hi [~zhangqiang2],

We (the Ranger team) discussed a similar issue for Hadoop (where upgrading to 
Hadoop 3.0.0 meant that support was dropped for 2.x). It was felt that we 
should not have multiple plugin versions but instead users who want support for 
an older plugin version can just get it from an older Ranger release. If users 
want support for Kafka 0.10.x they can just get the plugin from Ranger 0.7.1.

Colm.

> The Ranger support the Kafka 1.0.0
> --
>
> Key: RANGER-1967
> URL: https://issues.apache.org/jira/browse/RANGER-1967
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Zsombor Gegesy
>Priority: Major
>  Labels: newbie, patch
> Attachments: RANGER-1967-2.patch, RANGER-1967.patch
>
>
> Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka 
> 1.0.0.



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

Re: Prep for ranger-1.0.0 release

[Colm O hEigeartaigh]

+1. It would be nice to get the Kafka upgrade in if possible, as currently
we support a very old version of Kafka.

Colm.

On Fri, Feb 23, 2018 at 9:00 AM, Jianhua Peng <pengjian...@apache.org>
wrote:

> +1
>
> On 2018/02/23 01:34:36, Sailaja Polavarapu <spolavar...@hortonworks.com>
> 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.
> >
>



-- 
Colm O hEigeartaigh

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

[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on RANGER-1967:
-

[~zhangqiang2] any update on this?

> The Ranger support the Kafka 1.0.0
> --
>
> Key: RANGER-1967
> URL: https://issues.apache.org/jira/browse/RANGER-1967
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
>  Labels: newbie, patch
>
> Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka 
> 1.0.0.



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

Review Request 65709: RANGER-1987 - Upgrade to Storm 1.2.0

[Colm O hEigeartaigh]

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

Review request for ranger.


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


Repository: ranger


Description
---

We should upgrade to the recently release Apache Storm 1.2.0. No code changes 
are required.


Diffs
-

  pom.xml fa1d1c7b 


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


Testing
---

Tested Ranger with Storm 1.2.0.


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-1987) Upgrade to Storm 1.2.0

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated RANGER-1987:

Attachment: 0001-RANGER-1987-Upgrade-to-Storm-1.2.0.patch

> Upgrade to Storm 1.2.0
> --
>
> Key: RANGER-1987
> URL: https://issues.apache.org/jira/browse/RANGER-1987
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>    Reporter: Colm O hEigeartaigh
>    Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-RANGER-1987-Upgrade-to-Storm-1.2.0.patch
>
>
>  
> We should upgrade to the recently release Apache Storm 1.2.0. No code changes 
> are required.



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

[jira] [Created] (RANGER-1987) Upgrade to Storm 1.2.0

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created RANGER-1987:
---

 Summary: Upgrade to Storm 1.2.0
 Key: RANGER-1987
 URL: https://issues.apache.org/jira/browse/RANGER-1987
 Project: Ranger
  Issue Type: Improvement
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.0.0


 

We should upgrade to the recently release Apache Storm 1.2.0. No code changes 
are required.



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

Re: Review Request 65608: RANGER-1980: Build failure for Ranger 0.7 branch

[Colm O hEigeartaigh]

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On Feb. 12, 2018, 2:55 p.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65608/
> ---
> 
> (Updated Feb. 12, 2018, 2:55 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, deepak sharma, 
> Gautam Borad, Mehul Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1980
> https://issues.apache.org/jira/browse/RANGER-1980
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> **Problem Statement:** Ranger Build is failing on ranger-0.7 branch.
> 
> **Proposed Solution:** It seems 0.8.2-SNAPSHOT jars have been removed from 
> all the sub-modules of 
> https://repository.apache.org/content/repositories/snapshots/org/apache/atlas.
>  However 0.8.2 release jars are available here 
> https://repository.apache.org/content/repositories/releases/org/apache/atlas 
> and I am able to build ranger-0.7 using the 0.8.2 release jars.
> 
> 
> Diffs
> -
> 
>   pom.xml cc09475 
> 
> 
> Diff: https://reviews.apache.org/r/65608/diff/2/
> 
> 
> Testing
> ---
> 
> Steps performed for Ranger-admin(with patch):
> 1. Created Build with patch and untar the build.
> 2. Opened install.properties and provided db configuration in 
> install.properties
> 3. Called setup.sh
> 
> **Expected Behavior:**
> Ranger-admin installation should finish successfully.
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>