date:20180212

Re: Review Request 65567: RANGER-1972 : Ability to label policies, filter/search and show policies by labels

2018-02-12 Thread bhavik patel


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

(Updated Feb. 13, 2018, 6:57 a.m.)


Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
Sailaja Polavarapu, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

In Ranger Admin, need a feature to be able to group (for example by tenant name 
or business unit) sets of policies with one or more labels that are relevant to 
business. 
Furthermore, Need to able to search policies on this additional set of labels. 
This will be useful for export/import policies as well.


Diffs (updated)
-

  agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicy.java 
60daed9 
  
agents-common/src/main/java/org/apache/ranger/plugin/store/AbstractPredicateUtil.java
 7583864 
  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
fa4f767 
  security-admin/db/mysql/patches/030-policy-labels-schema.sql PRE-CREATION 
  security-admin/db/oracle/patches/030-policy-labels-schema.sql PRE-CREATION 
  security-admin/db/postgres/patches/030-policy-labels-schema.sql PRE-CREATION 
  security-admin/db/sqlanywhere/patches/030-policy-labels-schema.sql 
PRE-CREATION 
  security-admin/db/sqlserver/patches/030-policy-labels-schema.sql PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/biz/RangerPolicyRetriever.java 
1b6f440 
  security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
7aee433 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
92b0e03 
  security-admin/src/main/java/org/apache/ranger/db/RangerDaoManagerBase.java 
db20a14 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyLabelDao.java 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyLabelMapDao.java 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/entity/XXPolicyLabel.java 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/entity/XXPolicyLabelMap.java 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 9e4d799 
  
security-admin/src/main/java/org/apache/ranger/service/RangerPolicyLabelsService.java
 PRE-CREATION 
  
security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java 
5aec948 
  
security-admin/src/main/java/org/apache/ranger/service/RangerPolicyServiceBase.java
 5d3af2f 
  security-admin/src/main/java/org/apache/ranger/view/VXPolicy.java c73d42b 
  security-admin/src/main/java/org/apache/ranger/view/VXPolicyLabel.java 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/view/VXPolicyLabelList.java 
PRE-CREATION 
  security-admin/src/main/resources/META-INF/jpa_named_queries.xml 786b4bf 
  security-admin/src/main/webapp/scripts/models/RangerPolicy.js b5a274a 
  security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
b71427c 
  security-admin/src/main/webapp/scripts/utils/XAUtils.js 8fa7fca 
  security-admin/src/main/webapp/scripts/views/policies/RangerPolicyDetail.js 
5bf2296 
  security-admin/src/main/webapp/scripts/views/policies/RangerPolicyForm.js 
542147f 
  security-admin/src/main/webapp/scripts/views/policies/RangerPolicyRO.js 
a01350b 
  
security-admin/src/main/webapp/scripts/views/policies/RangerPolicyTableLayout.js
 ce295ff 
  
security-admin/src/main/webapp/scripts/views/reports/PlugableServiceDiffDetail.js
 914f271 
  security-admin/src/main/webapp/scripts/views/reports/UserAccessLayout.js 
90f44c1 
  security-admin/src/main/webapp/styles/xa.css ee13655 
  
security-admin/src/main/webapp/templates/policies/RangerPolicyDetail_tmpl.html 
f8d1791 
  security-admin/src/main/webapp/templates/policies/RangerPolicyRO_tmpl.html 
f298fd0 
  security-admin/src/main/webapp/templates/reports/UserAccessLayout_tmpl.html 
36a7a6e 
  security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java 
f7eb0d4 
  security-admin/src/test/java/org/apache/ranger/rest/TestServiceREST.java 
bb97fab 


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

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


Testing
---

1. While creating policy, multiple labels can be assigned also lookup is 
working.
2. On policy listing page admin is able to filter policies based on policy 
labels.
3. On report page also admin is able to filter policies based on policy labels.


Thanks,

bhavik patel

[jira] [Updated] (RANGER-1972) Ability to label policies, filter/search and show policies by labels

2018-02-12 Thread bhavik patel (JIRA)


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

bhavik patel updated RANGER-1972:
-
Attachment: RANGER-1972-master-02.patch

> Ability to label policies, filter/search and show policies by labels
> 
>
> Key: RANGER-1972
> URL: https://issues.apache.org/jira/browse/RANGER-1972
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: bhavik patel
>Assignee: bhavik patel
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1972-master-01.patch, 
> RANGER-1972-master-02.patch, RANGER-1972-master.patch
>
>
> In Ranger Admin, need a feature to be able to group (for example by tenant 
> name or business unit) sets of policies with one or more labels that are 
> relevant to business. 
> Furthermore, Need to able to search policies on this additional set of 
> labels. This will be useful for export/import policies as well.



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

Re: Review Request 65599: RANGER-1976: Upgrade Apache POI to 3.15

2018-02-12 Thread Qiang Zhang


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


Ship it!




Ship It!

- Qiang Zhang


On 二月 12, 2018, 8:58 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65599/
> ---
> 
> (Updated 二月 12, 2018, 8:58 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1976
> https://issues.apache.org/jira/browse/RANGER-1976
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Change Apache POI version from 3.12 to 3.15
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
> 
> 
> Diff: https://reviews.apache.org/r/65599/diff/1/
> 
> 
> 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 and File poi-3.17.jar 
> should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar
> 
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File poi-3.17.jar was 
> available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar
> 
> 
> User, Group, Service and Policy creation is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65604: RANGER-1977: Upgrade Apache commons-beanutils to 1.9.3

2018-02-12 Thread Qiang Zhang


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


Ship it!




Ship It!

- Qiang Zhang


On 二月 12, 2018, 11:31 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65604/
> ---
> 
> (Updated 二月 12, 2018, 11:31 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1977
> https://issues.apache.org/jira/browse/RANGER-1977
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Apache commons-beanutils to 1.9.3
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
>   security-admin/pom.xml 48fff2e 
>   src/main/assembly/kms.xml 120ee00 
> 
> 
> Diff: https://reviews.apache.org/r/65604/diff/1/
> 
> 
> 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 and File 
> commons-beanutils-1.9.3.jar should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar
> 
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File 
> commons-beanutils-1.9.3.jar was available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar
> 
> 
> User, Group, Service and Policy creation is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65605: RANGER-1979: Upgrade Spring-LDAP to 2.3.2

2018-02-12 Thread Qiang Zhang


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


Ship it!




Ship It!

- Qiang Zhang


On 二月 12, 2018, 12:13 p.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65605/
> ---
> 
> (Updated 二月 12, 2018, 12:13 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1979
> https://issues.apache.org/jira/browse/RANGER-1979
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Spring-LDAP to 2.3.2
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
> 
> 
> Diff: https://reviews.apache.org/r/65605/diff/1/
> 
> 
> 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 and File 
> spring-ldap-core-2.3.2.RELEASE.jar should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File 
> spring-ldap-core-2.3.2.RELEASE.jar was available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar
> 
> **Note:**
> User, Group, Service and Policy creation is working successfully.
> Ldap user sync and Ldap Authentication is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

[jira] [Commented] (RANGER-1978) Upgrade Jackson Databind to 2.8.11

2018-02-12 Thread peng.jianhua (JIRA)


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

peng.jianhua commented on RANGER-1978:
--

Please create a RR for this issue. Thanks!

> Upgrade Jackson Databind to 2.8.11
> --
>
> Key: RANGER-1978
> URL: https://issues.apache.org/jira/browse/RANGER-1978
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-RANGER-1978-Upgrade-Jackson-Databind-to-2.8.11.patch
>
>
> Upgrade Jackson Databind to 2.8.11



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

Re: Review Request 65599: RANGER-1976: Upgrade Apache POI to 3.15

2018-02-12 Thread pengjianhua


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


Ship it!




Ship It!

- pengjianhua


On 二月 12, 2018, 8:58 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65599/
> ---
> 
> (Updated 二月 12, 2018, 8:58 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1976
> https://issues.apache.org/jira/browse/RANGER-1976
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Change Apache POI version from 3.12 to 3.15
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
> 
> 
> Diff: https://reviews.apache.org/r/65599/diff/1/
> 
> 
> 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 and File poi-3.17.jar 
> should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar
> 
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File poi-3.17.jar was 
> available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar
> 
> 
> User, Group, Service and Policy creation is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65604: RANGER-1977: Upgrade Apache commons-beanutils to 1.9.3

2018-02-12 Thread pengjianhua


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


Ship it!




Ship It!

- pengjianhua


On 二月 12, 2018, 11:31 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65604/
> ---
> 
> (Updated 二月 12, 2018, 11:31 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1977
> https://issues.apache.org/jira/browse/RANGER-1977
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Apache commons-beanutils to 1.9.3
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
>   security-admin/pom.xml 48fff2e 
>   src/main/assembly/kms.xml 120ee00 
> 
> 
> Diff: https://reviews.apache.org/r/65604/diff/1/
> 
> 
> 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 and File 
> commons-beanutils-1.9.3.jar should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar
> 
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File 
> commons-beanutils-1.9.3.jar was available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar
> 
> 
> User, Group, Service and Policy creation is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65605: RANGER-1979: Upgrade Spring-LDAP to 2.3.2

2018-02-12 Thread pengjianhua


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


Ship it!




Ship It!

- pengjianhua


On 二月 12, 2018, 12:13 p.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65605/
> ---
> 
> (Updated 二月 12, 2018, 12:13 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1979
> https://issues.apache.org/jira/browse/RANGER-1979
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Spring-LDAP to 2.3.2
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
> 
> 
> Diff: https://reviews.apache.org/r/65605/diff/1/
> 
> 
> 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 and File 
> spring-ldap-core-2.3.2.RELEASE.jar should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File 
> spring-ldap-core-2.3.2.RELEASE.jar was available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar
> 
> **Note:**
> User, Group, Service and Policy creation is working successfully.
> Ldap user sync and Ldap Authentication is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65611: RANGER-1980: changed Atlas version from 1.0.0-SNAPSHOT to Atlas-0.8.2 (revert of RANGER-1897)

2018-02-12 Thread Abhay Kulkarni


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


Ship it!




Ship It!

- Abhay Kulkarni


On Feb. 12, 2018, 5:14 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65611/
> ---
> 
> (Updated Feb. 12, 2018, 5:14 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1980
> https://issues.apache.org/jira/browse/RANGER-1980
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-1897 committed in master earlier was to change Atlas version from 
> 0.8.1-SNAPSHOT to 1.0.0-SNAPSHOT. Now that master will be using Atlas 0.8.2, 
> this commit needs to be reverted.
> 
> 
> Diffs
> -
> 
>   
> plugin-atlas/src/main/java/org/apache/ranger/authorization/atlas/authorizer/RangerAtlasResource.java
>  4367c5e2 
>   pom.xml 69e042f8 
>   src/main/assembly/tagsync.xml c9293956 
>   tagsync/pom.xml 7e53641b 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/process/TagSynchronizer.java 
> 45997e40 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/sink/tagadmin/TagAdminRESTSink.java
>  a1dc8f5d 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasEntityWithTraits.java
>  PRE-CREATION 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHbaseResourceMapper.java
>  33e804a2 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHdfsResourceMapper.java
>  378542cd 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHiveResourceMapper.java
>  3e0a97f4 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasKafkaResourceMapper.java
>  86e37c33 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java
>  91cf606a 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasResourceMapper.java
>  5d067a5b 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasResourceMapperUtil.java
>  cd2cb630 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasStormResourceMapper.java
>  650968d7 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java
>  8c15ee58 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/AtlasRESTTagSource.java
>  b7158693 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/AtlasRESTUtil.java
>  PRE-CREATION 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntity.java
>  991dccac 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java
>  b25a2412 
>   
> tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHbaseResourceMapper.java
>  499247c4 
>   
> tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHdfsResourceMapper.java
>  62769040 
>   
> tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHiveResourceMapper.java
>  22a0bb48 
>   
> tagsync/src/test/java/org/apache/ranger/tagsync/process/TestKafkaResourceMapper.java
>  ce359448 
> 
> 
> Diff: https://reviews.apache.org/r/65611/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Ranger website checks

2018-02-12 Thread Selvamohan Neethiraj

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

Selva-

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

signature.asc
Description: Message signed with OpenPGP

[jira] [Commented] (RANGER-1975) Address Ranger Website checks flagged by Whimsy

2018-02-12 Thread Selvamohan Neethiraj (JIRA)


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

Selvamohan Neethiraj commented on RANGER-1975:
--

Also, I had to change all license links to [https://www.apache.org/licenses/].

And I had to add our logo jpg file, ranger.jpg to the folder: 
[https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/img/] using 
SVN to clear the error related to image.

 

 

> Address Ranger Website checks flagged by Whimsy
> ---
>
> Key: RANGER-1975
> URL: https://issues.apache.org/jira/browse/RANGER-1975
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Velmurugan Periasamy
>Assignee: Selvamohan Neethiraj
>Priority: Major
>  Labels: documentation, site
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-1975-fixes-to-add-apache-links-for-fixing-Whi.patch
>
>
> The ranger.apache.org website is failing a lot of the automated checks that 
> Apache runs.
> [https://whimsy.apache.org/site/project/ranger]
> In particular, Ranger should absolutely get the security check resolved.
> Reported by [~owen.omalley]



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

[jira] [Updated] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1980:

Attachment: 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch, 
> 0001-RANGER-1980-changed-Atlas-version-from-1.0.0-SNAPSHO.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Updated] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1980:

Attachment: (was: 
0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch)

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-changed-Atlas-version-from-1.0.0-SNAPSHO.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal commented on RANGER-1980:
-

Patch committed in ranger-0.7 branch:  
https://github.com/apache/ranger/commit/0c948119dbb109e65c8a811a49f537f478d6eda7

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch, 
> 0001-RANGER-1980-changed-Atlas-version-from-1.0.0-SNAPSHO.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

Review Request 65611: RANGER-1980: changed Atlas version from 1.0.0-SNAPSHOT to Atlas-0.8.2 (revert of RANGER-1897)

2018-02-12 Thread Madhan Neethiraj


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

Review request for ranger, Abhay Kulkarni and Velmurugan Periasamy.


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


Repository: ranger


Description
---

RANGER-1897 committed in master earlier was to change Atlas version from 
0.8.1-SNAPSHOT to 1.0.0-SNAPSHOT. Now that master will be using Atlas 0.8.2, 
this commit needs to be reverted.


Diffs
-

  
plugin-atlas/src/main/java/org/apache/ranger/authorization/atlas/authorizer/RangerAtlasResource.java
 4367c5e2 
  pom.xml 69e042f8 
  src/main/assembly/tagsync.xml c9293956 
  tagsync/pom.xml 7e53641b 
  tagsync/src/main/java/org/apache/ranger/tagsync/process/TagSynchronizer.java 
45997e40 
  
tagsync/src/main/java/org/apache/ranger/tagsync/sink/tagadmin/TagAdminRESTSink.java
 a1dc8f5d 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasEntityWithTraits.java
 PRE-CREATION 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHbaseResourceMapper.java
 33e804a2 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHdfsResourceMapper.java
 378542cd 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHiveResourceMapper.java
 3e0a97f4 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasKafkaResourceMapper.java
 86e37c33 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java
 91cf606a 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasResourceMapper.java
 5d067a5b 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasResourceMapperUtil.java
 cd2cb630 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasStormResourceMapper.java
 650968d7 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java
 8c15ee58 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/AtlasRESTTagSource.java
 b7158693 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/AtlasRESTUtil.java
 PRE-CREATION 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntity.java
 991dccac 
  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java
 b25a2412 
  
tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHbaseResourceMapper.java
 499247c4 
  
tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHdfsResourceMapper.java
 62769040 
  
tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHiveResourceMapper.java
 22a0bb48 
  
tagsync/src/test/java/org/apache/ranger/tagsync/process/TestKafkaResourceMapper.java
 ce359448 


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


Testing
---


Thanks,

Madhan Neethiraj

Re: Review Request 65567: RANGER-1972 : Ability to label policies, filter/search and show policies by labels

2018-02-12 Thread Velmurugan Periasamy


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




security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java
Lines 1293 (patched)


Please address unit test failures. I see below error with this patch. 

```

---
Test set: org.apache.ranger.biz.TestServiceDBStore

---
Tests run: 31, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.83 sec 
<<< FAILURE! - in org.apache.ranger.biz.TestServiceDBStore
unnecessary Mockito stubbings(org.apache.ranger.biz.TestServiceDBStore)  
Time elapsed: 0.034 sec  <<< ERROR!
org.mockito.exceptions.misusing.UnnecessaryStubbingException: 
Unnecessary stubbings detected in test class: TestServiceDBStore
Clean & maintainable test code requires zero unnecessary code.
Following stubbings are unnecessary (click to navigate to relevant line of 
code):
  1. -> at 
org.apache.ranger.biz.TestServiceDBStore.test21deleteService(TestServiceDBStore.java:1375)
Please remove unnecessary stubbings or use 'silent' option. More info: 
javadoc for UnnecessaryStubbingException class.
at org.mockito.internal.runners.StrictRunner.run(StrictRunner.java:49)
at org.mockito.junit.MockitoJUnitRunner.run(MockitoJUnitRunner.java:161)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

```


- Velmurugan Periasamy


On Feb. 12, 2018, 6:13 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65567/
> ---
> 
> (Updated Feb. 12, 2018, 6:13 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1972
> https://issues.apache.org/jira/browse/RANGER-1972
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> In Ranger Admin, need a feature to be able to group (for example by tenant 
> name or business unit) sets of policies with one or more labels that are 
> relevant to business. 
> Furthermore, Need to able to search policies on this additional set of 
> labels. This will be useful for export/import policies as well.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicy.java 
> 60daed9 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/AbstractPredicateUtil.java
>  7583864 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> fa4f767 
>   security-admin/db/mysql/patches/030-policy-labels-schema.sql PRE-CREATION 
>   security-admin/db/oracle/patches/030-policy-labels-schema.sql PRE-CREATION 
>   security-admin/db/postgres/patches/030-policy-labels-schema.sql 
> PRE-CREATION 
>   security-admin/db/sqlanywhere/patches/030-policy-labels-schema.sql 
> PRE-CREATION 
>   security-admin/db/sqlserver/patches/030-policy-labels-schema.sql 
> PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/biz/RangerPolicyRetriever.java 
> 1b6f440 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
> 7aee433 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 92b0e03 
>   security-admin/src/main/java/org/apache/ranger/db/RangerDaoManagerBase.java 
> db20a14 
>   security-admin/src/main/java/org/apache/ranger/db/XXPolicyLabelDao.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/db/XXPolicyLabelMapDao.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/entity/XXPolicyLabel.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/entity/XXPolicyLabelMap.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 
> 9e4d799 
>   
>

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

2018-02-12 Thread 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
> 
>

Re: Review Request 65605: RANGER-1979: Upgrade Spring-LDAP to 2.3.2

2018-02-12 Thread Velmurugan Periasamy


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


Ship it!




Ship It!

- Velmurugan Periasamy


On Feb. 12, 2018, 12:13 p.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65605/
> ---
> 
> (Updated Feb. 12, 2018, 12:13 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1979
> https://issues.apache.org/jira/browse/RANGER-1979
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Spring-LDAP to 2.3.2
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
> 
> 
> Diff: https://reviews.apache.org/r/65605/diff/1/
> 
> 
> 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 and File 
> spring-ldap-core-2.3.2.RELEASE.jar should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File 
> spring-ldap-core-2.3.2.RELEASE.jar was available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar
> 
> **Note:**
> User, Group, Service and Policy creation is working successfully.
> Ldap user sync and Ldap Authentication is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65604: RANGER-1977: Upgrade Apache commons-beanutils to 1.9.3

2018-02-12 Thread Velmurugan Periasamy


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


Ship it!




Ship It!

- Velmurugan Periasamy


On Feb. 12, 2018, 11:31 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65604/
> ---
> 
> (Updated Feb. 12, 2018, 11:31 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1977
> https://issues.apache.org/jira/browse/RANGER-1977
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Upgrade Apache commons-beanutils to 1.9.3
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
>   security-admin/pom.xml 48fff2e 
>   src/main/assembly/kms.xml 120ee00 
> 
> 
> Diff: https://reviews.apache.org/r/65604/diff/1/
> 
> 
> 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 and File 
> commons-beanutils-1.9.3.jar should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar
> 
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File 
> commons-beanutils-1.9.3.jar was available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar
> 
> 
> User, Group, Service and Policy creation is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Re: Review Request 65599: RANGER-1976: Upgrade Apache POI to 3.15

2018-02-12 Thread Velmurugan Periasamy


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


Ship it!




Ship It!

- Velmurugan Periasamy


On Feb. 12, 2018, 8:58 a.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65599/
> ---
> 
> (Updated Feb. 12, 2018, 8:58 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
> Parikh, suja s, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1976
> https://issues.apache.org/jira/browse/RANGER-1976
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Change Apache POI version from 3.12 to 3.15
> 
> 
> Diffs
> -
> 
>   pom.xml 69e042f 
> 
> 
> Diff: https://reviews.apache.org/r/65599/diff/1/
> 
> 
> 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 and File poi-3.17.jar 
> should be available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar
> 
> 
> **Actual Behavior:**
> Ranger-admin Installation finished successfully and File poi-3.17.jar was 
> available in location: 
> ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar
> 
> 
> User, Group, Service and Policy creation is working successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj commented on RANGER-1980:
--

bq. Master is not compiling with 0.8.2. I am getting below error. 
[~vperiasamy] - updates in RANGER-1897 work only with Atlas 1.0.0. To build 
master with Atlas 0.8.2, this commit needs to be reverted. I am working on that 
and will upload the patch shortly.

bq. Any reason we can't just upgrade both master + 0.7.x with Atlas 0.8.2?
I agree on building both master & 0.7.x with Atlas 0.8.2.

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

Re: Review Request 65525: Show actual hive query on ranger audit UI

2018-02-12 Thread Nikhil P


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

(Updated Feb. 12, 2018, 8:49 p.m.)


Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
Sailaja Polavarapu, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

Hive Access audits in ranger(Access Audit Tab) should show the actual query 
associated with the hive access event for a particular column or table or 
database.


Diffs (updated)
-

  
security-admin/src/main/java/org/apache/ranger/service/XAccessAuditService.java 
5d03fb2 
  
security-admin/src/main/java/org/apache/ranger/solr/SolrAccessAuditsService.java
 a3c693e 
  security-admin/src/main/resources/conf.dist/ranger-admin-site.xml 939d7e6 
  security-admin/src/main/webapp/scripts/utils/XAUtils.js 8fa7fca 
  security-admin/src/main/webapp/scripts/utils/XAViewUtils.js 08e1881 
  security-admin/src/main/webapp/scripts/views/reports/AuditLayout.js 0e864b6 
  security-admin/src/main/webapp/styles/xa.css ee13655 
  security-admin/src/main/webapp/templates/reports/AuditLayout_tmpl.html 
bee65db 


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

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


Testing
---

1.Verified various hive queries gets displayed on UI.
2.checked grant/revoke queries gets reflected correctly on UI.
3.verified if configurable hive query visibility property works properly.


Thanks,

Nikhil P

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

2018-02-12 Thread Velmurugan Periasamy


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


Ship it!




Ship It!

- Velmurugan Periasamy


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
> 
>

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

2018-02-12 Thread Pradeep Agrawal


---
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.


Changes
---

changed to 0.8.2 released version.


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


Repository: ranger


Description (updated)
---

**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 (updated)
-

  pom.xml cc09475 


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

Changes: https://reviews.apache.org/r/65608/diff/1-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

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

2018-02-12 Thread Pradeep Agrawal



> On Feb. 12, 2018, 2:27 p.m., Colm O hEigeartaigh wrote:
> > Why not just update to the released 0.8.2? We should avoid depending on 
> > SNAPSHOT versions of other projects unless there is a good reason to do so.
> 
> Pradeep Agrawal wrote:
> Currently 0.8.2-SNAPSHOT jars are not available here 
> https://repository.apache.org/content/repositories/snapshots/org/apache/atlas
> 
> Velmurugan Periasamy wrote:
> Using 0.8.2 for ranger-0.7 branch makse sense.

Sorry, yes 0.8.2 release is available here 
https://repository.apache.org/content/repositories/releases/org/apache/atlas so 
i will try and provide the updated patch.


- Pradeep


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


On Feb. 12, 2018, 2:09 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:09 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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
> using the 0.8.3-SNAPSHOT jar.
> 
> 
> Diffs
> -
> 
>   pom.xml cc09475 
> 
> 
> Diff: https://reviews.apache.org/r/65608/diff/1/
> 
> 
> 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
> 
>

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

2018-02-12 Thread Velmurugan Periasamy



> On Feb. 12, 2018, 2:27 p.m., Colm O hEigeartaigh wrote:
> > Why not just update to the released 0.8.2? We should avoid depending on 
> > SNAPSHOT versions of other projects unless there is a good reason to do so.
> 
> Pradeep Agrawal wrote:
> Currently 0.8.2-SNAPSHOT jars are not available here 
> https://repository.apache.org/content/repositories/snapshots/org/apache/atlas

Using 0.8.2 for ranger-0.7 branch makse sense.


- Velmurugan


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


On Feb. 12, 2018, 2:09 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:09 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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
> using the 0.8.3-SNAPSHOT jar.
> 
> 
> Diffs
> -
> 
>   pom.xml cc09475 
> 
> 
> Diff: https://reviews.apache.org/r/65608/diff/1/
> 
> 
> 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
> 
>

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

2018-02-12 Thread Pradeep Agrawal



> On Feb. 12, 2018, 2:27 p.m., Colm O hEigeartaigh wrote:
> > Why not just update to the released 0.8.2? We should avoid depending on 
> > SNAPSHOT versions of other projects unless there is a good reason to do so.

Currently 0.8.2-SNAPSHOT jars are not available here 
https://repository.apache.org/content/repositories/snapshots/org/apache/atlas


- Pradeep


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


On Feb. 12, 2018, 2:09 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:09 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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
> using the 0.8.3-SNAPSHOT jar.
> 
> 
> Diffs
> -
> 
>   pom.xml cc09475 
> 
> 
> Diff: https://reviews.apache.org/r/65608/diff/1/
> 
> 
> 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
> 
>

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

2018-02-12 Thread Colm O hEigeartaigh


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



Why not just update to the released 0.8.2? We should avoid depending on 
SNAPSHOT versions of other projects unless there is a good reason to do so.

- Colm O hEigeartaigh


On Feb. 12, 2018, 2:09 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:09 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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
> using the 0.8.3-SNAPSHOT jar.
> 
> 
> Diffs
> -
> 
>   pom.xml cc09475 
> 
> 
> Diff: https://reviews.apache.org/r/65608/diff/1/
> 
> 
> 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
> 
>

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

2018-02-12 Thread Velmurugan Periasamy


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


Ship it!




Ship It!

- Velmurugan Periasamy


On Feb. 12, 2018, 2:09 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:09 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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
> using the 0.8.3-SNAPSHOT jar.
> 
> 
> Diffs
> -
> 
>   pom.xml cc09475 
> 
> 
> Diff: https://reviews.apache.org/r/65608/diff/1/
> 
> 
> 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
> 
>

[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Velmurugan Periasamy (JIRA)


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

Velmurugan Periasamy commented on RANGER-1980:
--

Master is not compiling with 0.8.2. I am getting below error. CC [~abhayk] / 
[~madhan.neethiraj]
{quote}[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on 
project ranger-tagsync: Compilation failure: Compilation failure:

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[24,45]
 error: package org.apache.atlas.v1.model.notification does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[25,41]
 error: package org.apache.atlas.v1.model.instance does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[26,41]
 error: package org.apache.atlas.v1.model.instance does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[38,37]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class RangerAtlasEntityWithTags

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java:[26,45]
 error: package org.apache.atlas.v1.model.notification does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java:[141,54]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class AtlasTagSource

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java:[154,37]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class AtlasTagSource.ConsumerRunnable

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java:[156,48]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class AtlasTagSource.ConsumerRunnable

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java:[22,45]
 error: package org.apache.atlas.v1.model.notification does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java:[23,41]
 error: package org.apache.atlas.v1.model.instance does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java:[24,41]
 error: package org.apache.atlas.v1.model.instance does not exist

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java:[49,52]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class AtlasNotificationMapper

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java:[79,53]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class AtlasNotificationMapper

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java:[114,46]
 error: cannot find symbol

[ERROR]   symbol:   class EntityNotificationV1

[ERROR]   location: class AtlasNotificationMapper

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[39,8]
 error: cannot find symbol

[ERROR]   symbol:   class Referenceable

[ERROR]   location: class RangerAtlasEntityWithTags

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[48,13]
 error: cannot find symbol

[ERROR]   symbol:   class Struct

[ERROR]   location: class RangerAtlasEntityWithTags

[ERROR] 
/Users/vperiasamy/git/tlp-ranger/master/ranger/tagsync/src/main/java/org/apache/ranger/tagsync/source/atlasrest/RangerAtlasEntityWithTags.java:[49,13]
 error: cannot find symbol

[ERROR]   symbol:   class Struct

[ERROR]   location: class RangerAtlasEntityWithTags

[ERROR]

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

2018-02-12 Thread Pradeep Agrawal


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

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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
using the 0.8.3-SNAPSHOT jar.


Diffs
-

  pom.xml cc09475 


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


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

[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Velmurugan Periasamy (JIRA)


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

Velmurugan Periasamy commented on RANGER-1980:
--

Atlas had completed 0.8.2 release. That's probably why snapshot jars are not 
there. 

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Colm O hEigeartaigh (JIRA)


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

Colm O hEigeartaigh commented on RANGER-1980:
-

Any reason we can't just upgrade both master + 0.7.x with Atlas 0.8.2?

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Updated] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1980:

Affects Version/s: 0.7.2

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Affects Versions: 0.7.2
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Comment Edited] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal edited comment on RANGER-1980 at 2/12/18 2:00 PM:
--

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.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
using the 0.8.3-SNAPSHOT jar.


was (Author: pradeep.agrawal):
It seems 0.8.2-SNAPSHOT jars have been removed from all the submodule of 
[https://repository.apache.org/content/repositories/snapshots/org/apache/atlas.]
 However 0.8.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
using the 0.8.3-SNAPSHOT jar.

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Updated] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1980:

Fix Version/s: 0.7.2

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal commented on RANGER-1980:
-

It seems 0.8.2-SNAPSHOT jars have been removed from all the submodule of 
[https://repository.apache.org/content/repositories/snapshots/org/apache/atlas.]
 However 0.8.3-SNAPSHOT jars are available and I am able to build ranger-0.7 
using the 0.8.3-SNAPSHOT jar.

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 0.7.2
>
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Updated] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1980:

Attachment: 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments: 
> 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Assigned] (RANGER-1980) Build failure for Ranger 0.7 branch

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal reassigned RANGER-1980:
---

Assignee: Pradeep Agrawal

> Build failure for Ranger 0.7 branch
> ---
>
> Key: RANGER-1980
> URL: https://issues.apache.org/jira/browse/RANGER-1980
> Project: Ranger
>  Issue Type: Bug
>  Components: build-infra
>Reporter: Don Bosco Durai
>Assignee: Pradeep Agrawal
>Priority: Major
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Ranger 0.7 compilation is failing with the following error.
>  
>  
> [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve 
> dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: 
> The following artifacts could not be resolved: 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, 
> org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact 
> org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in 
> apache.snapshots.https 
> ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1]
>  
>  
>  
>  
> Seems, Atlas snapshot jars are not found



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

[jira] [Updated] (RANGER-1978) Upgrade Jackson Databind to 2.8.11

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1978:

Attachment: 0001-RANGER-1978-Upgrade-Jackson-Databind-to-2.8.11.patch

> Upgrade Jackson Databind to 2.8.11
> --
>
> Key: RANGER-1978
> URL: https://issues.apache.org/jira/browse/RANGER-1978
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-RANGER-1978-Upgrade-Jackson-Databind-to-2.8.11.patch
>
>
> Upgrade Jackson Databind to 2.8.11



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

[jira] [Updated] (RANGER-1979) Upgrade Spring-LDAP to 2.3.2

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1979:

Attachment: RANGER-1979-1.patch

> Upgrade Spring-LDAP to 2.3.2
> 
>
> Key: RANGER-1979
> URL: https://issues.apache.org/jira/browse/RANGER-1979
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1979-1.patch
>
>
> Upgrade Spring-LDAP to 2.3.2+



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

Review Request 65605: RANGER-1979: Upgrade Spring-LDAP to 2.3.2

2018-02-12 Thread Pradeep Agrawal


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

Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
Parikh, suja s, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

Upgrade Spring-LDAP to 2.3.2


Diffs
-

  pom.xml 69e042f 


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


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 and File 
spring-ldap-core-2.3.2.RELEASE.jar should be available in location: 
ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar

**Actual Behavior:**
Ranger-admin Installation finished successfully and File 
spring-ldap-core-2.3.2.RELEASE.jar was available in location: 
ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/spring-ldap-core-2.3.2.RELEASE.jar

**Note:**
User, Group, Service and Policy creation is working successfully.
Ldap user sync and Ldap Authentication is working successfully.


Thanks,

Pradeep Agrawal

[jira] [Updated] (RANGER-1977) Upgrade Apache commons-beanutils to 1.9.3

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1977:

Attachment: RANGER-1977-1.patch

> Upgrade Apache commons-beanutils to 1.9.3
> -
>
> Key: RANGER-1977
> URL: https://issues.apache.org/jira/browse/RANGER-1977
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1977-1.patch
>
>
> Upgrade Apache commons-beanutils to 1.9.3



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

Review Request 65604: RANGER-1977: Upgrade Apache commons-beanutils to 1.9.3

2018-02-12 Thread Pradeep Agrawal


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

Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
Parikh, suja s, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

Upgrade Apache commons-beanutils to 1.9.3


Diffs
-

  pom.xml 69e042f 
  security-admin/pom.xml 48fff2e 
  src/main/assembly/kms.xml 120ee00 


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


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 and File 
commons-beanutils-1.9.3.jar should be available in location: 
ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar


**Actual Behavior:**
Ranger-admin Installation finished successfully and File 
commons-beanutils-1.9.3.jar was available in location: 
ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/commons-beanutils-1.9.3.jar


User, Group, Service and Policy creation is working successfully.


Thanks,

Pradeep Agrawal

[jira] [Updated] (RANGER-1976) Upgrade Apache POI to 3.15

2018-02-12 Thread Pradeep Agrawal (JIRA)


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

Pradeep Agrawal updated RANGER-1976:

Attachment: RANGER-1976-1.patch

> Upgrade Apache POI to 3.15
> --
>
> Key: RANGER-1976
> URL: https://issues.apache.org/jira/browse/RANGER-1976
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1976-1.patch
>
>
> Upgrade Apache POI to 3.15 or latest version.



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

Review Request 65599: RANGER-1976: Upgrade Apache POI to 3.15

2018-02-12 Thread Pradeep Agrawal


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

Review request for ranger, Ankita Sinha, deepak sharma, Gautam Borad, Mehul 
Parikh, suja s, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

Change Apache POI version from 3.12 to 3.15


Diffs
-

  pom.xml 69e042f 


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


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 and File poi-3.17.jar 
should be available in location: 
ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar


**Actual Behavior:**
Ranger-admin Installation finished successfully and File poi-3.17.jar was 
available in location: 
ranger-1.0.0-SNAPSHOT-admin/ews/webapp/WEB-INF/lib/poi-3.17.jar


User, Group, Service and Policy creation is working successfully.


Thanks,

Pradeep Agrawal

47 matches

Mail list logo