[jira] [Commented] (RANGER-2243) Provide option to ranger builds to specifically build a single plugin
[ https://issues.apache.org/jira/browse/RANGER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661745#comment-16661745 ] Pradeep Agrawal commented on RANGER-2243: - Below command shall work to build ranger-admin mvn clean compile package assembly:assembly install -Pall > Provide option to ranger builds to specifically build a single plugin > - > > Key: RANGER-2243 > URL: https://issues.apache.org/jira/browse/RANGER-2243 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sailaja Polavarapu >Assignee: Sailaja Polavarapu >Priority: Major > Fix For: 2.0.0, 1.2.1 > > Attachments: > 0001-RANGER-2243-Created-separate-maven-profiles-for-each.patch > > > Make changes to ranger pom file to provide option for building individual > plugins. This way if anyone wants to deploy only ranger's hbase plugin, for > example, they can use the corresponding build option and generate only > ranger's hbase plugin tar instead of generating all the tar files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Ranger mvn build parameters...
Seems after https://issues.apache.org/jira/browse/RANGER-2243 patch, we need to pass -Pall to the build. Without that, I am getting this error: mvn -DskipTests=true clean compile package install assembly:assembly [ERROR] Could not find goal 'assembly' in plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals help, single -> [Help 1] Can we change the public documentation with additional details? Seems we need to change quite a few places: https://ranger.apache.org/quick_start_guide.html https://cwiki.apache.org/confluence/display/RANGER/Ranger+Installation+Guide https://github.com/apache/ranger There are other places also. Thanks Bosco
Review Request 69134: RANGER-2264:Kafka default policies for new resources are not showing up in UI when upgrade is done from older version
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69134/ --- Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, and Velmurugan Periasamy. Bugs: RANGER-2264 https://issues.apache.org/jira/browse/RANGER-2264 Repository: ranger Description --- RANGER-2264:Kafka default policies for new resources are not showing up in UI when upgrade is done from older version Diffs - security-admin/src/main/java/org/apache/ranger/patch/PatchForKafkaServiceDefUpdate_J10025.java 0ef1544 Diff: https://reviews.apache.org/r/69134/diff/1/ Testing --- Tested in Local VM for upgrade scenario Thanks, Ramesh Mani
[jira] [Updated] (RANGER-2264) Kafka default policies for new resources are not showing up in UI when upgrade is done from older version
[ https://issues.apache.org/jira/browse/RANGER-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated RANGER-2264: Attachment: 0001-RANGER-2264-Kafka-default-policies-for-new-resources.patch > Kafka default policies for new resources are not showing up in UI when > upgrade is done from older version > - > > Key: RANGER-2264 > URL: https://issues.apache.org/jira/browse/RANGER-2264 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master, 2.0.0 >Reporter: Ramesh Mani >Priority: Critical > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2264-Kafka-default-policies-for-new-resources.patch > > > Kafka default policies for new resources are not showing up in UI when the > upgrade is done from the older version. > This is due to the changes in the range DB schema and corresponding patch > file to upgrade has to be modified to set the PolicyText in the Policy table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2264) Kafka default policies for new resources are not showing up in UI when upgrade is done from older version
Ramesh Mani created RANGER-2264: --- Summary: Kafka default policies for new resources are not showing up in UI when upgrade is done from older version Key: RANGER-2264 URL: https://issues.apache.org/jira/browse/RANGER-2264 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master, 2.0.0 Reporter: Ramesh Mani Fix For: 2.0.0 Kafka default policies for new resources are not showing up in UI when the upgrade is done from the older version. This is due to the changes in the range DB schema and corresponding patch file to upgrade has to be modified to set the PolicyText in the Policy table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69126: RANGER-2263: Removed unnecessary explicit dependency for apache commons compress jar in Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69126/#review209933 --- Ship it! Ship It! - Velmurugan Periasamy On Oct. 23, 2018, 5:09 p.m., Sailaja Polavarapu wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69126/ > --- > > (Updated Oct. 23, 2018, 5:09 p.m.) > > > Review request for ranger. > > > Bugs: RANGER-2263 > https://issues.apache.org/jira/browse/RANGER-2263 > > > Repository: ranger > > > Description > --- > > Removed apache commons compress jar during compile time and packaging of > security admin module as there is no direct usage of this. Also changed > tagsync packaging to inlcude apache commons compress version from hadoop > commons instead of spcifying explicity version in ranger. > > > Diffs > - > > pom.xml 9e990a8ec > security-admin/pom.xml 7f81e6873 > src/main/assembly/tagsync.xml d1b83df42 > > > Diff: https://reviews.apache.org/r/69126/diff/1/ > > > Testing > --- > > Ran all unit tests succssfully. > Confirmed the packaging of security admin to not include commons compress jar > Congirmed the tagsync tar file contains proper version of commons compress jar > Patched cluster by removing commons compress jar from security admin module > and performed basic ranger UI fucntionality > > > Thanks, > > Sailaja Polavarapu > >
Re: Review Request 69126: RANGER-2263: Removed unnecessary explicit dependency for apache commons compress jar in Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69126/ --- (Updated Oct. 23, 2018, 5:09 p.m.) Review request for ranger. Bugs: RANGER-2263 https://issues.apache.org/jira/browse/RANGER-2263 Repository: ranger Description --- Removed apache commons compress jar during compile time and packaging of security admin module as there is no direct usage of this. Also changed tagsync packaging to inlcude apache commons compress version from hadoop commons instead of spcifying explicity version in ranger. Diffs - pom.xml 9e990a8ec security-admin/pom.xml 7f81e6873 src/main/assembly/tagsync.xml d1b83df42 Diff: https://reviews.apache.org/r/69126/diff/1/ Testing (updated) --- Ran all unit tests succssfully. Confirmed the packaging of security admin to not include commons compress jar Congirmed the tagsync tar file contains proper version of commons compress jar Patched cluster by removing commons compress jar from security admin module and performed basic ranger UI fucntionality Thanks, Sailaja Polavarapu
Review Request 69126: RANGER-2263: Removed unnecessary explicit dependency for apache commons compress jar in Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69126/ --- Review request for ranger. Bugs: RANGER-2263 https://issues.apache.org/jira/browse/RANGER-2263 Repository: ranger Description --- Removed apache commons compress jar during compile time and packaging of security admin module as there is no direct usage of this. Also changed tagsync packaging to inlcude apache commons compress version from hadoop commons instead of spcifying explicity version in ranger. Diffs - pom.xml 9e990a8ec security-admin/pom.xml 7f81e6873 src/main/assembly/tagsync.xml d1b83df42 Diff: https://reviews.apache.org/r/69126/diff/1/ Testing --- Ran all unit tests succssfully. Patched cluster by removing commons compress jar from security admin module and performed basic ranger UI fucntionality Thanks, Sailaja Polavarapu
[jira] [Commented] (RANGER-2262) Improvement of export to excel from report listing page for Oracle database.
[ https://issues.apache.org/jira/browse/RANGER-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660720#comment-16660720 ] Pradeep Agrawal commented on RANGER-2262: - Patch committed in master branch: [https://github.com/apache/ranger/commit/fe4db5764c1140dd663a3a41ef6b13516645ad5e] Patch committed in ranger-1.2 branch : c5959f34ac4921f79f895e33f1d0189271085bde Patch committed in ranger-1.1 branch : 001c5102855ca1d4c87c51d98e5649bc4a5aa372 Patch committed in ranger-1 branch : 7077c4099fd5115d1e5efcfc524612cbe761086e Patch committed in ranger-0.7 branch : 37b1e1c236e6501b31fee89a0ca98377f3dd72fb > Improvement of export to excel from report listing page for Oracle database. > > > Key: RANGER-2262 > URL: https://issues.apache.org/jira/browse/RANGER-2262 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Harshal Chavan >Assignee: Nikhil Purbhe >Priority: Major > Fix For: master, 0.7.2, 1.0.1, 2.0.0, 1.1.1, 1.2.1 > > Attachments: RANGER-2262-0.7.patch, RANGER-2262.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69117: Improvement of export to excel from report listing page for Oracle database
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69117/#review209919 --- Ship it! Ship It! - Pradeep Agrawal On Oct. 22, 2018, 12:51 p.m., Nikhil P wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69117/ > --- > > (Updated Oct. 22, 2018, 12:51 p.m.) > > > Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, > Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja > Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-2262 > https://issues.apache.org/jira/browse/RANGER-2262 > > > Repository: ranger > > > Description > --- > > Improvement of export to excel from report listing page for Oracle database > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java > 5dfe446 > > > Diff: https://reviews.apache.org/r/69117/diff/1/ > > > Testing > --- > > 1.Tested on VM. > > > Thanks, > > Nikhil P > >
[jira] [Commented] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660662#comment-16660662 ] Vishal Suvagia commented on RANGER-2251: Committed in ranger-0.7 branch: https://github.com/apache/ranger/commit/61b69730225687508123dae489b542bc86bfbd60 > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch, RANGER-2251-ranger-0.7.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2262) Improvement of export to excel from report listing page for Oracle database.
[ https://issues.apache.org/jira/browse/RANGER-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Purbhe updated RANGER-2262: -- Attachment: RANGER-2262-0.7.patch > Improvement of export to excel from report listing page for Oracle database. > > > Key: RANGER-2262 > URL: https://issues.apache.org/jira/browse/RANGER-2262 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Harshal Chavan >Assignee: Nikhil Purbhe >Priority: Major > Fix For: master, 0.7.2, 1.0.1, 2.0.0, 1.1.1, 1.2.1 > > Attachments: RANGER-2262-0.7.patch, RANGER-2262.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2262) Improvement of export to excel from report listing page for Oracle database.
[ https://issues.apache.org/jira/browse/RANGER-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Purbhe updated RANGER-2262: -- Fix Version/s: 1.2.1 1.1.1 1.0.1 0.7.2 master > Improvement of export to excel from report listing page for Oracle database. > > > Key: RANGER-2262 > URL: https://issues.apache.org/jira/browse/RANGER-2262 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Harshal Chavan >Assignee: Nikhil Purbhe >Priority: Major > Fix For: master, 0.7.2, 1.0.1, 2.0.0, 1.1.1, 1.2.1 > > Attachments: RANGER-2262.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69081: RANGER-2258 Improve the policy list page to prompt users when the service is disabled
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69081/#review209918 --- Ship it! Ship It! - Nitin Galave On Oct. 19, 2018, 8:06 a.m., Qiang Zhang wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69081/ > --- > > (Updated Oct. 19, 2018, 8:06 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-2258 > https://issues.apache.org/jira/browse/RANGER-2258 > > > Repository: ranger > > > Description > --- > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. > > Modified screenshots: > > https://issues.apache.org/jira/secure/attachment/12944673/Modify.PNG > > > Diffs > - > > > security-admin/src/main/webapp/scripts/views/policies/RangerPolicyTableLayout.js > 115083881 > > security-admin/src/main/webapp/templates/policies/RangerPolicyTableLayout_tmpl.html > bcd495cf6 > > > Diff: https://reviews.apache.org/r/69081/diff/1/ > > > Testing > --- > > Test Result: > > Tested. > > > Thanks, > > Qiang Zhang > >
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: RANGER-2251-ranger-0.7.patch > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch, RANGER-2251-ranger-0.7.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68990: RANGER-2248 Sorting does not work in AbstractPredicateUtil.java
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68990/#review209913
---
Ship it!
Ship It!
- pengjianhua
On 十月 11, 2018, 7:32 a.m., Qiang Zhang wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68990/
> ---
>
> (Updated 十月 11, 2018, 7:32 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-2248
> https://issues.apache.org/jira/browse/RANGER-2248
>
>
> Repository: ranger
>
>
> Description
> ---
>
> Sorting does not work in AbstractPredicateUtil.java
>
>
> Diffs
> -
>
>
> agents-common/src/main/java/org/apache/ranger/plugin/store/AbstractPredicateUtil.java
> 4d2bc622b
>
>
> Diff: https://reviews.apache.org/r/68990/diff/1/
>
>
> Testing
> ---
>
> Tested api:
> http://rangeradmin:6080/service/plugins/policies?sortBy={sortBy}
> http://rangeradmin:6080/service/plugins/policies/service/name/{name}?sortBy={sortBy}
> http://rangeradmin:6080/service/plugins/policies/service/{id}?sortBy={sortBy}
> Verified sort results.
>
>
> Thanks,
>
> Qiang Zhang
>
>
Re: Review Request 69081: RANGER-2258 Improve the policy list page to prompt users when the service is disabled
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69081/#review209912 --- Ship it! Ship It! - pengjianhua On 十月 19, 2018, 8:06 a.m., Qiang Zhang wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69081/ > --- > > (Updated 十月 19, 2018, 8:06 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-2258 > https://issues.apache.org/jira/browse/RANGER-2258 > > > Repository: ranger > > > Description > --- > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. > > Modified screenshots: > > https://issues.apache.org/jira/secure/attachment/12944673/Modify.PNG > > > Diffs > - > > > security-admin/src/main/webapp/scripts/views/policies/RangerPolicyTableLayout.js > 115083881 > > security-admin/src/main/webapp/templates/policies/RangerPolicyTableLayout_tmpl.html > bcd495cf6 > > > Diff: https://reviews.apache.org/r/69081/diff/1/ > > > Testing > --- > > Test Result: > > Tested. > > > Thanks, > > Qiang Zhang > >
Re: Review Request 69080: RANGER-2257:Add policyID to error message when click the Access log of Audit
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69080/#review209911 --- Ship it! Ship It! - pengjianhua On 十月 19, 2018, 3:26 a.m., Qiang Zhang wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69080/ > --- > > (Updated 十月 19, 2018, 3:26 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, Velmurugan Periasamy, > and Zsombor Gegesy. > > > Bugs: RANGER-2257 > https://issues.apache.org/jira/browse/RANGER-2257 > > > Repository: ranger > > > Description > --- > > Check the Access log of Audit in RangerAdmin, > click on a log to see its corresponding policyID history, > If the policyID does not exist, the following error will occur: > No policy history found for given time: 2018-08-14T08:43:11Z > Please check the following screenshots: > https://issues.apache.org/jira/secure/attachment/12944645/OnlyTime.png > The information given in the above error message does not give policyID > information, > which can lead to user confusion. > Add policyID to modify the error message as follows: > No policy history found for given policy ID: 1 and event time: > 2018-08-14T08:43:11Z > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java > 5dfe446 > > > Diff: https://reviews.apache.org/r/69080/diff/1/ > > > Testing > --- > > #Test Result: > Tested. > > > Thanks, > > Qiang Zhang > >
