You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2016/03/30 01:55:25 UTC

[jira] [Updated] (RANGER-901) x_service table columns that track policy/tag updates to be moved to a new table

     [ https://issues.apache.org/jira/browse/RANGER-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj updated RANGER-901:
------------------------------------
    Assignee: Abhay Kulkarni

> x_service table columns that track policy/tag updates to be moved to a new table
> --------------------------------------------------------------------------------
>
>                 Key: RANGER-901
>                 URL: https://issues.apache.org/jira/browse/RANGER-901
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 0.6.0
>            Reporter: Abhay
>            Assignee: Abhay Kulkarni
>
> When Tag objects (Tag and TagResourceMap) are created or updated because of receipt of Atlas notification, the tag-version stored in x_service table is incremented. If the service is updated at the same time, then one of these two operations fails due to database concurrency constraints. Moving  tag-version attribute to another table will alleviate this issue.



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