RANGER-5526: Security Zone creation fails with tag service due to NonUniqueResultException#888
Open
RakeshGuptaDev wants to merge 1 commit intoapache:ranger-2.9from
Open
Conversation
…UniqueResultException
Contributor
|
@RakeshGuptaDev - the fix looks good. Given this service-def is in DRAFT mode, it is not necessary to handle upgrade scenario. |
mneethiraj
approved these changes
Mar 24, 2026
maheshbandal15
approved these changes
Mar 25, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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?
While creating a Security Zone with a tag service, the operation fails during postCreate execution. The stack trace shows a NonUniqueResultException from XXAccessTypeDefDao.findByNameAndServiceId(), triggered during default policy creation.
This issue is caused by duplicate entries in the access type definition tables for the associated service.
For example, the following query returns 2 records:
select * from x_access_type_def where name = 'ozone:assume_role';
How was this patch tested?
Verified that duplicate entries in x_access_type_def were removed, after which the Security Zone was created successfully and default policies were generated as expected.