Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
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
Attachments
Issue Links
- is a child of
-
HUDI-383 Introduce TransactionHandle abstraction to manage state transitions in hudi clients
- Resolved