RANGER-5315: Enhance Audit Log Filters to Support Resource Name Exclusions #663
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dhavalshah9131
requested review from
dhavaljrajpara,
pradeepagrawal8184 and
dineshkumar-yadav
RakeshGuptaDev
force-pushed
the
RANGER-5315
branch
from
83beb9b to
f57a3a8
Compare
dineshkumar-yadav
approved these changes
Sep 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Enhance Ranger's audit search functionality to support exclusion filters based on resource names.
How was this patch tested?
Tested /assets/accessAudit?excludeResourceName= — confirmed that Ranger access audit logs correctly exclude entries for the specified resource name. Verification was performed via both the API and the Ranger UI. Currently tested and validated for Solr only.