BigData / Apache Hudi Interview Questions
Explain the lifecycle of a Hudi commit on the timeline?
Every write action on a Hudi table — not just user commits, but compactions, clusterings, and cleans too — passes through the same three-state lifecycle on the timeline.
An instant starts as requested, simply recording that an action has been planned. Once execution begins it moves to inflight, meaning data or metadata is actively being written but isn't yet safe to read. Only when the action finishes successfully does it become completed, at which point it's atomically visible to every reader as part of the table's history. If the writer fails or is interrupted while an instant is inflight, that instant is left dangling until a rollback cleans it up on the next write attempt — readers never see partial results because they only ever consider completed instants.
More Related questions...
