You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2016/02/02 07:02:39 UTC

[jira] [Commented] (RANGER-831) Single policy update increases policy history version by 2 - gives error to view history

    [ https://issues.apache.org/jira/browse/RANGER-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127727#comment-15127727 ] 

Gautam Borad commented on RANGER-831:
-------------------------------------

Committed to master : https://github.com/apache/incubator-ranger/commit/de9327df0a2f7b5e8fcea976dbc253d7098e2578
Committed to ranger-0.5 : https://github.com/apache/incubator-ranger/commit/0c9418cf8465e5757440eef9c8a706c4b0584538

> Single policy update increases policy history version by 2 - gives error to view history
> ----------------------------------------------------------------------------------------
>
>                 Key: RANGER-831
>                 URL: https://issues.apache.org/jira/browse/RANGER-831
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin, audit
>    Affects Versions: 0.6.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 0.6.0
>
>         Attachments: RANGER-831.patch
>
>
> *Problem Statement*
> When we update the object of policy ( i.e. when resource and policy item both are changed in single update), it increments value of version field by 2 rather than incrementing by 1. So it skips the sequence of version in DB and it looks like this
> 1 2 4 6 8 10 .. etc
> And because of this we are facing issue in seeing snapshot of policy update from Access Audit -> Policy Snapshot popup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)