[
https://issues.apache.org/jira/browse/RANGER-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881437#comment-17881437
]
wangzhongwei edited comment on RANGER-4930 at 9/13/24 2:36 AM:
---------------------------------------------------------------
[~madhan] Thank you very much for your guidance. I found the changes in the
RANGER-3554 patch are all within
{{{}RangerTransactionSynchronizationAdapter.afterCompletion{}}}, but after
investigating, I found that in abnormal situations, this function is not
called, and the log message {{LOG.debug("==>
RangerTransactionSynchronizationAdapter.afterCompletion(status=" + (status ==
STATUS_COMMITTED ? "COMMITTED" : "ROLLED_BACK") + ")");}} is missing. However,
in normal scenarios without issues, this log is present.
was (Author: JIRAUSER285670):
[~madhan] thank you very much for your gudance,I will merge this patch and
observer the results
> policy or role created or updated while plugin not re-fetch the policy
> ----------------------------------------------------------------------
>
> 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)
