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/02 20:12:18 UTC

[jira] [Updated] (RANGER-866) Service delete fails with error 'XXService was updated or deleted by another transaction'

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

Madhan Neethiraj updated RANGER-866:
------------------------------------
    Attachment: 0001-RANGER-866-refactor-the-logic-to-update-XXService.ta.patch

> Service delete fails with error 'XXService was updated or deleted by another transaction'
> -----------------------------------------------------------------------------------------
>
>                 Key: RANGER-866
>                 URL: https://issues.apache.org/jira/browse/RANGER-866
>             Project: Ranger
>          Issue Type: Sub-task
>          Components: admin
>    Affects Versions: 0.6.0
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>         Attachments: 0001-RANGER-866-refactor-the-logic-to-update-XXService.ta.patch
>
>
> When a service has associated service-resource and tag-resource-map objects, deleting of the service fails with error "XXService was updated or deleted by another transaction'.
> This issue is caused the logic that updates service attributes tagVersion and tagUpdateTime on changes in tags associated with the service. Current implementation uses 'update statement', which does not seem to update XXService instances in JPA's transaction cache. To fix this issue, use 'select statement' to retrieve XXService objects and update the fields.



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