[
https://issues.apache.org/jira/browse/RANGER-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-5134.
------------------------------------
Fix Version/s: 3.0.0
2.7.0
Resolution: Fixed
Commit to master: [https://github.com/apache/ranger/commit/e93c017]
Commit to ranger-2.7: [https://github.com/apache/ranger/commit/f04e8dd]
> Fix processing of tasks scheduled to run after current transaction is complete
> ------------------------------------------------------------------------------
>
> Key: RANGER-5134
> URL: https://issues.apache.org/jira/browse/RANGER-5134
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 2.5.0
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0, 2.7.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Certain tasks like policy label updates, role version updates, tag version
> updates, etc. happen in a separate subsequent transaction after the current
> transaction to create/update policy/role/tag is complete. This happens in
> RangerTransactionSynchronizationAdapter.
> Fix the processing of tasks in runRunnables where unhandled
> TransactionExceptions could lead to an infinite do while loop.
> Here are test scenarios which capture this:
> # Update a policy in one session and delete the same policy in another
> session
> # Add a label for a policy in one session and remove an existing label for
> the same policy in another session.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
