phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3656) Define a transaction abstraction layer
Date Thu, 09 Mar 2017 21:31:38 GMT

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

Thomas D'Silva commented on PHOENIX-3656:
-----------------------------------------

+1 
Committed to the omid branch

> 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, PHOENIX-3656.v1.patch, PHOENIX-3656.v2.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)

Mime
View raw message