[
https://issues.apache.org/jira/browse/FALCON-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358071#comment-14358071
]
Pallavi Rao commented on FALCON-1060:
-------------------------------------
An excerpt from the documentation - "Transactions need to be manually closed to
mark the end of a transactional context and to inform the graph database
whether the transaction was successful or not. Calling
TransactionalGraph.commit() persists the transactional state to the database
whereas TransactionalGraph.rollback() fails the transaction and discards any
mutations." To me it sounds like we do need to do an explicit rollback.
> 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)
