[
https://issues.apache.org/jira/browse/PHOENIX-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205263#comment-15205263
]
Gary Helmling commented on PHOENIX-2788:
----------------------------------------
I really did not mean to kill discussion on HBASE-11447. I was merely trying
to dig into some important details of how the API would tie in to the rest of
the HBase client and whether or not anyone making use of it would be tied
directly to implementation specific code for common cases, both of which seemed
to be missing in the current proposal.
Reviving HBASE-11447 and then using those APIs might be a way of making this
pluggable from the Phoenix standpoint. But from what I recall, the way that
Phoenix coprocessors hooked in to changes for secondary indexes gets pretty
deep into what the underlying transaction implementation is doing. So there
may be more plugging needed on the Phoenix side even if a common HBase API
existed.
> 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)
