Fix: evict namespace cache after transaction commit using event listener #1360
+50
−1
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.
Description:
This PR ensures that namespace details are correctly evicted from the cache when a member is removed from a namespace.
Previously, when removing a member, the cache was not being cleared, which caused stale data to persist — e.g., the removed user would still appear in the cached namespace details.
The updated method now evicts the namespace details before deleting the membership entity, ensuring cache consistency.
Changes:
Added cache.evictNamespaceDetails(namespace); before entity removal in removeNamespaceMember.
Annotated method with @transactional(rollbackOn = ErrorResultException.class) to maintain consistency on failures.
Why this fix matters:
Prevents stale cache entries after member removal.
Ensures consistency between database and cache.
Improves overall system reliability and data correctness.
Fixes #1185