You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/05/10 15:01:00 UTC

[jira] [Commented] (ATLAS-2667) Enhance GraphTransactionInterceptor to ignore inner commit/rollback

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

Apoorv Naik commented on ATLAS-2667:
------------------------------------

Committed on master: https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=479b9ab1c0d461e89d14d2d3426af64f3cb9acb9

> Enhance GraphTransactionInterceptor to ignore inner commit/rollback
> -------------------------------------------------------------------
>
>                 Key: ATLAS-2667
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2667
>             Project: Atlas
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-alpha
>            Reporter: Apoorv Naik
>            Assignee: Apoorv Naik
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: 0001-ATLAS-2667-Enhance-GraphTransactionInterceptor-to-de.patch
>
>
> Some transactions need to be committed in one single shot, right now any layer that orchestrates the data persistence using different stores (e.g. AtlasEntityStore and AtlasRelationshipStore) will see two different commits. With introduction of relationships and Glossary it's become a necessity that the entity and relationships are persisted in one single transaction or else the object gets created partially and leads to an inconsistent state.
> This change restricts the commit/rollback from the outermost method invocation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)