[
https://issues.apache.org/jira/browse/RANGER-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607784#comment-17607784
]
Pradeep Agrawal edited comment on RANGER-3852 at 9/21/22 2:41 PM
[
https://issues.apache.org/jira/browse/RANGER-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3852.
-
Resolution: Fixed
https://github.com/apache/ranger/commit
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74090/#review224694
---
Ship it!
Ship It!
- Pradeep Agrawal
On Aug. 17, 2022, 4:54
> On Aug. 19, 2022, 10:16 a.m., Pradeep Agrawal wrote:
> > Please fix the rat text/license issue.
> >
> > 4 Unknown Licenses
> >
> > ***
> >
> > Unapproved licenses:
> >
> > ranger-tools/src/main/python
[
https://issues.apache.org/jira/browse/RANGER-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3852:
Attachment: 0001-RANGER-3852-performance-and-scalability-analyzer-too.patch
> Performa
[
https://issues.apache.org/jira/browse/RANGER-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3852:
Fix Version/s: 3.0.0
2.4.0
> Performance and scalability analyzer t
[
https://issues.apache.org/jira/browse/RANGER-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3680.
-
Fix Version/s: 3.0.0
2.4.0
Resolution: Duplicate
> my
[
https://issues.apache.org/jira/browse/RANGER-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3719.
-
Fix Version/s: 3.0.0
2.4.0
Resolution: Duplicate
>
[
https://issues.apache.org/jira/browse/RANGER-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3394.
-
Fix Version/s: 3.0.0
2.4.0
Resolution: Duplicate
> Too m
[
https://issues.apache.org/jira/browse/RANGER-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607560#comment-17607560
]
Pradeep Agrawal commented on RANGER-3914:
-
master branch commit link:
[https://github.com
, Madhan Neethiraj, Nikhil P, Pradeep
Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan
Periasamy.
Changes
---
Tested the patch for mssql db flavor.
Bugs: RANGER-3914
https://issues.apache.org/jira/browse/RANGER-3914
Repository: ranger
Description
------
On Sept. 16, 2022, 6:12 a.m., Pradeep Agrawal wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74122/
> --
, Madhan Neethiraj, Nikhil P, Pradeep
Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan
Periasamy.
Changes
---
Addressed review comments and updated the patch.
Bugs: RANGER-3914
https://issues.apache.org/jira/browse/RANGER-3914
Repository: ranger
t be having any issue with that).
- Pradeep
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74122/#review224674
-------
On Sep
/
Testing
---
Tested Ranger install and upgrade with this patch which was failing earlier.
Thanks,
Pradeep Agrawal
Pradeep Agrawal created RANGER-3914:
---
Summary: Change sync_source column's datatype from varchar to text
Key: RANGER-3914
URL: https://issues.apache.org/jira/browse/RANGER-3914
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3719:
---
Assignee: Pradeep Agrawal
> Can not create mysql table with charset utf8
Pradeep Agrawal created RANGER-3911:
---
Summary: NPE fix in RangerDefaultPolicyEvaluator
Key: RANGER-3911
URL: https://issues.apache.org/jira/browse/RANGER-3911
Project: Ranger
Issue Type
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74094/#review224639
---
Ship it!
Ship It!
- Pradeep Agrawal
On Aug. 23, 2022, 8:31
[
https://issues.apache.org/jira/browse/RANGER-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583347#comment-17583347
]
Pradeep Agrawal commented on RANGER-3837:
-
master branch commit link :
[https://github.com
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74091/#review224633
---
Ship it!
Ship It!
- Pradeep Agrawal
On Aug. 19, 2022, 7:47
Hi Jay,
Please propose a contribution (doc or patch) first in the respective Apache
ranger jira. After the first contribution account will be added for the
contributor role.
If you have already raised any jira, please send the link.
Regards,
Pradeep
-tools/src/main/python/ranger_performance_tool/ranger_perf_assets/default_secondary_config.json
- Pradeep Agrawal
On Aug. 17, 2022, 4:54 a.m., Fateh Singh wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit
ecause both are executing in a
different transaction.
- Pradeep
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74087/#review224624
----------
ithout this change when policies are getting updated then i am getting
error "invalid resource-type "admin". Its because both are executing in a
different transaction.
- Pradeep Agrawal
On Aug. 13, 2022, 9:27 p.m.,
script.
without the patch it was taking 3 hours, after the patch its taking 3 minutes
only.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3857:
---
Assignee: Pradeep Agrawal (was: Abhishek Kumar)
> Ranger java patch J10055 ta
Pradeep Agrawal created RANGER-3857:
---
Summary: Ranger java patch J10055 takes time
Key: RANGER-3857
URL: https://issues.apache.org/jira/browse/RANGER-3857
Project: Ranger
Issue Type: Bug
Pradeep Agrawal created RANGER-3853:
---
Summary: Ranger java patch J10054 take time
Key: RANGER-3853
URL: https://issues.apache.org/jira/browse/RANGER-3853
Project: Ranger
Issue Type: Bug
[
https://issues.apache.org/jira/browse/RANGER-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3824:
Fix Version/s: 2.4.0
> [Ranger] : /service/tags/resources error message is not pro
d is causing PMD Error.
- Pradeep Agrawal
On Aug. 9, 2022, 2:02 a.m., Fateh Singh wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://re
such as
'mockCreatePolicyUnconditionally_1(RangerPolicy)'..
- Pradeep Agrawal
On Aug. 3, 2022, 8:53 p.m., Fateh Singh wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache
[
https://issues.apache.org/jira/browse/RANGER-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574585#comment-17574585
]
Pradeep Agrawal commented on RANGER-3846:
-
Commit link:
master branch :
[https://github.com
on
x_policy table.
started ranger and login to ranger-admin and duplicate policies were removed.
Thanks,
Pradeep Agrawal
Pradeep Agrawal created RANGER-3846:
---
Summary: Ranger DB patch 058 failing when multiple policies having
same resourceSignature
Key: RANGER-3846
URL: https://issues.apache.org/jira/browse/RANGER-3846
.java
Lines 419 (patched)
<https://reviews.apache.org/r/74067/#comment313382>
Change the API to :
/api/services/policyVersion/{serviceName}
or
/api/services/service/policyVersion/{serviceName}
- Pradeep Agrawal
On July 22, 2022, 3:58 p.m., Fateh Singh
[
https://issues.apache.org/jira/browse/RANGER-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3829.
-
Fix Version/s: 3.0.0
Resolution: Fixed
https://github.com/apache/ranger/commit
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74058/#review224580
---
Ship it!
Ship It!
- Pradeep Agrawal
On July 19, 2022, 1:51
[
https://issues.apache.org/jira/browse/RANGER-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3813.
-
Fix Version/s: 3.0.0
Resolution: Fixed
Commit link :
https://github.com/apache
[
https://issues.apache.org/jira/browse/RANGER-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3824:
Attachment: 0001-RANGER-3824-Tag-resource-API-error-message-is-not-pr.patch
> [Ran
08b1e45fd
Diff: https://reviews.apache.org/r/74059/diff/1/
Testing
---
Installed ranger admin with the patch and curl request to API is able to update
the resource object when updateIfexists is set to true. It throws an error when
object exists and updateIfexists is set to false.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3824:
---
Assignee: Pradeep Agrawal
> [Ranger] : /service/tags/resources error mess
was succeeded.
7) logged in from admin user and tried to change password of testuser3 and
testuser4 and it was succeeded. logout and tried login for testuser3 with
updated password which was succeeded.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3825:
Attachment: 0001-RANGER-3825-Ranger-internal-user-is-unable-to-change.patch
> Ran
[
https://issues.apache.org/jira/browse/RANGER-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3825:
Priority: Critical (was: Major)
> Ranger internal user is unable to change his passw
Pradeep Agrawal created RANGER-3825:
---
Summary: Ranger internal user is unable to change his password
after the upgrade.
Key: RANGER-3825
URL: https://issues.apache.org/jira/browse/RANGER-3825
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74030/#review224555
---
Ship it!
Ship It!
- Pradeep Agrawal
On June 17, 2022, 3:37
ser/randomuser;
Response:
{"statusCode":1,"msgDesc":"randomuser is Not
Found","messageList":[{"name":"DATA_NOT_FOUND","rbKey":"xa.error.data_not_found","message":"Data
not found"}]}
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3807:
Attachment: 0001-RANGER-3807-getUserRoles-API-gives-200-for-non-exist.patch
Pradeep Agrawal created RANGER-3807:
---
Summary: getUserRoles API gives 200 for non existing user passed
to this API
Key: RANGER-3807
URL: https://issues.apache.org/jira/browse/RANGER-3807
Project
org/apache/ranger/service/XGroupUserService.java
9345e8180
Diff: https://reviews.apache.org/r/74039/diff/1/
Testing
---
With the patch issue is not reproducing when i have set the
auto_increment_increment to 3 in mysql server env.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3806:
Attachment: 0001-RANGER-3806-Group-s-users-mapping-entry-failing-when.patch
> Grou
[
https://issues.apache.org/jira/browse/RANGER-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3806:
Summary: Group's users mapping entry failing whenever primary key
auto-increment
Pradeep Agrawal created RANGER-3806:
---
Summary: group's users mapping entry failing whenever primary key
auto-increment is not set to 1 in db
Key: RANGER-3806
URL: https://issues.apache.org/jira/browse/RANGER
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73794/#review224526
---
Ship it!
Ship It!
- Pradeep Agrawal
On April 20, 2022, 6:02
[
https://issues.apache.org/jira/browse/RANGER-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3797.
-
Fix Version/s: 3.0.0
Resolution: Fixed
commit link :
https://github.com/apache
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74031/#review224525
---
Ship it!
Ship It!
- Pradeep Agrawal
On June 21, 2022, 10:45
[
https://issues.apache.org/jira/browse/RANGER-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556740#comment-17556740
]
Pradeep Agrawal commented on RANGER-2742:
-
This issue was caused by RANGER-2713 commit, which i
[
https://issues.apache.org/jira/browse/RANGER-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3799:
---
Assignee: Pradeep Agrawal
> Move off jersey
please find if there will be any impact of this change.
- Pradeep Agrawal
On June 17, 2022, 11:41 a.m., Pradeep Agrawal wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.
failure.
5) restart ranger-admin and check the kafka service policies.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3795:
Attachment: 0001-RANGER-3795-Fix-java-patch-J10033-and-J10046-failure.patch
> Fix j
[
https://issues.apache.org/jira/browse/RANGER-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3795:
Summary: Fix java patch J10033 and J10046 failure (was: Fix
Pradeep Agrawal created RANGER-3795:
---
Summary: Fix PatchForMigratingOldRegimePolicyJson_J10046 failure
Key: RANGER-3795
URL: https://issues.apache.org/jira/browse/RANGER-3795
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3782:
---
Assignee: Mateen Mansoori
> RANGER - Upgrade spring-security version to 5.
043e2c2e9
Diff: https://reviews.apache.org/r/74024/diff/1/
Testing
---
Build successful - mvn clean install
Ranger started successfully and able to CRUD on service/policy/users/groups.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3791:
Attachment: 0001-RANGER-3791-Upgrade-json-smart-gson-and-jersey-clien.patch
> Upgr
[
https://issues.apache.org/jira/browse/RANGER-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3791:
Description:
Upgrade jersey-client to 2.35
Upgrade gson to 2.9.0
Upgrade json-smart
[
https://issues.apache.org/jira/browse/RANGER-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3791:
Summary: Upgrade json-smart, gson and jersey-client libraries version
(was: Upgrade json
[
https://issues.apache.org/jira/browse/RANGER-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3791:
Summary: Upgrade json-smart, gson libraries version (was: Upgrade
json-smart, gson
[
https://issues.apache.org/jira/browse/RANGER-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3791:
Description:
Upgrade gson to 2.9.0
Upgrade json-smart to 2.4.7
was:
Upgrade jersey
Pradeep Agrawal created RANGER-3791:
---
Summary: Upgrade json-smart, gson and jersey libraries version
Key: RANGER-3791
URL: https://issues.apache.org/jira/browse/RANGER-3791
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3785:
---
Assignee: Pradeep Agrawal
> CVSS-V3 >= 10 vulnerability in Apache Ranger
[
https://issues.apache.org/jira/browse/RANGER-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553418#comment-17553418
]
Pradeep Agrawal commented on RANGER-3785:
-
[~anurag2898] : Either you can upgrade to latest
[
https://issues.apache.org/jira/browse/RANGER-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3784:
---
Assignee: Pradeep Agrawal (was: Bhavik Patel)
> CLONE - Upgrade netty to 4.1
Pradeep Agrawal created RANGER-3784:
---
Summary: CLONE - Upgrade netty to 4.1.77-final
Key: RANGER-3784
URL: https://issues.apache.org/jira/browse/RANGER-3784
Project: Ranger
Issue Type: Bug
[
https://issues.apache.org/jira/browse/RANGER-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3784:
Description: Upgrade netty to 4.1.77-final (was: Upgrade netty to
4.1.76-final)
> CL
[
https://issues.apache.org/jira/browse/RANGER-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3752.
-
Resolution: Fixed
[~kirbyzhou] : create another Jira and attach your proposed patch
nks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3780:
Fix Version/s: (was: 2.3.0)
> Ranger - Upgrade tomcat to 8.5
[
https://issues.apache.org/jira/browse/RANGER-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3780:
---
Assignee: Pradeep Agrawal (was: Mateen Mansoori)
> Ranger - Upgrade tom
[
https://issues.apache.org/jira/browse/RANGER-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3780:
Description: This task is to upgrade tomcat version to 8.5.79 (was:
Currently ranger
Pradeep Agrawal created RANGER-3780:
---
Summary: Ranger - Upgrade tomcat to 8.5.79
Key: RANGER-3780
URL: https://issues.apache.org/jira/browse/RANGER-3780
Project: Ranger
Issue Type: Task
Thank-you Ramesh for putting the Apache Ranger 2.3.0 rc0.
+1 for the Apache Ranger 2.3.0 rc0.
Verified the build of Ranger from the source tar succeeded without any
issues.
Verified the upgrade from ranger 2.1 to 2.3 and existence of
policies/users/groups after the upgrade
Tested the crud
> On May 17, 2022, 2:35 p.m., Pradeep Agrawal wrote:
> > Ship It!
Able to build successfully along with
https://issues.apache.org/jira/secure/attachment/13043369/0001-RANGER-3182-Rename-Prestosql-to-Trino-ranger-2.3.patch
on 2.3 branch.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73984/#review224451
---
Ship it!
Ship It!
- Pradeep Agrawal
On May 17, 2022, 6:10
[
https://issues.apache.org/jira/browse/RANGER-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-3669.
-
Resolution: Fixed
master branch commit link :
[https://github.com/apache/ranger/commit
[
https://issues.apache.org/jira/browse/RANGER-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538113#comment-17538113
]
Pradeep Agrawal commented on RANGER-3669:
-
have reverted this commit as wrong patch
[
https://issues.apache.org/jira/browse/RANGER-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reopened RANGER-3669:
-
> Connection to DB fails for MySQL version above
[
https://issues.apache.org/jira/browse/RANGER-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535869#comment-17535869
]
Pradeep Agrawal commented on RANGER-3752:
-
[~kirbyzhou] : I don't understand what are you saying
an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73981/#review224432
---
On May 10, 2022, 7:31 p.m., Pradeep Agrawal wrote:
>
> ---
t;delegateAdmin":true}],"dataMaskPolicyItems":[],"rowFilterPolicyItems":[],"serviceType":"hive","options":{},"validitySchedules":[],"policyLabels":[],"zoneName":"","isDenyAllElse":false}'
2. make a curl request to get the policy and compare the json. json content
will be having the duplicate entries of access permissions as provided in the
create policy request.
**Proposed solution:**
Option-1: Since policy validation is done before policy creation, hence during
validation phase we can filter out duplicate access permissions.
Option-2: Add a validation to detect duplicate entries of access-permissions
and if there are any duplicate entries then fail the policy request.
I have provided the patch with option-1 mentioned above.
Diffs (updated)
-
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerPolicyValidator.java
fb6556b59
Diff: https://reviews.apache.org/r/73981/diff/2/
Changes: https://reviews.apache.org/r/73981/diff/1-2/
Testing
---
With patch tested the create policy request with duplicate access-permissions
entries, policy was created successfully and get request is not having
duplicate access-permissions entries.
With patch tested the update policy request with duplicate access-permissions
entries, policy was updated successfully and get request is not having
duplicate access-permissions entries.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534318#comment-17534318
]
Pradeep Agrawal commented on RANGER-3182:
-
Build is failing for me too with the below command
licyItems":[],"serviceType":"hive","options":{},"validitySchedules":[],"policyLabels":[],"zoneName":"","isDenyAllElse":false}'
2. make a curl request to get the policy and compare the json. json content
will be having the duplicate entries of access permissions as provided in the
create policy request.
**Proposed solution:**
Option-1: Since policy validation is done before policy creation, hence during
validation phase we can filter out duplicate access permissions.
Option-2: Add a validation to detect duplicate entries of access-permissions
and if there are any duplicate entries then fail the policy request.
I have provided the patch with option-1 mentioned above.
Diffs
-
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerPolicyValidator.java
fb6556b59
Diff: https://reviews.apache.org/r/73981/diff/1/
Testing
---
With patch tested the create policy request with duplicate access-permissions
entries, policy was created successfully and get request is not having
duplicate access-permissions entries.
With patch tested the update policy request with duplicate access-permissions
entries, policy was updated successfully and get request is not having
duplicate access-permissions entries.
Thanks,
Pradeep Agrawal
[
https://issues.apache.org/jira/browse/RANGER-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3752:
Attachment: 0001-RANGER-3752-Restrict-duplicate-access-types-entries-.patch
> Restr
Pradeep Agrawal created RANGER-3752:
---
Summary: Restrict duplicate access types entries in policy creation
Key: RANGER-3752
URL: https://issues.apache.org/jira/browse/RANGER-3752
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3139:
---
Assignee: Pradeep Agrawal
> Create service SQLException: Lock wait time
[
https://issues.apache.org/jira/browse/RANGER-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3393:
---
Assignee: Pradeep Agrawal
> Stop using deprecated mysql driver cl
[
https://issues.apache.org/jira/browse/RANGER-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3680:
---
Assignee: Pradeep Agrawal
> mysql ErrorCode:1118 when Importing DB sch
[
https://issues.apache.org/jira/browse/RANGER-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-3394:
---
Assignee: Pradeep Agrawal
> Too much `varchar(4000)` causes table to exceed
301 - 400 of 2225 matches
Mail list logo
