You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[EPIC] Stateful transactions and snapshot production (RFC-0003) #3266
Today, transaction actions are replayed from scratch on every catalog conflict. That is fine for simple metadata updates, but snapshot-producing actions (appends, and eventually merging operations like RowDelta/RewriteFiles) benefit from retaining work across retry attempts: stable execution identity, reusable metadata processing, and ownership of generated files that may require cleanup.
The RFC establishes:
A stateful TransactionAction model: each action pairs immutable intent with exclusively-owned, retry-persistent state; the transaction owns catalog refresh, retry, and replay.
Persistent snapshot producers (SimpleSnapshotProducer, MergingSnapshotProducer) as action state, replacing the attempt-scoped producer and its hook traits.
End-to-end operation implementations built on top of this foundation — e.g. RowDelta / RewriteFiles — are tracked separately (#1607) and become unblocked once milestones 2–4 land.
Activity
MergingSnapshotProducer, manifest filtering, reusable added-manifest production; wire terminalCommitStatusreporting and cleanup #3417SimpleSnapshotProducer, migrateFastAppendAction, remove the attempt-scopedSnapshotProducerand hook traits #3418