[
https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinoth Chandar updated HUDI-677:
--------------------------------
Labels: help-requested help-wanted (was: help-wanted)
> 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: Improvement
> Components: Code Cleanup
> Reporter: Vinoth Chandar
> Assignee: Vinoth Chandar
> Priority: Major
> Labels: help-requested, 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)
