----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74003/#review224472 -----------------------------------------------------------
Ship it! Ship It! - Madhan Neethiraj On May 27, 2022, 3:17 a.m., Abhishek Kumar wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74003/ > ----------------------------------------------------------- > > (Updated May 27, 2022, 3:17 a.m.) > > > Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, and Velmurugan > Periasamy. > > > Bugs: RANGER-3670 > https://issues.apache.org/jira/browse/RANGER-3670 > > > Repository: ranger > > > Description > ------- > > When a policy is updated, Ranger creates entries in x_trx_log table for each > updated field in the policy. For example, when a policy is disabled, > following record is added in this table: > > > > object_id object_name attr_name prev_val new_val > 6 all - database Policy Status true false > > > Following 2 additional records are added in this table even though these > fields are not updated in the policy: > > object_id object_name attr_name prev_val new_val > 6 all - database Validity Schedules [] [] > 6 all - database Policy Conditions > > > Above entries should be avoided. > > > Diffs > ----- > > > security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java > a7a0d6f0d > > > Diff: https://reviews.apache.org/r/74003/diff/1/ > > > Testing > ------- > > Tested on remote cluster. > > > Thanks, > > Abhishek Kumar > >
