Re: Review Request 74923: RANGER-4730: Migrate Ranger modules to junit5 - phase 2

2024-03-18 Thread Dineshkumar Yadav 

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


Ship it!




Ship It!

- Dineshkumar Yadav


On March 4, 2024, 6:05 a.m., Kishor Gollapalliwar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74923/
> ---
> 
> (Updated March 4, 2024, 6:05 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Abhay Kulkarni, 
> Madhan Neethiraj, Ramesh Mani, Sailaja Polavarapu, Vikas Kumar, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4730
> https://issues.apache.org/jira/browse/RANGER-4730
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> This sub-task is responsible to migrate following maven sub-modules to junit5.
>  1. ranger-kms
>  2. ranger-kms-plugin
>  3. ranger-kms-plugin-shim
> 
> 
> Diffs
> -
> 
>   kms/pom.xml 2739bb81a 
>   kms/src/test/java/org/apache/hadoop/crypto/key/kms/TestRangerKeyStore.java 
> bcdf2e337 
>   
> kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/RangerKeyStoreProviderTest.java
>  5fde0afc8 
>   
> kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/RangerMasterKeyTest.java
>  f420322ca 
>   kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMSACLs.java 
> 80564d466 
>   kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMSAudit.java 
> ec0bae877 
>   
> kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMSAuthenticationFilter.java
>  e8ca7b714 
>   
> kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKeyAuthorizationKeyProvider.java
>  d7988e7b8 
>   kms/src/test/java/org/apache/ranger/kms/metrics/TestKMSMetricsWrapper.java 
> 209251026 
>   plugin-kms/pom.xml 42e8ec25d 
>   
> plugin-kms/src/test/java/org/apache/ranger/authorization/kms/authorizer/RangerKmsAuthorizerTest.java
>  4baec7ba8 
> 
> 
> Diff: https://reviews.apache.org/r/74923/diff/1/
> 
> 
> Testing
> ---
> 
> mvn clean compile package install
> 
> 
> Thanks,
> 
> Kishor Gollapalliwar
> 
>

Re: Review Request 74926: RANGER-4076: Support Java 17 for build and runtime

2024-03-18 Thread Rakesh Gupta 


> On March 6, 2024, 3:28 p.m., bhavik patel wrote:
> > After starting the server have checked the catalina and ranger admin login 
> > file?

After starting the server, I checked the Catalina error log, which is being 
handled by Jira ticket RANGER-4744. However, the Ranger admin log does not 
appear, and this will also be handled by Jira ticket RANGER-4743.


- Rakesh


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


On March 5, 2024, 7:10 a.m., Rakesh Gupta wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74926/
> ---
> 
> (Updated March 5, 2024, 7:10 a.m.)
> 
> 
> Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
> Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, 
> sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4076
> https://issues.apache.org/jira/browse/RANGER-4076
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Currently only Java 8 and 11 are supported.  Java 17 is a major LTS version 
> of Java and adding support would modernize our Java version support.
> 
> This patch enables manual and Docker-based build of Apache Ranger. It ensures 
> compatibility with Java 8, Java 11, and Java 17 for both build and runtime 
> environments.
> (I encountered a TestCase Failure in the KnoxRangerTest class, so currently I 
> had excluded that class from jdk17 build)
> 
> 
> Diffs
> -
> 
>   agents-common/pom.xml 12e093f78 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/GraalScriptEngineCreator.java
>  512d8d3ca 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/NashornScriptEngineCreator.java
>  db620df92 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ScriptEngineUtil.java
>  8d76c1d81 
>   dev-support/ranger-docker/.env 60bc4a9f2 
>   dev-support/ranger-docker/Dockerfile.ranger-build 9a192f152 
>   dev-support/ranger-docker/docker-compose.ranger-build.yml 3dd4a4a06 
>   distro/src/main/assembly/admin-web.xml 245d9ca09 
>   docs/src/site/resources/index.js bb876f28d 
>   hdfs-agent/pom.xml dece8f46f 
>   kms/pom.xml 2739bb81a 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java 
> 7188b19b2 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java 
> b6fc32950 
>   plugin-nestedstructure/pom.xml 0e208f99c 
>   
> plugin-nestedstructure/src/main/java/org/apache/ranger/authorization/nestedstructure/authorizer/RecordFilterJavaScript.java
>  77767767c 
>   
> plugin-nestedstructure/src/test/java/org/apache/ranger/authorization/nestedstructure/authorizer/TestRecordFilterJavaScript.java
>  9cb161b8d 
>   pom.xml cec2390f2 
>   ranger-tools/pom.xml cac8d7ba3 
>   
> ranger-tools/src/test/java/org/apache/ranger/policyengine/RangerPolicyEnginePerformanceTest.java
>  187d20227 
>   security-admin/pom.xml fc59287d0 
> 
> 
> Diff: https://reviews.apache.org/r/74926/diff/1/
> 
> 
> Testing
> ---
> 
> This patch has been successfully tested and verified with Java versions 8, 
> 11, and 17. The verification process included both manual and Docker setup. 
> Now we are able to build and run on same jdk.
> 
> 
> Thanks,
> 
> Rakesh Gupta
> 
>

Re: [PR] RANGER-4511: Enable Parallel Compilation for Multiple Modules in Ranger [ranger]

2024-03-18 Thread via GitHub 


kumaab commented on PR #289:
URL: https://github.com/apache/ranger/pull/289#issuecomment-2005327035

   + 1 
   The changes look good, this is helpful in reducing the time taken for mvn 
builds significantly. 


-- 
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-4743) [JDK 11]: Fix ranger admin logging

2024-03-18 Thread Abhishek Kumar (Jira) 


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

Abhishek Kumar commented on RANGER-4743:


Thanks [~rakeshgupta264], I'll try this out. 

> [JDK 11]: Fix ranger admin logging 
> ---
>
> Key: RANGER-4743
> URL: https://issues.apache.org/jira/browse/RANGER-4743
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Attachments: 0001-RANGER-4743.patch
>
>
> Currently, the ranger-admin logs do not appear when built and run with jdk 11.
> Logback and slf4j versions need to be upgraded to fix the above issue.
> More info: [https://logback.qos.ch/download.html] 
> CC: [~rmani]



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

[jira] [Created] (RANGER-4752) Enable JDK 11 builds on GitHub PRs and merges to master

2024-03-18 Thread Abhishek Kumar (Jira) 
Abhishek Kumar created RANGER-4752:
--

 Summary: Enable JDK 11 builds on GitHub PRs and merges to master
 Key: RANGER-4752
 URL: https://issues.apache.org/jira/browse/RANGER-4752
 Project: Ranger
  Issue Type: Task
  Components: Ranger
Reporter: Abhishek Kumar
Assignee: Abhishek Kumar


For modules which have a compile time requirement of JDK 11(for eg: trino), 
this Jira tracks the work for enabling jdk11 maven build whenever there is a 
code change raised via GitHub PRs or merges to master occur.



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

[jira] [Created] (RANGER-4751) Enable docker builds for PRs and merges to master

2024-03-18 Thread Abhishek Kumar (Jira) 
Abhishek Kumar created RANGER-4751:
--

 Summary: Enable docker builds for PRs and merges to master
 Key: RANGER-4751
 URL: https://issues.apache.org/jira/browse/RANGER-4751
 Project: Ranger
  Issue Type: Task
  Components: Ranger
Affects Versions: 2.4.0
Reporter: Abhishek Kumar
Assignee: Abhishek Kumar


Currently, maven build with tests are part of GitHub PRs and merges to master. 
This Jira tracks an additional job to build all existing docker images whenever 
there is a code change or merge.



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

Re: Review Request 74941: RANGER-4749: Tag api to get serviceResource by resource. Getting list of associated tags in resources/paginated api's response.

2024-03-18 Thread Madhan Neethiraj 

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




agents-common/src/main/java/org/apache/ranger/plugin/model/RangerServiceResourceWithTags.java
Lines 39 (patched)


- I suggest changing datatype for associatedTags from List to 
List
- I suggest removing resourceSignature as this is not necessary in the 
model class. This field is necessary only in entity class
- any specific usecase for additionalInfo field?



agents-common/src/main/java/org/apache/ranger/plugin/store/TagStore.java
Line 105 (original), 105 (patched)


Instead of updating the existing method, consider introducing a new method: 
getPaginatedServiceResourcesWithTags()



security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java
Lines 375 (patched)


isMultiValue will be true here, given the if at #372. Please review and 
remove the else clause at #379.



security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java
Lines 528 (patched)


isMultiValue will be true here, given the if at #525. Please review and 
remove the else clause at #532.



security-admin/src/main/java/org/apache/ranger/rest/TagREST.java
Lines 1022 (patched)


POST for getServiceResource() doesn't seem right. I suggest changing this 
to GET and get the resourceElements via query params - like: 
service/hive/resource?resource:database=db1&resource:table=tbl1&resource:column=col1

Note that isExcludes is always false in RangerServiceResource, and 
isRecursive is always true for resources that support recusion.


- Madhan Neethiraj


On March 18, 2024, 2:23 p.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74941/
> ---
> 
> (Updated March 18, 2024, 2:23 p.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4749
> https://issues.apache.org/jira/browse/RANGER-4749
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Created new tag api which will get the service resource by comparing the 
> resouse signature of the resource from request. (POST - 
> service/tags/resource/service/{serviceName}/resource)
> Added list of tagNames to the resource/paginated api which will return all 
> the tagNames which are associated with the resource.
> Added freetext search on resource, and multiple search of tagNames in 
> service/tags/resources/paginated api - 
> 1 - 
> service/tags/resources/paginated?tagServiceName=hive&resourceElements=Cust_
> 2 - 
> service/tags/resources/paginated?tagServiceName=hive&tagNames=SSN&tagNames=PII_NAME
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerServiceResourceWithTags.java
>  PRE-CREATION 
>   agents-common/src/main/java/org/apache/ranger/plugin/store/TagStore.java 
> f9f80c9ac 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/JsonUtilsV2.java 
> ca61131dd 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> b0fad0aea 
>   security-admin/src/main/java/org/apache/ranger/biz/TagDBStore.java 
> a472fe131 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> c816ad229 
>   security-admin/src/main/java/org/apache/ranger/rest/TagREST.java 09d771565 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceWithTagsService.java
>  PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceWithTagsServiceBase.java
>  PRE-CREATION 
>   security-admin/src/test/java/org/apache/ranger/biz/TestTagDBStore.java 
> d6ebbc54d 
>   security-admin/src/test/java/org/apache/ranger/rest/TestTagREST.java 
> 98d87bc0a 
> 
> 
> Diff: https://reviews.apache.org/r/74941/diff/1/
> 
> 
> Testing
> ---
> 
> Validated POST - service/tags/resource/service/{serviceName}/resource with 
> postive and negative case.
> Validated response of service/tags/resources/paginated api 
> Sample response
> {
> "startIndex": 0,
> "pageSize": 5,
> "totalCount": 1,
> "resultSize": 1,
> "sortType": "asc",
> "sortBy": "resourceId",
> "queryTimeMS": 1710771145888,
> "list": [
> {
> "id": 4,
> "guid": "8f18d7b3-f885-4687-9438-ededdf340b18",
> "isEnabled": true,
> "createdBy": "Admin",
> "updatedBy": "Admin",
> "cr

[jira] [Updated] (RANGER-4749) Tag: Create an api to check if a resource is already available in database by resource input. And send tag list along with the resource list in response of GET /service/

2024-03-18 Thread Anand Nadar (Jira) 


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

Anand Nadar updated RANGER-4749:

Attachment: RANGER-4749.patch

> Tag: Create an api to check if a resource is already available in database by 
> resource input. And send tag list along with the resource list in response of 
> GET /service/tags/resources/paginated API
> -
>
> Key: RANGER-4749
> URL: https://issues.apache.org/jira/browse/RANGER-4749
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Anand Nadar
>Priority: Major
> Attachments: RANGER-4749.patch
>
>
> *1. Need an api to get the resource by resource if it exists in database.*
> Case:
> Suppose there already exists below tag and resource association.
> PII_NAME tag is associated with (database:HR-DB, table:EMPLOYEE, column:NAME)
> Now we dont know about the above resource already existing, so we are now 
> trying to create a new tag resource association as below
> PII_EMP_NAME associated with (database:HR-DB, table:EMPLOYEE, column:NAME)
> This is done using PUT /service/tags/importservicetags -> op: add_or_update
> So this will result in the deletion of PII_NAME association with the 
> resource,  and creation of PII_EMP_NAME tag associated with the resource.
> So if we have this GET service/tags/resource/service/\{serviceName}/resource 
> api which will have the payload as
> {code:java}
> {
>"database": {
>"values": [
>"HR-DB"
>],
>"isRecursive": true
>},
>"table": {
>"values": [
>"EMPLOYEE"
>],
>"isRecursive": true
>},
>"column": {
>"values": [
>"NAME"
>],
>"isRecursive": true
>}
> } {code}
> we can check if this resource already exists or not.
> If the resource exists, we can get all the tags associated with that 
> resource(in our case PII_NAME), and include the new tag PII_EMP_NAME as well 
> and send this in 
> PUT /service/tags/importservicetags -> op: add_or_update
> then both PII_NAME and PII_EMP_NAME will be associated with the resource.
> *2. Need the list of associated tag names for a resource as well in  
> /service/tags/resources/paginated api.*
> Currently we are not returning the list of tags associated in the response.
> This will get the service resources with all its associated tags in a single 
> api which is also paginated.
> Free text search on the resource, and multiple tag-name search



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

Review Request 74941: RANGER-4749: Tag api to get serviceResource by resource. Getting list of associated tags in resources/paginated api's response.

2024-03-18 Thread Anand Nadar 

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

Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika Kachhadiya, 
Siddhesh Phatak, and Subhrat Chaudhary.


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


Repository: ranger


Description
---

Created new tag api which will get the service resource by comparing the 
resouse signature of the resource from request. (POST - 
service/tags/resource/service/{serviceName}/resource)
Added list of tagNames to the resource/paginated api which will return all the 
tagNames which are associated with the resource.
Added freetext search on resource, and multiple search of tagNames in 
service/tags/resources/paginated api - 
1 - service/tags/resources/paginated?tagServiceName=hive&resourceElements=Cust_
2 - 
service/tags/resources/paginated?tagServiceName=hive&tagNames=SSN&tagNames=PII_NAME


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerServiceResourceWithTags.java
 PRE-CREATION 
  agents-common/src/main/java/org/apache/ranger/plugin/store/TagStore.java 
f9f80c9ac 
  agents-common/src/main/java/org/apache/ranger/plugin/util/JsonUtilsV2.java 
ca61131dd 
  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
b0fad0aea 
  security-admin/src/main/java/org/apache/ranger/biz/TagDBStore.java a472fe131 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
c816ad229 
  security-admin/src/main/java/org/apache/ranger/rest/TagREST.java 09d771565 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceWithTagsService.java
 PRE-CREATION 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceWithTagsServiceBase.java
 PRE-CREATION 
  security-admin/src/test/java/org/apache/ranger/biz/TestTagDBStore.java 
d6ebbc54d 
  security-admin/src/test/java/org/apache/ranger/rest/TestTagREST.java 
98d87bc0a 


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


Testing
---

Validated POST - service/tags/resource/service/{serviceName}/resource with 
postive and negative case.
Validated response of service/tags/resources/paginated api 
Sample response
{
"startIndex": 0,
"pageSize": 5,
"totalCount": 1,
"resultSize": 1,
"sortType": "asc",
"sortBy": "resourceId",
"queryTimeMS": 1710771145888,
"list": [
{
"id": 4,
"guid": "8f18d7b3-f885-4687-9438-ededdf340b18",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 1710429722000,
"updateTime": 1710431917000,
"version": 8,
"serviceName": "hive",
"resourceElements": {
"column": {
"values": [
"name"
],
"isExcludes": false,
"isRecursive": true
},
"database": {
"values": [
"hrDb1"
],
"isExcludes": false,
"isRecursive": true
},
"table": {
"values": [
"employee"
],
"isExcludes": false,
"isRecursive": true
}
},
"resourceSignature": 
"483ce23070c3243ffd6e9ebc4a2bc2c90553cbab0ed810bcae22ff6d76e9ca33",
"associatedTags": [
"PII_NAME",
"SSN"
]
}

],
"listSize": 1
}

Validated service/tags/resources/paginated api with resourceElements and 
tagNames for freestext resource search and multiple tagNames search 
respectively.


Thanks,

Anand Nadar

[jira] [Commented] (RANGER-4743) [JDK 11]: Fix ranger admin logging

2024-03-18 Thread Rakesh Gupta (Jira) 


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

Rakesh Gupta commented on RANGER-4743:
--

Hi [~abhi_2110],
Ranger admin logs not appearing due to HikariCP dependency which includes 
slf4j-api dependency with lower version(1.7.30) same issue is visible in JDK 
17, To resolve use below patch.
[^0001-RANGER-4743.patch]

> [JDK 11]: Fix ranger admin logging 
> ---
>
> Key: RANGER-4743
> URL: https://issues.apache.org/jira/browse/RANGER-4743
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Attachments: 0001-RANGER-4743.patch
>
>
> Currently, the ranger-admin logs do not appear when built and run with jdk 11.
> Logback and slf4j versions need to be upgraded to fix the above issue.
> More info: [https://logback.qos.ch/download.html] 
> CC: [~rmani]



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

[jira] [Updated] (RANGER-4743) [JDK 11]: Fix ranger admin logging

2024-03-18 Thread Rakesh Gupta (Jira) 


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

Rakesh Gupta updated RANGER-4743:
-
Attachment: 0001-RANGER-4743.patch

> [JDK 11]: Fix ranger admin logging 
> ---
>
> Key: RANGER-4743
> URL: https://issues.apache.org/jira/browse/RANGER-4743
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Attachments: 0001-RANGER-4743.patch
>
>
> Currently, the ranger-admin logs do not appear when built and run with jdk 11.
> Logback and slf4j versions need to be upgraded to fix the above issue.
> More info: [https://logback.qos.ch/download.html] 
> CC: [~rmani]



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

Review Request 74940: RANGER-4744: Ranger Admin startup using JDK17 gives ERROR in catalina.out due to missing jaxb dependencies

2024-03-18 Thread Rakesh Gupta 

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

Review request for ranger, bhavik patel, Dineshkumar Yadav, Kishor 
Gollapalliwar, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, sanket shelar, 
Sailaja Polavarapu, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

When we try to start Ranger Admin using JDK17, the Ranger Admin startup gives 
ERROR "javax.xml.bind.JAXBException Implementation of JAXB-API has not been 
found on module path or classpath" in catalina.out due to missing jaxb 
dependencies.
The jaxb classes were part of rt.jar in jdk8, but were removed in later 
versions of JDK.


Diffs
-

  kms/pom.xml 2739bb81a 
  security-admin/pom.xml fc59287d0 


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


Testing
---

Build Ranger using the command below and set up a local cluster by executing 
'mvn clean compile package install', followed by starting the Ranger Admin.

Verified that no errors are seen in the catalina.out file upon Ranger Admin 
startup.


Thanks,

Rakesh Gupta

[jira] [Updated] (RANGER-4749) Tag: Create an api to check if a resource is already available in database by resource input. And send tag list along with the resource list in response of GET /service/

2024-03-18 Thread Anand Nadar (Jira) 


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

Anand Nadar updated RANGER-4749:

Description: 
*1. Need an api to get the resource by resource if it exists in database.*
Case:
Suppose there already exists below tag and resource association.
PII_NAME tag is associated with (database:HR-DB, table:EMPLOYEE, column:NAME)

Now we dont know about the above resource already existing, so we are now 
trying to create a new tag resource association as below
PII_EMP_NAME associated with (database:HR-DB, table:EMPLOYEE, column:NAME)

This is done using PUT /service/tags/importservicetags -> op: add_or_update
So this will result in the deletion of PII_NAME association with the resource,  
and creation of PII_EMP_NAME tag associated with the resource.

So if we have this GET service/tags/resource/service/\{serviceName}/resource 
api which will have the payload as
{code:java}
{
   "database": {
   "values": [
   "HR-DB"
   ],
   "isRecursive": true
   },
   "table": {
   "values": [
   "EMPLOYEE"
   ],
   "isRecursive": true
   },
   "column": {
   "values": [
   "NAME"
   ],
   "isRecursive": true
   }
} {code}
we can check if this resource already exists or not.

If the resource exists, we can get all the tags associated with that 
resource(in our case PII_NAME), and include the new tag PII_EMP_NAME as well 
and send this in 
PUT /service/tags/importservicetags -> op: add_or_update
then both PII_NAME and PII_EMP_NAME will be associated with the resource.

*2. Need the list of associated tag names for a resource as well in  
/service/tags/resources/paginated api.*
Currently we are not returning the list of tags associated in the response.
This will get the service resources with all its associated tags in a single 
api which is also paginated.
Free text search on the resource, and multiple tag-name search

  was:
*1. Need an api to get the resource by resource if it exists in database.*
Case:
Suppose there already exists below tag and resource association.
PII_NAME tag is associated with (database:HR-DB, table:EMPLOYEE, column:NAME)

Now we dont know about the above resource already existing, so we are now 
trying to create a new tag resource association as below
PII_EMP_NAME associated with (database:HR-DB, table:EMPLOYEE, column:NAME)

This is done using PUT /service/tags/importservicetags -> op: add_or_update
So this will result in the deletion of PII_NAME association with the resource,  
and creation of PII_EMP_NAME tag associated with the resource.

So if we have this GET service/tags/resource/service/\{serviceName}/resource 
api which will have the payload as
{code:java}
{
   "database": {
   "values": [
   "HR-DB"
   ],
   "isRecursive": true
   },
   "table": {
   "values": [
   "EMPLOYEE"
   ],
   "isRecursive": true
   },
   "column": {
   "values": [
   "NAME"
   ],
   "isRecursive": true
   }
} {code}
we can check if this resource already exists or not.

If the resource exists, we can get all the tags associated with that 
resource(in our case PII_NAME), and include the new tag PII_EMP_NAME as well 
and send this in 
PUT /service/tags/importservicetags -> op: add_or_update
then both PII_NAME and PII_EMP_NAME will be associated with the resource.

*2. Need the list of associated tag names for a resource as well in  
/service/tags/resources/paginated api.*
Currently we are not returning the list of tags associated in the response.
This will get the service resources with all its associated tags in a single 
api which is also paginated.
And a free text search on the resource.


> Tag: Create an api to check if a resource is already available in database by 
> resource input. And send tag list along with the resource list in response of 
> GET /service/tags/resources/paginated API
> -
>
> Key: RANGER-4749
> URL: https://issues.apache.org/jira/browse/RANGER-4749
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Anand Nadar
>Priority: Major
>
> *1. Need an api to get the resource by resource if it exists in database.*
> Case:
> Suppose there already exists below tag and resource association.
> PII_NAME tag is associated with (database:HR-DB, table:EMPLOYEE, column:NAME)
> Now we dont know about the above resource already existing, so we are now 
> trying to create a new tag resource association as below
> PII_EMP_NAME associated with (database:HR-DB, table:EMPLOYEE, column:NAME)
> This is done using PUT /service/tags/importservicetags -> op: add_or_up