tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poorna Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEPHRA-136) TransactionContext should have a method to flush changes
Date Wed, 17 May 2017 01:17:04 GMT

     [ https://issues.apache.org/jira/browse/TEPHRA-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Poorna Chandra updated TEPHRA-136:
----------------------------------
    Fix Version/s:     (was: 0.7.1)

> TransactionContext should have a method to flush changes
> --------------------------------------------------------
>
>                 Key: TEPHRA-136
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-136
>             Project: Tephra
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.6.3
>            Reporter: Andreas Neumann
>            Assignee: Poorna Chandra
>            Priority: Critical
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message