You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ohad Shacham (JIRA)" <ji...@apache.org> on 2017/03/06 15:26:32 UTC

[jira] [Commented] (PHOENIX-3656) Define a transaction abstraction layer

    [ https://issues.apache.org/jira/browse/PHOENIX-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897510#comment-15897510 ] 

Ohad Shacham commented on PHOENIX-3656:
---------------------------------------

As per James request, I have changed PhoenixTransactionalTable to inherit from HTableInterface. 
I will change [PHOENIX-3671] accordingly.
Could you please review the patch? I would like to start working on the integration of Phoenix with the TAL and therefore, would be happy if the TAL and the Tephra implementation will be committed.

Thx!
Ohad


> Define a transaction abstraction layer
> --------------------------------------
>
>                 Key: PHOENIX-3656
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3656
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Ohad Shacham
>            Assignee: Ohad Shacham
>         Attachments: PHOENIX-3656.patch
>
>
> Currently Tephra calls are integrated inside Phoenix code. Therefore, in order to support both Omid and Tephra, we need to add another abstraction layer that later-on will be connected to both Tephra and Omid. 



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