[
https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinoth Chandar updated HUDI-677:
--------------------------------
Description:
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
was:
Over time a lot of the core transaction management code has been split across
various files in hudi-client.. We want to clean this up and present a nice
interface..
Some notes and thoughts and suggestions..
<WIP>
> 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)
