[
https://issues.apache.org/jira/browse/RANGER-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508971#comment-17508971
]
Jeevan p commented on RANGER-3670:
----------------------------------
hello, im so sorry but this comment is not of any use to this issue, i have
noticed you are one of the top contributors on apache-ranger github so can you
kindly please look into this issue
https://issues.apache.org/jira/browse/RANGER-3668
> Policy update creates unnecessary entries in transaction log table
> ------------------------------------------------------------------
>
> Key: RANGER-3670
> URL: https://issues.apache.org/jira/browse/RANGER-3670
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 2.2.0
> Reporter: Madhan Neethiraj
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
