[jira] [Updated] (RANGER-4165) API to find whether a user/group is authorized to the give operation on any resource of give type

2023-04-04 Thread Ramesh Mani (Jira) 


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

Ramesh Mani updated RANGER-4165:

Description: 
API to find whether a user/group is authorized to the given operation on any 
resource of give type.

This is needed to implement a Ranger Kafka authorizer API which checks if the 
caller is authorized to perform the given ACL operation on at least one 
resource of the given type.

[https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType])

  was:
API to find whether a user/group is authorized to the give operation on any 
resource of give type.

This is needed to implement a Ranger Kafka authorizer API which checks if the 
caller is authorized to perform the given ACL operation on at least one 
resource of the given type.

https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType)


> API to find whether a user/group is authorized to the give operation on any 
> resource of give type
> -
>
> Key: RANGER-4165
> URL: https://issues.apache.org/jira/browse/RANGER-4165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> API to find whether a user/group is authorized to the given operation on any 
> resource of give type.
> This is needed to implement a Ranger Kafka authorizer API which checks if the 
> caller is authorized to perform the given ACL operation on at least one 
> resource of the given type.
> [https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType])



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74366: RANGER-4136: Incorrect processing of tag-deltas by RangerTagEnricher - Part 2

2023-04-04 Thread Abhay Kulkarni 


> On April 4, 2023, 6:54 p.m., Madhan Neethiraj wrote:
> > agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java
> > Lines 582 (patched)
> > 
> >
> > I would suggest to avoid updating oldMatchers, as this may be a 
> > collection referenced within enrichedServiceTags. Instead, consider 
> > handling skipping of entries in notMatched within the following for loop at 
> > #585.

oldMatchers need to be updated, otherwise, line 602 will remove notMatched 
service-resource-matchers from resourceMatchers passed to this function, which 
will remove non-SELF matched matchers from the Trie indexes as well.


- Abhay


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


On April 4, 2023, 5:52 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74366/
> ---
> 
> (Updated April 4, 2023, 5:52 p.m.)
> 
> 
> Review request for ranger, madhan, Madhan Neethiraj, Ramesh Mani, Sailaja 
> Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4136
> https://issues.apache.org/jira/browse/RANGER-4136
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger supports incremental tag downloads when configured. When a mapping for 
> a service-resource is changed, the tag download request provides only the 
> updated service-resource. RangerTagEnricher is expected to remove the 
> existing service-resource and the associated tags from its cache and add it 
> back with updated associated tags.
> 
> Current code does not remove the existing service-resource and its associated 
> tags correctly leading to incorrect tags to be retrieved for the 
> service-resource.
> 
> More debugging help is added to monitor the process flow for the incremental 
> tag processing.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java
>  198d24d97 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceTags.java 
> 9b902789a 
> 
> 
> Diff: https://reviews.apache.org/r/74366/diff/3/
> 
> 
> Testing
> ---
> 
> Passed all unit tests. Verified that incremental tagged entities are 
> correctly processed and properly cleaned up.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 74366: RANGER-4136: Incorrect processing of tag-deltas by RangerTagEnricher - Part 2

2023-04-04 Thread Madhan Neethiraj 

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


Fix it, then Ship it!




Given the complex and critical nature of handling deltas, consider adding unit 
tests. This can be tracked with a separate JIRA.


agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java
Lines 582 (patched)


I would suggest to avoid updating oldMatchers, as this may be a collection 
referenced within enrichedServiceTags. Instead, consider handling skipping of 
entries in notMatched within the following for loop at #585.


- Madhan Neethiraj


On April 4, 2023, 5:52 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74366/
> ---
> 
> (Updated April 4, 2023, 5:52 p.m.)
> 
> 
> Review request for ranger, madhan, Madhan Neethiraj, Ramesh Mani, Sailaja 
> Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4136
> https://issues.apache.org/jira/browse/RANGER-4136
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger supports incremental tag downloads when configured. When a mapping for 
> a service-resource is changed, the tag download request provides only the 
> updated service-resource. RangerTagEnricher is expected to remove the 
> existing service-resource and the associated tags from its cache and add it 
> back with updated associated tags.
> 
> Current code does not remove the existing service-resource and its associated 
> tags correctly leading to incorrect tags to be retrieved for the 
> service-resource.
> 
> More debugging help is added to monitor the process flow for the incremental 
> tag processing.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java
>  198d24d97 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceTags.java 
> 9b902789a 
> 
> 
> Diff: https://reviews.apache.org/r/74366/diff/3/
> 
> 
> Testing
> ---
> 
> Passed all unit tests. Verified that incremental tagged entities are 
> correctly processed and properly cleaned up.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

[jira] [Resolved] (RANGER-4166) ranger2 build failed

2023-04-04 Thread Madhan Neethiraj (Jira) 


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

Madhan Neethiraj resolved RANGER-4166.
--
Fix Version/s: 3.0.0
   2.4.1
   Resolution: Fixed

[~jialiang]  - thank you for the fix. It is now merged in master and ranger-2.4 
branches.

 
{noformat}
commit b6650fc8c81fd339052bb2999f4653460549fdb2 (HEAD -> master, origin/master, 
origin/HEAD)
Author: jialiang <2510095...@qq.com>
Date:   Tue Apr 4 11:00:24 2023 +0800

RANGER-4166: update maven-assembly-plugin version to 3.4.2

Signed-off-by: Madhan Neethiraj 
 {noformat}
 
{noformat}
commit 03c45aec6477ee88f8216ab9064e47b28b9232b5 (HEAD -> ranger-2.4, 
origin/ranger-2.4)
Author: jialiang <2510095...@qq.com>
Date:   Tue Apr 4 11:00:24 2023 +0800

RANGER-4166: update maven-assembly-plugin version to 3.4.2

Signed-off-by: Madhan Neethiraj 
(cherry picked from commit b6650fc8c81fd339052bb2999f4653460549fdb2)
 {noformat}

> ranger2  build failed
> -
>
> Key: RANGER-4166
> URL: https://issues.apache.org/jira/browse/RANGER-4166
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.3.0, 2.4.0
>Reporter: caijialiang
>Priority: Major
> Fix For: 3.0.0, 2.4.1
>
> Attachments: 
> 0001-RANGER-4166-fix-the-old-version-of-the-assembly-plug.patch, 
> image-2023-04-01-18-31-58-091.png, image-2023-04-01-18-33-29-756.png, 
> image-2023-04-04-10-28-23-029.png, image-2023-04-04-10-29-20-811.png, 
> image-2023-04-04-10-29-26-077.png, image-2023-04-04-10-29-41-802.png, 
> image-2023-04-04-10-29-56-998.png, image-2023-04-04-10-30-06-393.png, 
> image-2023-04-04-10-30-48-140.png, image-2023-04-04-10-31-13-216.png, 
> image-2023-04-04-10-31-37-426.png, image-2023-04-04-10-31-59-019.png, 
> image-2023-04-04-10-32-09-582.png, image-2023-04-04-10-32-19-271.png, 
> image-2023-04-04-11-05-05-371.png
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
>  
> summary：Here we mainly discuss how to reason and reproduce this compilation 
> error stably.
> environment
> [root@gs-server-12223 ~]# locale
> LANG=zh_CN.UTF-8
> LC_CTYPE="zh_CN.UTF-8"
> LC_NUMERIC="zh_CN.UTF-8"
> LC_TIME="zh_CN.UTF-8"
> LC_COLLATE="zh_CN.UTF-8"
> LC_MONETARY="zh_CN.UTF-8"
> LC_MESSAGES="zh_CN.UTF-8"
> LC_PAPER="zh_CN.UTF-8"
> LC_NAME="zh_CN.UTF-8"
> LC_ADDRESS="zh_CN.UTF-8"
> LC_TELEPHONE="zh_CN.UTF-8"
> LC_MEASUREMENT="zh_CN.UTF-8"
> LC_IDENTIFICATION="zh_CN.UTF-8"
> LC_ALL=zh_CN.UTF-8
> lsb_release -a
> LSB Version: :core-4.1-amd64:core-4.1-noarch
> Distributor ID: CentOS
> Description: CentOS Linux release 7.4.1708 (Core)
> Release: 7.4.1708
> Codename: Core
> uname -a
> Linux gs-server-12223 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 
> 2017 x86_64 x86_64 x86_64 GNU/Linux
> maven version 3.6.3
>  
> description：
> There are compilation errors when building Ranger 2.3 and Ranger 2.4 in a 
> Linux environment.
> Compilation command：
> mvn -Pall clean compile package install -Dmaven.test.skip=true 
> -DskipTests=true -Dfindbugs.skip=true -Dcheckstyle.skip=true 
> -Djacoco.skip=true -Dpmd.skip=true -Drat.skip=true -Dspotbugs.skip=true 
> -Dhadoop.version=3.3.4 -Dhbase.version=2.4.13 -Dhive.version=3.1.3 
> -Dkafka.version=2.8.1 -Dsolr.version=8.11.2 -Dzookeeper.version=3.6.4
> The following two patches were applied to ranger2.3 in order to compile 
> successfully.
> git apply ../ranger/patch1-RANGER-3818.diff
> git apply ../patch0-RANGER-3373.diff
> *The compilation of ranger 2.3 fails with the following error:*
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default) on 
> project ranger-distro: Failed to create assembly: Error creating assembly 
> archive schema-registry-plugin: Problem creating jar: 
> jar:file:/home/jialiang/prjs/ranger/distro/target/ranger-distro-2.3.0.jar!/META-INF/maven/org.apache.ranger/ranger-distro/pom.xml:
>  JAR entry META-INF/maven/org.apache.ranger/ranger-distro/pom.xml not found 
> in /home/jialiang/prjs/ranger/distro/target/ranger-distro-2.3.0.jar -> [Help 
> 1] {code}
>  
> *ranger2.4 did not apply any patches, and compilation errors are as follows：*
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default) on 
> project ranger-distro: Failed to create assembly: Error creating assembly 
> archive schema-registry-plugin: IOException when zipping 
> rMETA-INF/maven/org.apache.ranger/ranger-distro/pom.properties: invalid code 
> lengths set -> [Help 1]{code}
> According to the compilation error message of ranger2.4, it is suspected that 
> the issue is related to encoding. After checking the encoding format of the 
> corresponding file, it is found to be ASCII, while Linux defaults to UTF-8
>  
> file ./distro/target/maven-archiver/pom.properties
>

Re: Review Request 74366: RANGER-4136: Incorrect processing of tag-deltas by RangerTagEnricher - Part 2

2023-04-04 Thread Abhay Kulkarni 

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

(Updated April 4, 2023, 5:52 p.m.)


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


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


Repository: ranger


Description
---

Ranger supports incremental tag downloads when configured. When a mapping for a 
service-resource is changed, the tag download request provides only the updated 
service-resource. RangerTagEnricher is expected to remove the existing 
service-resource and the associated tags from its cache and add it back with 
updated associated tags.

Current code does not remove the existing service-resource and its associated 
tags correctly leading to incorrect tags to be retrieved for the 
service-resource.

More debugging help is added to monitor the process flow for the incremental 
tag processing.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java
 198d24d97 
  agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceTags.java 
9b902789a 


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

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


Testing
---

Passed all unit tests. Verified that incremental tagged entities are correctly 
processed and properly cleaned up.


Thanks,

Abhay Kulkarni

Re: Review Request 74379: RANGER-4164:Adding contributor name into ranger

2023-04-04 Thread Ramesh Mani 

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


Ship it!




Ship It!

- Ramesh Mani


On April 4, 2023, 3:41 p.m., Ramachandran Krishnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74379/
> ---
> 
> (Updated April 4, 2023, 3:41 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
> Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4164
> https://issues.apache.org/jira/browse/RANGER-4164
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-4164:Adding contributor name into ranger
> 
> 
> Diffs
> -
> 
>   docs/pom.xml 94f90abe6 
> 
> 
> Diff: https://reviews.apache.org/r/74379/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramachandran Krishnan
> 
>

Re: Review Request 74380: RANGER-4166: fix the old version of the assembly plugin bug, which causes compilation failure for ranger assembly:assembly or assembly:single

2023-04-04 Thread Madhan Neethiraj 

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


Ship it!




> 1.To reproduce the error, compile using the following command without making 
> any modifications.
mvn clean compile package install assembly:single  -Dmaven.test.skip=true 
-DskipTests=true  -Dfindbugs.skip=true -Dcheckstyle.skip=true   
-Djacoco.skip=true -Dpmd.skip=true -Drat.skip=true  -Dspotbugs.skip=true  
-Dhadoop.version=3.3.4  -Dhbase.version=2.4.13  -Dhive.version=3.1.3  
-Dkafka.version=2.8.1  -Dsolr.version=8.11.2  -Dzookeeper.version=3.6.4

On the lastest master branch, build with above command completes successfully 
without this patch.

However, it is good to use newer version of assembly.plugin.version. Will get 
this fix merged shortly. Thanks!

- Madhan Neethiraj


On April 4, 2023, 9:09 a.m., jialiang cai wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74380/
> ---
> 
> (Updated April 4, 2023, 9:09 a.m.)
> 
> 
> Review request for ranger and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-4166
> https://issues.apache.org/jira/browse/RANGER-4166
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The root cause of this issue is an encoding bug caused by the outdated 
> compression library dependency in the assembly-plugin of ranger. I have added 
> the detailed analysis and the steps to reproduce the issue stably to this 
> link.
> 
> https://issues.apache.org/jira/browse/RANGER-4166
> 
> 
> Diffs
> -
> 
>   pom.xml de0617e2a 
> 
> 
> Diff: https://reviews.apache.org/r/74380/diff/1/
> 
> 
> Testing
> ---
> 
> how to test:
> 1.To reproduce the error, compile using the following command without making 
> any modifications.
> mvn clean compile package install assembly:single  -Dmaven.test.skip=true 
> -DskipTests=true  -Dfindbugs.skip=true -Dcheckstyle.skip=true   
> -Djacoco.skip=true -Dpmd.skip=true -Drat.skip=true  -Dspotbugs.skip=true  
> -Dhadoop.version=3.3.4  -Dhbase.version=2.4.13  -Dhive.version=3.1.3  
> -Dkafka.version=2.8.1  -Dsolr.version=8.11.2  -Dzookeeper.version=3.6.4
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default) on 
> project ranger-distro: Failed to create assembly: Error creating assembly 
> archive schema-registry-plugin: IOException when zipping 
> rMETA-INF/maven/org.apache.ranger/ranger-distro/pom.properties: invalid code 
> lengths set -> [Help 1]
> 
> 2.apply this patch , and continue to compile using the above command. The 
> error disappears and the compilation can proceed smoothly.
> 
> 
> Thanks,
> 
> jialiang cai
> 
>

[jira] [Updated] (RANGER-4164) Adding contributor name into ranger-site

2023-04-04 Thread Ramachandran (Jira) 


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

Ramachandran updated RANGER-4164:
-
Attachment: 0001-RANGER-4164-Adding-contributor-name-into-ranger-site.patch

> Adding contributor name into ranger-site
> 
>
> Key: RANGER-4164
> URL: https://issues.apache.org/jira/browse/RANGER-4164
> Project: Ranger
>  Issue Type: Task
>  Components: documentation
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Attachments: 
> 0001-RANGER-4164-Adding-contributor-name-into-ranger-site.patch
>
>
> Adding contributor name into ranger-site in
> [https://github.com/apache/ranger-site]
> to be visible in the [https://ranger.apache.org/team-list.html]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4164) Adding contributor name into ranger-site

2023-04-04 Thread Ramachandran (Jira) 


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

Ramachandran commented on RANGER-4164:
--

[~mad...@apache.org]  The review is available here 
:[https://reviews.apache.org/r/74379/]

 

> Adding contributor name into ranger-site
> 
>
> Key: RANGER-4164
> URL: https://issues.apache.org/jira/browse/RANGER-4164
> Project: Ranger
>  Issue Type: Task
>  Components: documentation
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Attachments: 
> 0001-RANGER-4164-Adding-contributor-name-into-ranger-site.patch
>
>
> Adding contributor name into ranger-site in
> [https://github.com/apache/ranger-site]
> to be visible in the [https://ranger.apache.org/team-list.html]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74379: RANGER-4164:Adding contributor name into ranger

2023-04-04 Thread Abhishek Kumar 

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


Ship it!




Ship It!

- Abhishek  Kumar


On April 4, 2023, 3:41 p.m., Ramachandran Krishnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74379/
> ---
> 
> (Updated April 4, 2023, 3:41 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
> Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4164
> https://issues.apache.org/jira/browse/RANGER-4164
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-4164:Adding contributor name into ranger
> 
> 
> Diffs
> -
> 
>   docs/pom.xml 94f90abe6 
> 
> 
> Diff: https://reviews.apache.org/r/74379/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramachandran Krishnan
> 
>

Re: Review Request 74379: RANGER-4164:Adding contributor name into ranger

2023-04-04 Thread Ramachandran Krishnan 

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

(Updated April 4, 2023, 3:41 p.m.)


Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and 
Velmurugan Periasamy.


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


Repository: ranger


Description
---

RANGER-4164:Adding contributor name into ranger


Diffs (updated)
-

  docs/pom.xml 94f90abe6 


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

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


Testing
---


Thanks,

Ramachandran Krishnan

Re: Review Request 74379: RANGER-4164:Adding contributor name into ranger

2023-04-04 Thread Ramachandran Krishnan 


> On April 4, 2023, 3:16 a.m., Abhishek  Kumar wrote:
> > The names are in alphabetical order, please revise the patch.

Done


- Ramachandran


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


On April 4, 2023, 3:41 p.m., Ramachandran Krishnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74379/
> ---
> 
> (Updated April 4, 2023, 3:41 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, 
> Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4164
> https://issues.apache.org/jira/browse/RANGER-4164
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-4164:Adding contributor name into ranger
> 
> 
> Diffs
> -
> 
>   docs/pom.xml 94f90abe6 
> 
> 
> Diff: https://reviews.apache.org/r/74379/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramachandran Krishnan
> 
>

Re: Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Mehul Parikh 

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


Ship it!




Ship It!

- Mehul Parikh


On April 4, 2023, 7:38 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74381/
> ---
> 
> (Updated April 4, 2023, 7:38 a.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, 
> Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4090
> https://issues.apache.org/jira/browse/RANGER-4090
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Resouce lookup exception message is not available in react UI
> 
> Steps to reproduce :
> 1. While creating policy enter any resouce name which is not available 
> 
> Actual : We are not getting any expception message  related to these resouce 
> while resouce lookup 
> 
> Expected : Like Old ui user should get these expection message for resource 
> lookup
> 
> Thanks
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
>  221f0ea1d 
>   
> security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
>  e9ed9bac6 
>   
> security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
>  f8fc7781f 
> 
> 
> Diff: https://reviews.apache.org/r/74381/diff/2/
> 
> 
> Testing
> ---
> 
> Tested that while resource lookup failed for resource, exception message 
> displayed properly.
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 74374: RANGER-4087 : Loader is still loading for resource field for policy creation even after Resource lookup API gives 200/204.

2023-04-04 Thread Nikunj Pansuriya 

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


Ship it!




Ship It!

- Nikunj Pansuriya


On April 3, 2023, 1:01 p.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74374/
> ---
> 
> (Updated April 3, 2023, 1:01 p.m.)
> 
> 
> Review request for ranger, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, 
> Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4087
> https://issues.apache.org/jira/browse/RANGER-4087
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Loader is still loading for resource field for policy creation even after 
> Resource lookup API gives 200/204
> 
> Steps to reproduce :
> 1. Create a hive Policy 
> 2. Edit that policy 
> 3. Go back to ranger home page and again navigate back to policy with edit 
> option
> 
> Actual :  Resouce fields are still having loader which seems its still 
> waiting for resouce even Resource lookup API gives 200/204.
> 
> Expected : Loader should not be there after some time
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
>  11b240c465d351a61b4a5689700d59f8c6ca06aa 
> 
> 
> Diff: https://reviews.apache.org/r/74374/diff/3/
> 
> 
> Testing
> ---
> 
> Tested
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 74337: RANGER-4033 Upgrade React version to 18.2.0

2023-04-04 Thread Nikunj Pansuriya 

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


Ship it!




Ship It!

- Nikunj Pansuriya


On April 3, 2023, 12:52 p.m., Mugdha Varadkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74337/
> ---
> 
> (Updated April 3, 2023, 12:52 p.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, 
> Mehul Parikh, and Nikunj Pansuriya.
> 
> 
> Bugs: RANGER-4033
> https://issues.apache.org/jira/browse/RANGER-4033
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Currently Ranger React code base is using version - 17.0.2. Need to upgrade 
> the existing react version to latest 18.2.0.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/react-webapp/README.md 
> d2a3b1fbd2a31e50e3d5c6d435001de43b3fba77 
>   security-admin/src/main/webapp/react-webapp/package-lock.json 
> aba80451f5c09e0e13f1657c3e5a01236051833d 
>   security-admin/src/main/webapp/react-webapp/package.json 
> 5b930a0bff196d5229c5fb536336d31372a9eb38 
>   
> security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/popover.js
>  c329be9e49772869260b70e020e80a39460f3856 
>   security-admin/src/main/webapp/react-webapp/src/index.jsx 
> 67ff4d87307efefdfb23c2a55d4fafba1faf6305 
> 
> 
> Diff: https://reviews.apache.org/r/74337/diff/4/
> 
> 
> Testing
> ---
> 
> Tested Ranger React build using below command,
> mvn clean compile package -DskipTests -Psecurity-admin-react
> 
> Successfully setup Ranger Admin UI with updated react 18.2.0 version.
> 
> 
> Thanks,
> 
> Mugdha Varadkar
> 
>

Re: Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Brijesh Bhalala 

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


Ship it!




Ship It!

- Brijesh Bhalala


On April 4, 2023, 7:38 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74381/
> ---
> 
> (Updated April 4, 2023, 7:38 a.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Madhan Neethiraj, 
> Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4090
> https://issues.apache.org/jira/browse/RANGER-4090
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Resouce lookup exception message is not available in react UI
> 
> Steps to reproduce :
> 1. While creating policy enter any resouce name which is not available 
> 
> Actual : We are not getting any expception message  related to these resouce 
> while resouce lookup 
> 
> Expected : Like Old ui user should get these expection message for resource 
> lookup
> 
> Thanks
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
>  221f0ea1d 
>   
> security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
>  e9ed9bac6 
>   
> security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
>  f8fc7781f 
> 
> 
> Diff: https://reviews.apache.org/r/74381/diff/2/
> 
> 
> Testing
> ---
> 
> Tested that while resource lookup failed for resource, exception message 
> displayed properly.
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Mugdha Varadkar 

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


Ship it!




Ship It!

- Mugdha Varadkar


On April 4, 2023, 7:38 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74381/
> ---
> 
> (Updated April 4, 2023, 7:38 a.m.)
> 
> 
> Review request for ranger, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, 
> Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4090
> https://issues.apache.org/jira/browse/RANGER-4090
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Resouce lookup exception message is not available in react UI
> 
> Steps to reproduce :
> 1. While creating policy enter any resouce name which is not available 
> 
> Actual : We are not getting any expception message  related to these resouce 
> while resouce lookup 
> 
> Expected : Like Old ui user should get these expection message for resource 
> lookup
> 
> Thanks
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
>  221f0ea1d 
>   
> security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
>  e9ed9bac6 
>   
> security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
>  f8fc7781f 
> 
> 
> Diff: https://reviews.apache.org/r/74381/diff/2/
> 
> 
> Testing
> ---
> 
> Tested that while resource lookup failed for resource, exception message 
> displayed properly.
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Dhaval Rajpara 

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

(Updated April 4, 2023, 7:38 a.m.)


Review request for ranger, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, 
Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.


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


Repository: ranger


Description
---

Resouce lookup exception message is not available in react UI

Steps to reproduce :
1. While creating policy enter any resouce name which is not available 

Actual : We are not getting any expception message  related to these resouce 
while resouce lookup 

Expected : Like Old ui user should get these expection message for resource 
lookup

Thanks


Diffs (updated)
-

  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
 221f0ea1d 
  
security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
 e9ed9bac6 
  
security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
 f8fc7781f 


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

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


Testing
---

Tested that while resource lookup failed for resource, exception message 
displayed properly.


Thanks,

Dhaval Rajpara

Re: Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Mugdha Varadkar 

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


Ship it!




Ship It!

- Mugdha Varadkar


On April 4, 2023, 7:19 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74381/
> ---
> 
> (Updated April 4, 2023, 7:19 a.m.)
> 
> 
> Review request for ranger, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, 
> Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4090
> https://issues.apache.org/jira/browse/RANGER-4090
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Resouce lookup exception message is not available in react UI
> 
> Steps to reproduce :
> 1. While creating policy enter any resouce name which is not available 
> 
> Actual : We are not getting any expception message  related to these resouce 
> while resouce lookup 
> 
> Expected : Like Old ui user should get these expection message for resource 
> lookup
> 
> Thanks
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
>  221f0ea1d11d67bffb71ec52139c97dfe6df9853 
>   
> security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
>  e9ed9bac6f56baf2d3440615b06d32bfb850d048 
>   
> security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
>  f8fc7781fed76dc77adfb532933c4b58beb4fd49 
> 
> 
> Diff: https://reviews.apache.org/r/74381/diff/1/
> 
> 
> Testing
> ---
> 
> Tested that while resource lookup failed for resource, exception message 
> displayed properly.
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Dhaval Rajpara 

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

(Updated April 4, 2023, 7:19 a.m.)


Review request for ranger, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, 
Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.


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


Repository: ranger


Description
---

Resouce lookup exception message is not available in react UI

Steps to reproduce :
1. While creating policy enter any resouce name which is not available 

Actual : We are not getting any expception message  related to these resouce 
while resouce lookup 

Expected : Like Old ui user should get these expection message for resource 
lookup

Thanks


Diffs
-

  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
 221f0ea1d11d67bffb71ec52139c97dfe6df9853 
  
security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
 e9ed9bac6f56baf2d3440615b06d32bfb850d048 
  
security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
 f8fc7781fed76dc77adfb532933c4b58beb4fd49 


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


Testing (updated)
---

Tested that while resource lookup failed for resource, exception message 
displayed properly.


Thanks,

Dhaval Rajpara

[jira] [Updated] (RANGER-4171) Updated time is same as created time even user group membership is updated xusers/users/userName

2023-04-04 Thread Anupam Rai (Jira) 


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

Anupam Rai updated RANGER-4171:
---
Description: 
Updated time is same as created time even user group membership is updated when 
queried from 'xusers/users/userName'

Steps to reproduce :
1. Create user through freeIPA or any other source and associate it with group1 
wait for user to sync in Ranger
2. Create new group on usersync Active node name as group2
3. Associate create user with created group on usersync Active node.

Verify user on xusers/users/userName
Request :
{code:java}
curl -s -L "https://***/xusers/users/userName/tester1234"; -H "Authorization: 
Basic **==" {code}
response :
{code:java}
{
    "id": 209,
    "createDate": "2023-04-03T06:40:15Z",
    "updateDate": "2023-04-03T06:40:15Z",
    "owner": "**",
    "updatedBy": "***",
    "name": "**",
    "password": "*",
    "description": "tester1234 - add from Unix box",
    "groupIdList": [
        279,
        278
    ],
    "groupNameList": [
        "testanu",
        "tester1234"
    ],
    "status": 1,
    "isVisible": 1,
    "userSource": 1,
    "userRoleList": [
        "ROLE_USER"
    ],
    "otherAttributes": 
"{\"sync_source\":\"Unix\",\"full_name\":\"tester1234\",\"original_name\":\"tester1234\"}",
    "syncSource": "Unix"
} {code}

  was:
Updated time is same as created time even user group membership is updated when 
queried from 'xusers/users/userName'

Steps to reproduce :
1. Create user through freeIPA or any other source and associate it with group1 
wait for user to sync in Ranger
2. Create new group on usersync Active node name as group2
3. Associate create user with created group on usersync Active node.

Verify user on xusers/users/userName
Request :
{code:java}
curl -s -L "https://***/xusers/users/userName/tester1234"; -H "Authorization: 
Basic aHJ0X3FhOlBhc3N3b3JkQDEyMw==" {code}
response :
{code:java}
{
    "id": 209,
    "createDate": "2023-04-03T06:40:15Z",
    "updateDate": "2023-04-03T06:40:15Z",
    "owner": "**",
    "updatedBy": "***",
    "name": "**",
    "password": "*",
    "description": "tester1234 - add from Unix box",
    "groupIdList": [
        279,
        278
    ],
    "groupNameList": [
        "testanu",
        "tester1234"
    ],
    "status": 1,
    "isVisible": 1,
    "userSource": 1,
    "userRoleList": [
        "ROLE_USER"
    ],
    "otherAttributes": 
"{\"sync_source\":\"Unix\",\"full_name\":\"tester1234\",\"original_name\":\"tester1234\"}",
    "syncSource": "Unix"
} {code}


> Updated time is same as created time even user group membership is updated 
> xusers/users/userName
> 
>
> Key: RANGER-4171
> URL: https://issues.apache.org/jira/browse/RANGER-4171
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger, usersync
>Reporter: Anupam Rai
>Priority: Major
>
> Updated time is same as created time even user group membership is updated 
> when queried from 'xusers/users/userName'
> Steps to reproduce :
> 1. Create user through freeIPA or any other source and associate it with 
> group1 wait for user to sync in Ranger
> 2. Create new group on usersync Active node name as group2
> 3. Associate create user with created group on usersync Active node.
> Verify user on xusers/users/userName
> Request :
> {code:java}
> curl -s -L "https://***/xusers/users/userName/tester1234"; -H "Authorization: 
> Basic **==" {code}
> response :
> {code:java}
> {
>     "id": 209,
>     "createDate": "2023-04-03T06:40:15Z",
>     "updateDate": "2023-04-03T06:40:15Z",
>     "owner": "**",
>     "updatedBy": "***",
>     "name": "**",
>     "password": "*",
>     "description": "tester1234 - add from Unix box",
>     "groupIdList": [
>         279,
>         278
>     ],
>     "groupNameList": [
>         "testanu",
>         "tester1234"
>     ],
>     "status": 1,
>     "isVisible": 1,
>     "userSource": 1,
>     "userRoleList": [
>         "ROLE_USER"
>     ],
>     "otherAttributes": 
> "{\"sync_source\":\"Unix\",\"full_name\":\"tester1234\",\"original_name\":\"tester1234\"}",
>     "syncSource": "Unix"
> } {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4171) Updated time is same as created time even user group membership is updated xusers/users/userName

2023-04-04 Thread Anupam Rai (Jira) 
Anupam Rai created RANGER-4171:
--

 Summary: Updated time is same as created time even user group 
membership is updated xusers/users/userName
 Key: RANGER-4171
 URL: https://issues.apache.org/jira/browse/RANGER-4171
 Project: Ranger
  Issue Type: Bug
  Components: Ranger, usersync
Reporter: Anupam Rai


Updated time is same as created time even user group membership is updated when 
queried from 'xusers/users/userName'

Steps to reproduce :
1. Create user through freeIPA or any other source and associate it with group1 
wait for user to sync in Ranger
2. Create new group on usersync Active node name as group2
3. Associate create user with created group on usersync Active node.

Verify user on xusers/users/userName
Request :
{code:java}
curl -s -L "https://***/xusers/users/userName/tester1234"; -H "Authorization: 
Basic aHJ0X3FhOlBhc3N3b3JkQDEyMw==" {code}
response :
{code:java}
{
    "id": 209,
    "createDate": "2023-04-03T06:40:15Z",
    "updateDate": "2023-04-03T06:40:15Z",
    "owner": "**",
    "updatedBy": "***",
    "name": "**",
    "password": "*",
    "description": "tester1234 - add from Unix box",
    "groupIdList": [
        279,
        278
    ],
    "groupNameList": [
        "testanu",
        "tester1234"
    ],
    "status": 1,
    "isVisible": 1,
    "userSource": 1,
    "userRoleList": [
        "ROLE_USER"
    ],
    "otherAttributes": 
"{\"sync_source\":\"Unix\",\"full_name\":\"tester1234\",\"original_name\":\"tester1234\"}",
    "syncSource": "Unix"
} {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74368: RANGER-4149 : Create common module for HA support

2023-04-04 Thread Dineshkumar Yadav 

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

(Updated April 4, 2023, 7:07 a.m.)


Review request for ranger, Ankita Sinha, Jayendra Parab, Kishor Gollapalliwar, 
Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, 
Sailaja Polavarapu, and Velmurugan Periasamy.


Repository: ranger


Description
---

This patch is part of RANGER-4148.  
This common module act as common jar and will help other component to implement 
HA.


Diffs
-

  pom.xml 3a039565d 
  ranger-common-ha/pom.xml PRE-CREATION 
  ranger-common-ha/src/main/java/org/apache/ranger/RangerHAInitializer.java 
PRE-CREATION 
  
ranger-common-ha/src/main/java/org/apache/ranger/ha/ActiveInstanceElectorService.java
 PRE-CREATION 
  ranger-common-ha/src/main/java/org/apache/ranger/ha/ActiveInstanceState.java 
PRE-CREATION 
  
ranger-common-ha/src/main/java/org/apache/ranger/ha/ActiveStateChangeHandler.java
 PRE-CREATION 
  ranger-common-ha/src/main/java/org/apache/ranger/ha/CuratorFactory.java 
PRE-CREATION 
  ranger-common-ha/src/main/java/org/apache/ranger/ha/HAConfiguration.java 
PRE-CREATION 
  
ranger-common-ha/src/main/java/org/apache/ranger/ha/RangerServiceServerIdSelector.java
 PRE-CREATION 
  ranger-common-ha/src/main/java/org/apache/ranger/ha/ServiceState.java 
PRE-CREATION 
  
ranger-common-ha/src/main/java/org/apache/ranger/ha/ZookeeperSecurityProperties.java
 PRE-CREATION 
  ranger-common-ha/src/main/java/org/apache/ranger/ha/annotation/HAService.java 
PRE-CREATION 
  
ranger-common-ha/src/main/java/org/apache/ranger/ha/service/HARangerService.java
 PRE-CREATION 
  
ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java 
PRE-CREATION 
  
ranger-common-ha/src/test/java/org/apache/ranger/ha/service/TestRangerServiceServerIdSelector.java
 PRE-CREATION 
  ranger-common-ha/src/test/resources/log4j.xml PRE-CREATION 
  ranger-common-ha/src/test/resources/ranger-tagsync-site.xml PRE-CREATION 


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


Testing
---


Thanks,

Dineshkumar Yadav

Review Request 74381: RANGER-4090 : Resouce lookup exception message is not available in react UI.

2023-04-04 Thread Dhaval Rajpara 

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

Review request for ranger, Dhaval Rajpara, Madhan Neethiraj, Mehul Parikh, 
Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.


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


Repository: ranger


Description
---

Resouce lookup exception message is not available in react UI

Steps to reproduce :
1. While creating policy enter any resouce name which is not available 

Actual : We are not getting any expception message  related to these resouce 
while resouce lookup 

Expected : Like Old ui user should get these expection message for resource 
lookup

Thanks


Diffs
-

  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
 221f0ea1d11d67bffb71ec52139c97dfe6df9853 
  
security-admin/src/main/webapp/react-webapp/src/views/Resources/ResourceComp.jsx
 e9ed9bac6f56baf2d3440615b06d32bfb850d048 
  
security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
 f8fc7781fed76dc77adfb532933c4b58beb4fd49 


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


Testing
---

Tested


Thanks,

Dhaval Rajpara

[jira] [Updated] (RANGER-4090) Resouce lookup exception message is not available in react UI

2023-04-04 Thread Dhaval Rajpara (Jira) 


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

Dhaval Rajpara updated RANGER-4090:
---
Attachment: 0002-RANGER-4090.patch

> Resouce lookup exception message is not available in react UI
> -
>
> Key: RANGER-4090
> URL: https://issues.apache.org/jira/browse/RANGER-4090
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Dhaval Rajpara
>Priority: Major
>  Labels: ranger-react
> Attachments: 0001-RANGER-4090.patch, 0002-RANGER-4090.patch
>
>
> Resouce lookup exception message is not available in react UI
> Steps to reproduce :
> 1. While creating policy enter any resouce name which is not available 
> Actual : We are not getting any expception message  related to these resouce 
> while resouce lookup 
> Expected : Like Old ui user should get these expection message for resource 
> lookup
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)