----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73350/#review222990 -----------------------------------------------------------
Ship it! Ship It! - Ramesh Mani On May 12, 2021, 12:56 a.m., Abhay Kulkarni wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73350/ > ----------------------------------------------------------- > > (Updated May 12, 2021, 12:56 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Madhan > Neethiraj, Mehul Parikh, and Velmurugan Periasamy. > > > Bugs: RANGER-3284 > https://issues.apache.org/jira/browse/RANGER-3284 > > > Repository: ranger > > > Description > ------- > > Some tasks, such as updating policy/tag versions of a service after a > policy/tag is updated, are scheduled to run after the transaction changing > policy/tag is completed. The scheduling and execution of such tasks is > complicated and can be simplified by directly queueing the task to be > executed on Transaction commit/completion. > > > Diffs > ----- > > security-admin/src/main/java/org/apache/ranger/biz/PolicyRefUpdater.java > 115e55629 > security-admin/src/main/java/org/apache/ranger/biz/RoleRefUpdater.java > 10a762576 > security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java > dd58e0587 > > > Diff: https://reviews.apache.org/r/73350/diff/1/ > > > Testing > ------- > > Passed all unit tests. > Ensured that when a resource service is created, a tag service, if not > already present, is created and linked with the resource-service by the task > scheduled to run after the transaction that created resource service is > committed. > > > Thanks, > > Abhay Kulkarni > >
