[
https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075015#comment-17075015
]
Vinoth Chandar commented on HUDI-677:
-------------------------------------
After spending some time, accurately added new description..
For sake of multi engine support, I think the real issue would be to first
clean up teh calling code i.e the various action executions that interact with
the timeline.. I created HUDI-756 to do this for cleaning.. Will follow up with
other actions as well..
We can park this one until those are done..
> 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
> 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)
