----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74338/#review225264 -----------------------------------------------------------
Ship it! Ship It! - Abhay Kulkarni On March 6, 2023, 10:14 a.m., Pradeep Agrawal wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74338/ > ----------------------------------------------------------- > > (Updated March 6, 2023, 10:14 a.m.) > > > Review request for ranger, Abhishek Kumar, Dineshkumar Yadav, Kishor > Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Nikhil P, Pradeep Agrawal, > Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4123 > https://issues.apache.org/jira/browse/RANGER-4123 > > > Repository: ranger > > > Description > ------- > > **Problem Statement:** > During the ranger upgrade process, Java patch J10019 updates the policy and > policy json is also updated in policy_text column of each row. However policy > update entry is not being captured in x_data_hist. whenever we click on > policy id link of access audit page the /plugins/policies/eventTime API is > called along with corresponding policy id and version. if x_data_hist table > does contain such entry then API request fails with error message "No policy > found for given version" > > **Proposed solution:** The proposed changes shall create an entry in > x_data_hist table for each policy which is being updated. > > > Diffs > ----- > > > security-admin/src/main/java/org/apache/ranger/patch/PatchForUpdatingPolicyJson_J10019.java > 6eb3315e7 > > > Diff: https://reviews.apache.org/r/74338/diff/1/ > > > Testing > ------- > > Without this patch x_data_hist was not having any entry after the execution > of patch J10019. > However after this change the x_data_hist table is populated and API call is > working. > > > Thanks, > > Pradeep Agrawal > >
