You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Vinoth Chandar (Jira)" <ji...@apache.org> on 2020/05/10 13:35:00 UTC

[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes

     [ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinoth Chandar updated HUDI-677:
--------------------------------
    Fix Version/s:     (was: 0.6.0)

> Abstract/Refactor all transaction management logic into a set of classes 
> -------------------------------------------------------------------------
>
>                 Key: HUDI-677
>                 URL: https://issues.apache.org/jira/browse/HUDI-677
>             Project: Apache Hudi (incubating)
>          Issue Type: Sub-task
>          Components: Code Cleanup
>            Reporter: Vinoth Chandar
>            Assignee: Vinoth Chandar
>            Priority: Major
>              Labels: help-wanted
>
> Hudi's timeline management code sits in HoodieActiveTimeline and HoodieDefaultTimeline classes, taking action through the four stages : REQUESTED, INFLIGHT, COMPLETED, INVALID.
> For sake of better readability and maintenance, we should look into reimplementing these as a state machine. 
> Note that this is better done after organizing the action execution classes (as in HUDI-756) in hudi-client



--
This message was sent by Atlassian Jira
(v8.3.4#803005)