[jira] [Created] (ATLAS-1252) Transactions should be scoped at the API level not at the individual graph operations

["David Radley (JIRA)" <ji...@apache.org>]

David Radley created ATLAS-1252:
-----------------------------------

             Summary: Transactions should be scoped at the API level not at the individual graph operations   
                 Key: ATLAS-1252
                 URL: https://issues.apache.org/jira/browse/ATLAS-1252
             Project: Atlas
          Issue Type: New Feature
            Reporter: David Radley


I notice that GraphBackedMetadataRepository implements  MetadataRepository. It has @GraphTransaction annotations around its methods. This means that each one of the metadataService operations will run in its own transaction. There are cases in the code where an API call issue more than one update / creation orientated call to the Metadata service. This means that in the event of failures- the graph could be left partially updated. For example creating a term creates , a trait type and trait instance but each have their own transaction. Transactions should be scoped around all of the graph calls a create,update or delete API invocation makes. 

Note if an update / create / delete API call only issues one call to the metadata service then the existing mechanism works.



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