[ISSUE] (TEPHRA-136) TransactionContext should have a method to flush changes

Andreas Neumann (JIRA)

unread,

Oct 7, 2015, 9:16:21 PM10/7/15

to tephr...@googlegroups.com

Andreas Neumann created an issue

Tephra /

TEPHRA-136

TransactionContext should have a method to flush changes

Issue Type:	Improvement
Affects Versions:	0.6.3
Assignee:	Poorna Chandra
Components:	core
Created:	07/Oct/15 6:15 PM
Fix Versions:	0.6.3
Priority:	Critical
Reporter:	Andreas Neumann

Currently, TransactionContext has a method persist() that flushes all changes, and if anyone fails, aborts the transaction. There should be a method that simply attempts to flush all changes, but in case of failure does not abort the transaction. This is useful in transactions that span multiple processes, for example for map/reduce, where the commit and abort of the transaction is done only in a central client, but not in all of the clients.

Add Comment

This message was sent by Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc)

Andreas Neumann (JIRA)

unread,

Oct 7, 2015, 9:25:21 PM10/7/15

to tephr...@googlegroups.com

Andreas Neumann commented on an issue

Re: TransactionContext should have a method to flush changes

It would also be useful to have a getter for the list of TransactionAwares that are in the current transaction.

Add Comment

Tephra /

TEPHRA-136

TransactionContext should have a method to flush changes

Currently, TransactionContext has a method persist() that flushes all changes, and if anyone fails, aborts the transaction. There should be a method that simply attempts to flush all changes, but in case of failure does not abort the transaction. This is useful in transactions that span multiple processes, for example for map/reduce, where the commit and ...