[jira] [Updated] (RANGER-4334) [Ranger UI] [React JS] Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
[ https://issues.apache.org/jira/browse/RANGER-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4334: Summary: [Ranger UI] [React JS] Options for permissions pop up for knox policies are not the same in Backbone UI and React JS (was: Options for permissions pop up for knox policies are not the same in Backbone UI and React JS) > [Ranger UI] [React JS] Options for permissions pop up for knox policies are > not the same in Backbone UI and React JS > > > Key: RANGER-4334 > URL: https://issues.apache.org/jira/browse/RANGER-4334 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > On backbone JS, when the user tries to create a policy for Knox, the > permissions pop up box displays only one option, "Allow", but in React JS, > when the user tries to create a policy for Knox, the permissions pop up box > contains two options, > "Allow" and "Select All". > Ideally, the options in both backbone and react JS should be the same, > and moreover, when only one option is displayed, then "Select all" option is > not required. > Hence, it is better to remove the "Select All" option for permission pop ups > containing only one option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4334) Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
[ https://issues.apache.org/jira/browse/RANGER-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4334: Labels: ranger-react (was: ) > Options for permissions pop up for knox policies are not the same in Backbone > UI and React JS > - > > Key: RANGER-4334 > URL: https://issues.apache.org/jira/browse/RANGER-4334 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > On backbone JS, when the user tries to create a policy for Knox, the > permissions pop up box displays only one option, "Allow", but in React JS, > when the user tries to create a policy for Knox, the permissions pop up box > contains two options, > "Allow" and "Select All". > Ideally, the options in both backbone and react JS should be the same, > and moreover, when only one option is displayed, then "Select all" option is > not required. > Hence, it is better to remove the "Select All" option for permission pop ups > containing only one option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4334) Options for permissions pop up for knox policies are not the same in Backbone UI and React JS
Brijesh Bhalala created RANGER-4334: --- Summary: Options for permissions pop up for knox policies are not the same in Backbone UI and React JS Key: RANGER-4334 URL: https://issues.apache.org/jira/browse/RANGER-4334 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala Fix For: 3.0.0 On backbone JS, when the user tries to create a policy for Knox, the permissions pop up box displays only one option, "Allow", but in React JS, when the user tries to create a policy for Knox, the permissions pop up box contains two options, "Allow" and "Select All". Ideally, the options in both backbone and react JS should be the same, and moreover, when only one option is displayed, then "Select all" option is not required. Hence, it is better to remove the "Select All" option for permission pop ups containing only one option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4333) Make ranger2.4 hive plugin compatible with hadoop 3.3.5+
[ https://issues.apache.org/jira/browse/RANGER-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caijialiang updated RANGER-4333: Attachment: image-2023-07-27-11-04-31-790.png > Make ranger2.4 hive plugin compatible with hadoop 3.3.5+ > --- > > Key: RANGER-4333 > URL: https://issues.apache.org/jira/browse/RANGER-4333 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: caijialiang >Priority: Major > Attachments: image-2023-07-27-11-03-56-152.png, > image-2023-07-27-11-04-31-790.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4333) Make ranger2.4 hive plugin compatible with hadoop 3.3.5+
[ https://issues.apache.org/jira/browse/RANGER-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caijialiang updated RANGER-4333: Attachment: image-2023-07-27-11-03-56-152.png > Make ranger2.4 hive plugin compatible with hadoop 3.3.5+ > --- > > Key: RANGER-4333 > URL: https://issues.apache.org/jira/browse/RANGER-4333 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: caijialiang >Priority: Major > Attachments: image-2023-07-27-11-03-56-152.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4333) Make ranger2.4 hive plugin compatible with hadoop 3.3.5+
caijialiang created RANGER-4333: --- Summary: Make ranger2.4 hive plugin compatible with hadoop 3.3.5+ Key: RANGER-4333 URL: https://issues.apache.org/jira/browse/RANGER-4333 Project: Ranger Issue Type: Improvement Components: plugins Reporter: caijialiang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4327) Make ranger2.4 hdfs plugin compatible with hadoop 3.3.5 +
[ https://issues.apache.org/jira/browse/RANGER-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caijialiang updated RANGER-4327: Summary: Make ranger2.4 hdfs plugin compatible with hadoop 3.3.5 + (was: Make ranger hdfs plugin support hadoop 3.3.5 +) > Make ranger2.4 hdfs plugin compatible with hadoop 3.3.5 + > - > > Key: RANGER-4327 > URL: https://issues.apache.org/jira/browse/RANGER-4327 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.3.0, 2.4.0 >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2023-07-25-17-30-18-136.png, > image-2023-07-26-13-40-10-555.png, patch3-RANGER-4327.diff > > > hadoop 3.3.5 has upgraded its jackson dependency and removed all jackson 1.x > packages, including the jackson-jaxrs jar. As a result, when starting with > the Ranger plugin enabled, Hadoop namenode fails to start due to the > inability to load jackson 1.x. > To address this issue and ensure compatibility with the Hadoop 3.3.5 upgrade, > we need to package jackson 1.x jars in the hdfs plugin as well,like the Ozone > did https://issues.apache.org/jira/browse/RANGER-2818. This will allow the > namenode to start successfully. > !image-2023-07-26-13-40-10-555.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4327) Make ranger hdfs plugin support hadoop 3.3.5 +
[ https://issues.apache.org/jira/browse/RANGER-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caijialiang updated RANGER-4327: Attachment: patch3-RANGER-4327.diff > Make ranger hdfs plugin support hadoop 3.3.5 + > -- > > Key: RANGER-4327 > URL: https://issues.apache.org/jira/browse/RANGER-4327 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.3.0, 2.4.0 >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2023-07-25-17-30-18-136.png, > image-2023-07-26-13-40-10-555.png, patch3-RANGER-4327.diff > > > hadoop 3.3.5 has upgraded its jackson dependency and removed all jackson 1.x > packages, including the jackson-jaxrs jar. As a result, when starting with > the Ranger plugin enabled, Hadoop namenode fails to start due to the > inability to load jackson 1.x. > To address this issue and ensure compatibility with the Hadoop 3.3.5 upgrade, > we need to package jackson 1.x jars in the hdfs plugin as well,like the Ozone > did https://issues.apache.org/jira/browse/RANGER-2818. This will allow the > namenode to start successfully. > !image-2023-07-26-13-40-10-555.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74529: RANGER-4332: updated AuditBatchQueue.log() to block instead of throwing 'Queue full' exception
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74529/#review225614 --- Ship it! Ship It! - Ramesh Mani On July 26, 2023, 10:37 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74529/ > --- > > (Updated July 26, 2023, 10:37 p.m.) > > > Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Monika > Kachhadiya, Ramesh Mani, Siddhesh Phatak, and Subhrat Chaudhary. > > > Bugs: RANGER-4332 > https://issues.apache.org/jira/browse/RANGER-4332 > > > Repository: ranger > > > Description > --- > > updated AuditBatchQueue.log() to block instead of throwing 'Queue full' > exception > > > Diffs > - > > > agents-audit/src/main/java/org/apache/ranger/audit/queue/AuditBatchQueue.java > d9cd52b59 > security-admin/src/test/java/org/apache/ranger/audit/TestAuditQueue.java > d30854bef > > > Diff: https://reviews.apache.org/r/74529/diff/1/ > > > Testing > --- > > - updated unit test to cover this scenario > - verified that all tests pass successfully > > > Thanks, > > Madhan Neethiraj > >
Re: Review Request 74523: RANGER-4329: Add guava and commons-logging to tagsync/pom.xml
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74523/#review225613 --- Ship it! Ship It! - Madhan Neethiraj On July 26, 2023, 6:13 p.m., Szymon Orzechowski wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74523/ > --- > > (Updated July 26, 2023, 6:13 p.m.) > > > Review request for ranger, Abhishek Kumar and Madhan Neethiraj. > > > Bugs: RANGER-4329 > https://issues.apache.org/jira/browse/RANGER-4329 > > > Repository: ranger > > > Description > --- > > Tagsync failed to start due to missing jars on the classpath. JIRA issue > https://issues.apache.org/jira/browse/RANGER-4329 > > > Diffs > - > > tagsync/pom.xml ede5e838a > > > Diff: https://reviews.apache.org/r/74523/diff/1/ > > > Testing > --- > > Tested using docker scripts from dev-support > > > Thanks, > > Szymon Orzechowski > >
[jira] [Commented] (RANGER-4330) Ranger docker container fails to start due to change in ubuntu base image arch
[ https://issues.apache.org/jira/browse/RANGER-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747679#comment-17747679 ] Abhishek Kumar commented on RANGER-4330: Merged in ranger-2.4 branch: [https://github.com/apache/ranger/commit/948ff93297add2b44463d3c4ea5cee5a1cf0cc09] > Ranger docker container fails to start due to change in ubuntu base image arch > -- > > Key: RANGER-4330 > URL: https://issues.apache.org/jira/browse/RANGER-4330 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.1 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > There is a change in CPU arch from amd64 to arm64 in the ubuntu 20.04 base > image, the Java path changes due to this which affects all docker containers > since all images depend on this base image. > > Before > > abhishek.kumar@21127 ~ % docker run -ti --rm 14be0685b768 /bin/bash > > WARNING: The requested image's platform (linux/amd64) does not match the > detected host platform (linux/arm64/v8) and no specific platform was requested > root@f2f0f72e8b00:/# dpkg --print-architecture > amd64 > After > > abhishek.kumar@21127 ~ % docker run -ti --rm ubuntu:20.04 /bin/bash > root@4cb19655e55c:/# dpkg --print-architecture > arm64 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4330) Ranger docker container fails to start due to change in ubuntu base image arch
[ https://issues.apache.org/jira/browse/RANGER-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4330. Fix Version/s: 2.4.1 Resolution: Fixed > Ranger docker container fails to start due to change in ubuntu base image arch > -- > > Key: RANGER-4330 > URL: https://issues.apache.org/jira/browse/RANGER-4330 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.1 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.4.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > There is a change in CPU arch from amd64 to arm64 in the ubuntu 20.04 base > image, the Java path changes due to this which affects all docker containers > since all images depend on this base image. > > Before > > abhishek.kumar@21127 ~ % docker run -ti --rm 14be0685b768 /bin/bash > > WARNING: The requested image's platform (linux/amd64) does not match the > detected host platform (linux/arm64/v8) and no specific platform was requested > root@f2f0f72e8b00:/# dpkg --print-architecture > amd64 > After > > abhishek.kumar@21127 ~ % docker run -ti --rm ubuntu:20.04 /bin/bash > root@4cb19655e55c:/# dpkg --print-architecture > arm64 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] kumaab merged pull request #276: RANGER-4330: Fix ranger container startup due to arch change in ubuntu base image
kumaab merged PR #276: URL: https://github.com/apache/ranger/pull/276 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (RANGER-4332) AuditBatchQueue.log() should block instead of throwing 'Queue full' exception
[
https://issues.apache.org/jira/browse/RANGER-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-4332:
-
Attachment: RANGER-4332.patch
> AuditBatchQueue.log() should block instead of throwing 'Queue full' exception
> -
>
> Key: RANGER-4332
> URL: https://issues.apache.org/jira/browse/RANGER-4332
> Project: Ranger
> Issue Type: Bug
> Components: audit
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4332.patch
>
>
> Ranger audit framework uses AuditBatchQueue to buffer audit logs before
> sending as a batch to the destination. This helps to greatly reduce the
> overhead in writing audit logs to destinations like Solr, HDFS, S3. When the
> buffer held in AuditBatchQueue is full, attempts to add a log should wait
> until the buffer has space . Instead, IllegalStateException("Queue full")
> exception is thrown, which results in the audit log to be not sent to the
> destination. AuditBatchQueue should be updated to wait until the buffer has
> space to add entries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74529: RANGER-4332: updated AuditBatchQueue.log() to block instead of throwing 'Queue full' exception
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74529/ --- Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Monika Kachhadiya, Ramesh Mani, Siddhesh Phatak, and Subhrat Chaudhary. Bugs: RANGER-4332 https://issues.apache.org/jira/browse/RANGER-4332 Repository: ranger Description --- updated AuditBatchQueue.log() to block instead of throwing 'Queue full' exception Diffs - agents-audit/src/main/java/org/apache/ranger/audit/queue/AuditBatchQueue.java d9cd52b59 security-admin/src/test/java/org/apache/ranger/audit/TestAuditQueue.java d30854bef Diff: https://reviews.apache.org/r/74529/diff/1/ Testing --- - updated unit test to cover this scenario - verified that all tests pass successfully Thanks, Madhan Neethiraj
[jira] [Created] (RANGER-4332) AuditBatchQueue.log() should block instead of throwing 'Queue full' exception
Madhan Neethiraj created RANGER-4332:
Summary: AuditBatchQueue.log() should block instead of throwing
'Queue full' exception
Key: RANGER-4332
URL: https://issues.apache.org/jira/browse/RANGER-4332
Project: Ranger
Issue Type: Bug
Components: audit
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
Ranger audit framework uses AuditBatchQueue to buffer audit logs before sending
as a batch to the destination. This helps to greatly reduce the overhead in
writing audit logs to destinations like Solr, HDFS, S3. When the buffer held in
AuditBatchQueue is full, attempts to add a log should wait until the buffer has
space . Instead, IllegalStateException("Queue full") exception is thrown, which
results in the audit log to be not sent to the destination. AuditBatchQueue
should be updated to wait until the buffer has space to add entries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4044) Publish official docker images for ranger to dockerhub
[ https://issues.apache.org/jira/browse/RANGER-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4044: --- Fix Version/s: 2.4.1 (was: 3.0.0) > Publish official docker images for ranger to dockerhub > -- > > Key: RANGER-4044 > URL: https://issues.apache.org/jira/browse/RANGER-4044 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Labels: Docker > Fix For: 2.4.1 > > > Similar to other apache products having official docker images on dockerhub > ([https://hub.docker.com/u/apache]), ranger can have its own image published > to the repository as well. > To begin with this can be just ranger-admin and its dependencies. > It'll be good to have one ranger image published to dockerhub with every > apache release. > CC: [~madhan] , [~vel], [~abhay] , [~rmani] , [~mehul] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] kumaab commented on pull request #276: RANGER-4330: Fix ranger container startup due to arch change in ubuntu base image
kumaab commented on PR #276: URL: https://github.com/apache/ranger/pull/276#issuecomment-1652484394 Verified ranger container running fine with the latest changes on the PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ranger] kumaab commented on a diff in pull request #276: RANGER-4330: Fix ranger container startup due to arch change in ubuntu base image
kumaab commented on code in PR #276: URL: https://github.com/apache/ranger/pull/276#discussion_r1275468744 ## dev-support/ranger-docker/README.md: ## @@ -40,6 +40,7 @@ Docker files in this folder create docker images and run them to build Apache Ra export DOCKER_BUILDKIT=1 export COMPOSE_DOCKER_CLI_BUILD=1 export RANGER_DB_TYPE=postgres + export TARGETARCH=arm64 Review Comment: Got it, thank you! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (RANGER-4330) Ranger docker container fails to start due to change in ubuntu base image arch
[ https://issues.apache.org/jira/browse/RANGER-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747655#comment-17747655 ] Abhishek Kumar commented on RANGER-4330: PR available here: [https://github.com/apache/ranger/pull/276] > Ranger docker container fails to start due to change in ubuntu base image arch > -- > > Key: RANGER-4330 > URL: https://issues.apache.org/jira/browse/RANGER-4330 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.1 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > There is a change in CPU arch from amd64 to arm64 in the ubuntu 20.04 base > image, the Java path changes due to this which affects all docker containers > since all images depend on this base image. > > Before > > abhishek.kumar@21127 ~ % docker run -ti --rm 14be0685b768 /bin/bash > > WARNING: The requested image's platform (linux/amd64) does not match the > detected host platform (linux/arm64/v8) and no specific platform was requested > root@f2f0f72e8b00:/# dpkg --print-architecture > amd64 > After > > abhishek.kumar@21127 ~ % docker run -ti --rm ubuntu:20.04 /bin/bash > root@4cb19655e55c:/# dpkg --print-architecture > arm64 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] mneethiraj commented on a diff in pull request #276: RANGER-4330: Fix ranger container startup due to arch change in ubuntu base image
mneethiraj commented on code in PR #276: URL: https://github.com/apache/ranger/pull/276#discussion_r1275460143 ## dev-support/ranger-docker/README.md: ## @@ -40,6 +40,7 @@ Docker files in this folder create docker images and run them to build Apache Ra export DOCKER_BUILDKIT=1 export COMPOSE_DOCKER_CLI_BUILD=1 export RANGER_DB_TYPE=postgres + export TARGETARCH=arm64 Review Comment: @kumaab - TARGETARCH will be automatically set if following env is set while building the image: `DOCKER_BUILDKIT=1 ` More on this at https://docs.docker.com/build/buildkit/ and https://docs.docker.com/engine/reference/builder/. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ranger] kumaab commented on a diff in pull request #276: RANGER-4330: Fix ranger container startup due to arch change in ubuntu base image
kumaab commented on code in PR #276: URL: https://github.com/apache/ranger/pull/276#discussion_r1275445345 ## dev-support/ranger-docker/Dockerfile.ranger-base: ## @@ -25,7 +25,7 @@ RUN apt-get update && \ pip3 install requests # Set environment variables -ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64 +ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-arm64 Review Comment: Sure, I've updated the patch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ranger] mneethiraj commented on a diff in pull request #276: RANGER-4330: Fix ranger container startup due to arch change in ubuntu base image
mneethiraj commented on code in PR #276: URL: https://github.com/apache/ranger/pull/276#discussion_r1275410455 ## dev-support/ranger-docker/Dockerfile.ranger-base: ## @@ -25,7 +25,7 @@ RUN apt-get update && \ pip3 install requests # Set environment variables -ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64 +ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-arm64 Review Comment: RANGER-4181 replaced hardcoding of "amd64" with TARGETARCH. I suggest to consider a similar approach here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Review Request 74523: RANGER-4329: Add guava and commons-logging to tagsync/pom.xml
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74523/ --- (Updated July 26, 2023, 6:13 p.m.) Review request for ranger, Abhishek Kumar and Madhan Neethiraj. Bugs: RANGER-4329 https://issues.apache.org/jira/browse/RANGER-4329 Repository: ranger Description --- Tagsync failed to start due to missing jars on the classpath. JIRA issue https://issues.apache.org/jira/browse/RANGER-4329 Diffs - tagsync/pom.xml ede5e838a Diff: https://reviews.apache.org/r/74523/diff/1/ Testing (updated) --- Tested using docker scripts from dev-support Thanks, Szymon Orzechowski
Review Request 74528: RANGER-4323: GDS: Need new api to get details of dataset listing page
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74528/ --- Review request for ranger, Madhan Neethiraj and Subhrat Chaudhary. Bugs: RANGER-4323 https://issues.apache.org/jira/browse/RANGER-4323 Repository: ranger Description --- We get users,groups,roles all we get in response from one API (/xusers/users/groups/roles) we can also pass Query Params like name,isVisible Also we can PartialSearch Name for users,groups,roles Diffs - security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java 9a2253a3d security-admin/src/main/java/org/apache/ranger/view/VXRangerPrincipalView.java PRE-CREATION Diff: https://reviews.apache.org/r/74528/diff/1/ Testing --- We get users,groups,roles combined in response from API (/xusers/users/groups/roles) we can pass query params like name(PartialSearch Available),isVisible to filter the users,groups,roles we get in response Thanks, Prashant Satam
[jira] [Assigned] (RANGER-4325) Need api for collective search of user/group/roles
[ https://issues.apache.org/jira/browse/RANGER-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4325: -- Assignee: Prashant Satam > Need api for collective search of user/group/roles > -- > > Key: RANGER-4325 > URL: https://issues.apache.org/jira/browse/RANGER-4325 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Anand Nadar >Assignee: Prashant Satam >Priority: Major > > The api should search partially for user/groups/roles and return the results > as an object with user/group/role list -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74527: RANGER-4331: Fixes for search filter on Audits tabs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74527/#review225612 --- Ship it! Ship It! - Brijesh Bhalala On July 26, 2023, 7:38 a.m., Mugdha Varadkar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74527/ > --- > > (Updated July 26, 2023, 7:38 a.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, > Mehul Parikh, and Nikunj Pansuriya. > > > Bugs: RANGER-4331 > https://issues.apache.org/jira/browse/RANGER-4331 > > > Repository: ranger > > > Description > --- > > Issues : > > 1) On Access Tab "Exclude Service Users" option is not getting saved when > user comes again on that tab. > 2) Mismatch in the url search param for search filters having options. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/utils/XAUtils.js > 30fc4225be18bda54f4cb0de730196507ca4218a > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AccessLogs.jsx > b30c6f32f841ee683721d7921b6b79f07e2c7068 > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AuditLayout.jsx > a51b7ac2fe799b2f8a6c5be4f92798ba1ec071f9 > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/PluginStatusLogs.jsx > b1bcca65622ee4285a4f7707d63cf475586fd790 > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/PluginsLog.jsx > 37ae4e1c89c21f001aaacab98eae78b59bac2372 > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx > db2710bb9642e50a6efb130e5b61abf063cdb91f > > > Diff: https://reviews.apache.org/r/74527/diff/1/ > > > Testing > --- > > Tested changes on a cluster setup with Ranger Admin build with React JS code > base. > > Successful completion of build command : > mvn clean compile package -Psecurity-admin-react > > > Thanks, > > Mugdha Varadkar > >
[jira] [Updated] (RANGER-4290) Adding uiHint attribute in policy condition
[ https://issues.apache.org/jira/browse/RANGER-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4290: -- Attachment: (was: RANGER-4290.1.patch) > Adding uiHint attribute in policy condition > --- > > Key: RANGER-4290 > URL: https://issues.apache.org/jira/browse/RANGER-4290 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0002-RANGER-4290.patch > > > RANGER-4157 introduced addition of Policy conditions to all service-defs. > However, this update does not include uiHint attribute in policy condition. > This needs to be fixed so that uiHint attribute will be available in all > service-defs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4290) Adding uiHint attribute in policy condition
[ https://issues.apache.org/jira/browse/RANGER-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4290: -- Attachment: 0002-RANGER-4290.patch > Adding uiHint attribute in policy condition > --- > > Key: RANGER-4290 > URL: https://issues.apache.org/jira/browse/RANGER-4290 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0002-RANGER-4290.patch > > > RANGER-4157 introduced addition of Policy conditions to all service-defs. > However, this update does not include uiHint attribute in policy condition. > This needs to be fixed so that uiHint attribute will be available in all > service-defs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74526: RANGER-4290: Adding uiHint attribute in policy condition
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74526/ --- (Updated July 26, 2023, 9:11 a.m.) Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-4290 https://issues.apache.org/jira/browse/RANGER-4290 Repository: ranger Description --- RANGER-4157 introduced addition of Policy conditions to all service-defs. However, this update does not include uiHint attribute in policy condition. This needs to be fixed so that uiHint attribute will be available in all service-defs. Diffs (updated) - security-admin/src/main/java/org/apache/ranger/service/RangerServiceDefServiceBase.java 91d5f26bc Diff: https://reviews.apache.org/r/74526/diff/2/ Changes: https://reviews.apache.org/r/74526/diff/1-2/ Testing --- Tested for service-defs and UiHint attribute is present in policy condition. Thanks, sanket shelar
[jira] [Updated] (RANGER-4290) Adding uiHint attribute in policy condition
[ https://issues.apache.org/jira/browse/RANGER-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4290: -- Attachment: RANGER-4290.1.patch > Adding uiHint attribute in policy condition > --- > > Key: RANGER-4290 > URL: https://issues.apache.org/jira/browse/RANGER-4290 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: RANGER-4290.1.patch > > > RANGER-4157 introduced addition of Policy conditions to all service-defs. > However, this update does not include uiHint attribute in policy condition. > This needs to be fixed so that uiHint attribute will be available in all > service-defs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74526: RANGER-4290: Adding uiHint attribute in policy condition
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74526/ --- Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-4290 https://issues.apache.org/jira/browse/RANGER-4290 Repository: ranger Description --- RANGER-4157 introduced addition of Policy conditions to all service-defs. However, this update does not include uiHint attribute in policy condition. This needs to be fixed so that uiHint attribute will be available in all service-defs. Diffs - security-admin/src/main/java/org/apache/ranger/service/RangerServiceDefServiceBase.java 91d5f26bc Diff: https://reviews.apache.org/r/74526/diff/1/ Testing --- Tested for service-defs and UiHint attribute is present in policy condition. Thanks, sanket shelar
Review Request 74527: RANGER-4331: Fixes for search filter on Audits tabs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74527/ --- Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, and Nikunj Pansuriya. Bugs: RANGER-4331 https://issues.apache.org/jira/browse/RANGER-4331 Repository: ranger Description --- Issues : 1) On Access Tab "Exclude Service Users" option is not getting saved when user comes again on that tab. 2) Mismatch in the url search param for search filters having options. Diffs - security-admin/src/main/webapp/react-webapp/src/utils/XAUtils.js 30fc4225be18bda54f4cb0de730196507ca4218a security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AccessLogs.jsx b30c6f32f841ee683721d7921b6b79f07e2c7068 security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AuditLayout.jsx a51b7ac2fe799b2f8a6c5be4f92798ba1ec071f9 security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/PluginStatusLogs.jsx b1bcca65622ee4285a4f7707d63cf475586fd790 security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/PluginsLog.jsx 37ae4e1c89c21f001aaacab98eae78b59bac2372 security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx db2710bb9642e50a6efb130e5b61abf063cdb91f Diff: https://reviews.apache.org/r/74527/diff/1/ Testing --- Tested changes on a cluster setup with Ranger Admin build with React JS code base. Successful completion of build command : mvn clean compile package -Psecurity-admin-react Thanks, Mugdha Varadkar
[jira] [Updated] (RANGER-4331) Fixes for search filter on Audits tabs
[ https://issues.apache.org/jira/browse/RANGER-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4331: Attachment: 0001-RANGER-4331.patch > Fixes for search filter on Audits tabs > -- > > Key: RANGER-4331 > URL: https://issues.apache.org/jira/browse/RANGER-4331 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4331.patch > > > Issues : > 1) On Access Tab "Exclude Service Users" option is not getting saved when > user comes again on that tab. > 2) Mismatch in the url search param for search filters having options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4331) Fixes for search filter on Audits tabs
Mugdha Varadkar created RANGER-4331: --- Summary: Fixes for search filter on Audits tabs Key: RANGER-4331 URL: https://issues.apache.org/jira/browse/RANGER-4331 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Issues : 1) On Access Tab "Exclude Service Users" option is not getting saved when user comes again on that tab. 2) Mismatch in the url search param for search filters having options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74525: RANGER-4317: Error message displayed when resource lookup fails is not formatted properly
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74525/#review225611 --- Ship it! Ship It! - Mugdha Varadkar On July 26, 2023, 7:01 a.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74525/ > --- > > (Updated July 26, 2023, 7:01 a.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4317 > https://issues.apache.org/jira/browse/RANGER-4317 > > > Repository: ranger > > > Description > --- > > When a resource lookup fails on the new UI due to some config issue, > the error message is not displayed properly > But on backbone JS, it is displayed properly. > The error message on react js must be formatted properly > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/styles/style.css 8b86453a4 > > > Diff: https://reviews.apache.org/r/74525/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)The error message are formatted and displaying properly. > > > Thanks, > > Brijesh Bhalala > >
Re: Review Request 74524: RANGER-4293: Addendum change for Long User/group/role name overflowing from delete confirmation dialog box
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74524/#review225610 --- Ship it! Ship It! - Mugdha Varadkar On July 26, 2023, 6:44 a.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74524/ > --- > > (Updated July 26, 2023, 6:44 a.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4293 > https://issues.apache.org/jira/browse/RANGER-4293 > > > Repository: ranger > > > Description > --- > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > > Steps to reproduce: > > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdgfdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx > 991e27ea9 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx > e6293877c > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx > 95a21664d > > > Diff: https://reviews.apache.org/r/74524/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)Tested the User/Group/Role delete modules. > > > Thanks, > > Brijesh Bhalala > >
Review Request 74525: RANGER-4317: Error message displayed when resource lookup fails is not formatted properly
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74525/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4317 https://issues.apache.org/jira/browse/RANGER-4317 Repository: ranger Description --- When a resource lookup fails on the new UI due to some config issue, the error message is not displayed properly But on backbone JS, it is displayed properly. The error message on react js must be formatted properly Diffs - security-admin/src/main/webapp/react-webapp/src/styles/style.css 8b86453a4 Diff: https://reviews.apache.org/r/74525/diff/1/ Testing --- 1)Build and Verified Ranger Admin setup with this changes. 2)The error message are formatted and displaying properly. Thanks, Brijesh Bhalala
Review Request 74524: RANGER-4293: Addendum change for Long User/group/role name overflowing from delete confirmation dialog box
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74524/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4293 https://issues.apache.org/jira/browse/RANGER-4293 Repository: ranger Description --- When tried to delete a single user/group/role from UI. Inside the delete confirmation prompt the name of the entity is overflowing if the name is very large. Steps to reproduce: 1. create a user with very large username like "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdgfdgfdgfd" 2. Then try to delete it from the UI. 3. The name of the user flow out of the confirmation prompt. Current behaviour: The username is flowing out of the confirmation prompt. Expected behaviour: The username should be inside the confirmation prompt. If required there may be a scroll. Diffs - security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx 991e27ea9 security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx e6293877c security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx 95a21664d Diff: https://reviews.apache.org/r/74524/diff/1/ Testing --- 1)Build and Verified Ranger Admin setup with this changes. 2)Tested the User/Group/Role delete modules. Thanks, Brijesh Bhalala
[jira] [Updated] (RANGER-4293) [Ranger UI] [React JS] Long User/group/role name overflowing from delete confirmation dialog box
[ https://issues.apache.org/jira/browse/RANGER-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4293: Attachment: 0001-RANGER-4293-Addendum.patch > [Ranger UI] [React JS] Long User/group/role name overflowing from delete > confirmation dialog box > > > Key: RANGER-4293 > URL: https://issues.apache.org/jira/browse/RANGER-4293 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4293-Addendum.patch, 0001-RANGER-4293.patch, > Screenshot 2023-06-19 at 3.05.26 PM.png > > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > Steps to reproduce: > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdgfdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (RANGER-4293) [Ranger UI] [React JS] Long User/group/role name overflowing from delete confirmation dialog box
[ https://issues.apache.org/jira/browse/RANGER-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened RANGER-4293: - > [Ranger UI] [React JS] Long User/group/role name overflowing from delete > confirmation dialog box > > > Key: RANGER-4293 > URL: https://issues.apache.org/jira/browse/RANGER-4293 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4293.patch, Screenshot 2023-06-19 at 3.05.26 > PM.png > > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > Steps to reproduce: > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdgfdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. -- This message was sent by Atlassian Jira (v8.20.10#820010)
