ramackri opened a new pull request, #1070:
URL: https://github.com/apache/ranger/pull/1070

   ## Summary
   - Backports [RANGER-5513 (#880)](https://github.com/apache/ranger/pull/880) 
to the `ranger-2.9` release branch.
   - Adds input validation for Ranger lookup clients (Hive, HBase, Knox, 
Elasticsearch, Presto, Solr, Trino, Schema Registry) via shared helpers in 
`BaseClient`.
   - Adds unit tests across affected modules and ranger-2.9-specific 
pom/backport fixes (mockito test deps, parent version `2.9.0`, Solr enum 
naming, hamcrest for schema-registry).
   
   ## Backport adjustments for ranger-2.9
   - Restored `2.9.0` parent versions in plugin poms (master checkout had 
`3.0.0-SNAPSHOT`).
   - Added `mockito-inline` + `mockito-junit-jupiter` test dependencies where 
needed.
   - Kept `junit-vintage-engine` in `plugin-presto` for existing JUnit4 tests.
   - Removed conflicting `log4j-over-slf4j` test dep from `hive-agent`.
   - Mapped Solr lookup enums to `RESOURCE_TYPE` / `ADMIN_TYPE` (ranger-2.9 
naming).
   
   ## Test plan
   - [x] `mvn test -pl agents-common -Dtest=TestBaseClient`
   - [x] `mvn test -pl hive-agent -Dtest=TestHiveClient`
   - [x] `mvn test -pl hbase-agent -Dtest=TestHBaseClient`
   - [x] `mvn test -pl knox-agent -Dtest=TestKnoxClient`
   - [x] `mvn test -pl plugin-trino -Dtest=TestTrinoClient`
   - [x] `mvn test -pl plugin-presto -Dtest=TestPrestoClient`
   - [x] `mvn test -pl plugin-solr -Dtest=TestServiceSolrClient`
   - [x] `mvn test -pl plugin-elasticsearch -Dtest=TestElasticsearchClient`
   - [x] `mvn test -pl plugin-schema-registry -Dtest=AutocompletionAgentTest`
   
   **Note:** Merging to `ranger-2.9` while RC0 vote is open would invalidate 
RC0 and require an rc1 rebuild/re-vote. PMC approval is required per 
branch-lock policy.
   
   
   Made with [Cursor](https://cursor.com)


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to