[
https://issues.apache.org/jira/browse/RANGER-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881329#comment-17881329
]
Madhan Neethiraj edited comment on RANGER-4930 at 9/12/24 11:05 PM:
--------------------------------------------------------------------
[~zhongwei11] - thank you for the crisp description of the issue. The fix in
RANGER-3554 should address this issue. This fix was included in 2.3.0 release.
I suggest upgrading to 2.3.0 or higher version of Ranger.
was (Author: madhan.neethiraj):
[~zhongwei11] - the fix in RANGER-3554 should address this issue. This fix was
included in 2.3.0 release.
> ranger
> ------
>
> Key: RANGER-4930
> URL: https://issues.apache.org/jira/browse/RANGER-4930
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Environment: ranger2.2
> x86 cnetos
> Reporter: wangzhongwei
> Priority: Major
>
> When user creates a policy through the web interface, or updates a
> policy, or creates a role or updates a role , the version of the policy or
> role will be modified. This version change is implemented through
> {{{}transactionSynchronizationAdapter.executeOnTransactionCommit{}}}. The
> database update operation occurs in the callback function
> {{{}afterCompletion{}}}. However, during debugging, it is occasionally found
> that {{afterCompletion}} is not invoked, which results in the policy or role
> being created or updated on the web interface, but the version remains
> unchanged, preventing the plugin from triggering the action to re-fetch the
> policy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
