[
https://issues.apache.org/jira/browse/TEPHRA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166619#comment-16166619
]
Andreas Neumann commented on TEPHRA-99:
---------------------------------------
It seems what you really need is a read-only transaction. See the discussion in
TEPHRA-159. Perhaps it is time to add support for that.
In the mean time, if you can't wait until that is implemented, consider using
TransactionAwareHTable.startTx() to make it aware of the transaction, and it
will take care of injecting the transaction into the Scan.
> 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)
