[
https://issues.apache.org/jira/browse/PHOENIX-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205004#comment-15205004
]
stack commented on PHOENIX-2788:
--------------------------------
What would it take [~giacomotaylor]? I thought the notion of pluggable
transaction API was killed by the comment on the end of "HBASE-11447 Proposal
for a generic transaction API for HBase" by [~ghelmling] where he notes
transactions are begin/end/rollback at the highest level but when you dig in,
there is a a lot of implementation specifics that is hard to abstract.
> Make transactions pluggable in Phoenix
> --------------------------------------
>
> Key: PHOENIX-2788
> URL: https://issues.apache.org/jira/browse/PHOENIX-2788
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> Given that now there's another transactional library for transactions over
> HBase in Omid that will likely be entering the incubator soon, we should
> investigate what it'll take to make our transaction support pluggable. Omid
> may not be that difficult to plugin, given that its basic approach (snapshot
> isolation) is similar to Tephra's (but of course the devil's in the details).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
