phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ohad Shacham (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra
Date Thu, 11 May 2017 13:28:04 GMT


Ohad Shacham commented on PHOENIX-3734:

Hi [] and [~tdsilva],

We are currently at the point where the code was refactored and have an abstraction layer
for the transaction processor. 
At this point, the Tephra layer was implemented and the code functionality is as before. 

In my opinion, this should be a checkpoint where we review this patch and commit it to the
Keeping this code at the Omid branch and commit only when the Omid layer will be available
will significantly increase the review overhead and reduce its fruitfulness.

I also think it is better to do the following Omid related commits to the master. These commits
will be related only to Omid only and the Omid option in Phoenix will be disabled until completion
of the feature.

What do you think?

> Refactor Phoenix to use TAL instead of direct calls to Tephra
> -------------------------------------------------------------
>                 Key: PHOENIX-3734
>                 URL:
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Ohad Shacham
>            Assignee: Ohad Shacham
> Refactor Phoenix to use the new transaction abstraction layer instead of direct calls
to Tephra. Once this task will be committed, Phoenix will continue working with Tephra but
will have the option for fast integration of new transaction processing engines.

This message was sent by Atlassian JIRA

View raw message