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
Multi-statement DML on one Lance table in a transaction: partial commit and no read-your-writes #313
Several DML statements on one Lance table inside BEGIN ... COMMIT lose a change or fail COMMIT part-way with earlier statements already published (e.g. UPDATE; UPDATE conflicts, INSERT (11); DELETE WHERE id=11 keeps row 11). Each statement builds its own Lance transaction on the last committed version, and Lance 14.0.x cannot read or atomically commit uncommitted writes.
#312 fails closed for these combinations. The proper fix is Lance Transaction V2 staged transactions (lance-format/lance#7954, #8646, #10722), which currently cover append only. I propose keeping the guard and adopting V2 here, then removing the guard, once it covers delete and update.
The staged transaction API is still feat(dataset): add append-only staged transactions lance#10722: an open draft at 0d863ec960f84c5e28c4e2e216d4add78ff53a1e, currently conflicting with main, and explicitly append-only. Delete, update, schema changes and index operations remain follow-ups.
No released Lance version contains the staged transaction API needed here. The dependency in this repository is still Lance v14.0.3.
The #312 guard therefore remains correct. This issue stays open until Lance can stage and atomically commit delete/update, that lands on main and ships in a release, and this extension adopts the V2 path and removes the guard.
Thanks for the detailed update! That was exactly my intention in opening this issue: to document the current limitation and track the upstream Lance work needed to support multi-statement transactions on a Lance table.
I agree with keeping the guard in place and leaving this issue open until the required upstream support is released and integrated into lance-duckdb.
Activity
Xuanwo commentedon Nov 18, 2026
Checked the upstream state today; the prerequisite is still not met, so this stays open.
main: feat(transaction): action-based transaction wire format (Transaction V2) lance#7954, feat(transaction): implement the Transaction V2 action vocabulary lance#8644, feat(transaction): implement the index management actions lance#8645 and feat(transaction): implement the remaining drafted actions lance#8646. feat(transaction): implement the remaining drafted actions lance#8646 landed as903907d2a55b53129e182d20fc2ba0018fc81cf7on 2026-11-18. That work is the action vocabulary and conflict machinery, not the staged transaction API this issue needs.0d863ec960f84c5e28c4e2e216d4add78ff53a1e, currently conflicting withmain, and explicitly append-only. Delete, update, schema changes and index operations remain follow-ups.The #312 guard therefore remains correct. This issue stays open until Lance can stage and atomically commit delete/update, that lands on
mainand ships in a release, and this extension adopts the V2 path and removes the guard.jackylee-ch commentedon Nov 18, 2026
Thanks for the detailed update! That was exactly my intention in opening this issue: to document the current limitation and track the upstream Lance work needed to support multi-statement transactions on a Lance table.
I agree with keeping the guard in place and leaving this issue open until the required upstream support is released and integrated into lance-duckdb.