[
https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095782#comment-17095782
]
Vinoth Chandar commented on HUDI-677:
-------------------------------------
cc [~pwason] this is also something we need to do, to clean up tech debt.. also
a good learning task.. we will have to introduce new actions for metadata
compaction may be... and it will be usefiul to be conversant with this part of
the code as well
> 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
> Fix For: 0.6.0
>
>
> 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)
