[
https://issues.apache.org/jira/browse/TEPHRA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168167#comment-16168167
]
Micael Capitão commented on TEPHRA-99:
--------------------------------------
The TTL is of no concern to me. The second might be... the only way to avoid
the second problem would be to maintain the transaction in progress? But then
I'd need to have a way of finishing the transaction, etc. Now I see your point
on the other comment.
Is it possible to detect that the read point is behind some "destructive"
writing point? If so I could at least inform the client that the page he is
requesting is not valid anymore.
> Make "long running" transactions usable with TransactionContext
> ---------------------------------------------------------------
>
> Key: TEPHRA-99
> URL: https://issues.apache.org/jira/browse/TEPHRA-99
> Project: Tephra
> Issue Type: Improvement
> Components: core
> Reporter: Gary Helmling
> Assignee: Gary Helmling
>
> "Long running" transactions (type == LONG) are supported by the Tephra
> {{TransactionManager}}, but {{TransactionContext}} does not expose any way
> for clients to interact with them. I think this will require a couple
> changes:
> * add a {{startLong()}} method to TransactionContext
> * add a constructor to TransactionContext that takes an existing
> {{Transaction}} instance. Since long running transactions are often used in
> map reduce processing, the process committing the transaction may be
> different from the process that started the transaction. In this situation,
> we need a way to pass the serialized transaction all the way through to the
> other process.
> Regarding map reduce support, we could use additional utilities or support in
> place to make transactions easier to use with map reduce. But this would at
> least serve as a first step.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
