From 4b610dea0fbacf850def10188eea3aa40ea4737f Mon Sep 17 00:00:00 2001 From: Taewoon Kim Date: Tue, 3 Nov 2026 22:28:25 +0900 Subject: [PATCH] Docs: say that a failed load can keep different rows on the two packages (closes #174) The commit-size defaults are measured per build (native 1000, JVM 10000) and stay; the bulk-loads page already explained what a failed load keeps. This adds the cross-package consequence and the way to make it identical (the same commit_every on both, or commit_every=0). No behaviour change. Co-Authored-By: Claude Opus 5.5 --- docs/modules/ROOT/pages/how-to/bulk-loads.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/modules/ROOT/pages/how-to/bulk-loads.adoc b/docs/modules/ROOT/pages/how-to/bulk-loads.adoc index 1224d12..148c077 100644 --- a/docs/modules/ROOT/pages/how-to/bulk-loads.adoc +++ b/docs/modules/ROOT/pages/how-to/bulk-loads.adoc @@ -51,6 +51,8 @@ The in-flight transaction is the data that each young garbage collection must co Rows that are already committed stay committed when a later chunk fails. Only the transaction that was open is rolled back. With a smaller commit size, a failed load keeps its rows up to the last commit, and that commit is now at most 1000 rows behind the failure instead of 10,000. If you need all-or-nothing, open your own transaction, or pass `commit_every=0`. +Because the two packages have different defaults, the same program can keep different rows after the same failure: each keeps its rows up to its own last commit. If the outcome of a failed load must not depend on the package, pass the same `commit_every` on both, or `commit_every=0`. + == Change the commit size [source,python]