[
https://issues.apache.org/jira/browse/FALCON-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352598#comment-14352598
]
Pallavi Rao commented on FALCON-1060:
-------------------------------------
Two things that I noted:
1. Lets take the following code as an example:
{code}
entityGraphBuilder.addProcessEntity((Process) entity);
getTransactionalGraph().commit();
break;
{code}
The addClusterEntity is a multi-step method. It adds all relevant vertices and
edges one by one. If any exception occurs during creation, what happens to the
transaction? Shouldn't the rollback method be invoked in finally?
2. Lets take the same example as above. If the vertex creation succeeds, but,
edge creation fails, we still go ahead and commit, leaving the vertex dangling.
Shouldn't the transaction boundary include vertex and all its edges?
> Handle transaction failures in Lineage
> --------------------------------------
>
> Key: FALCON-1060
> URL: https://issues.apache.org/jira/browse/FALCON-1060
> Project: Falcon
> Issue Type: Improvement
> Reporter: Ajay Yadava
> Assignee: Ajay Yadava
>
> Transaction failures should be handled on lineage to avoid issues like memory
> leaks etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
