Repository navigation
The sorted index build is refused whenever ANY transaction on the thread holds a write, even one unrelated to the indexed type #10466
Description
Follow-up from #10450.
#10450 narrowed the decision of whether an index build joins the caller's transaction to "has the caller written to the buckets this build scans" (IndexBuilder.callerTransactionHasChangesIn). The sorted build has its own, broader guard: TypeIndexBuilder.sortedBuildRefusal() refuses it (and isSortedBuildChosenFor silently falls back to the record-at-a-time build) when anyCallerTransactionHasChanges() is true, i.e. when any transaction stacked on the thread holds any write at all.
So BEGIN; INSERT INTO Unrelated ...; CREATE INDEX ON Big (id) UNIQUE; COMMIT over a large committed Big loses the sorted build (#10334, #10267), and a UNIQUE index pays the quadratic record-at-a-time build again, even though the sorted build only needs the indexed buckets to be free of pending writes.
Entry point: TypeIndexBuilder.sortedBuildRefusal() / isSortedBuildChosenFor().
Why it was out of scope for #10450: the sorted build sets the whole transaction stack aside (CommittedReadScope) and writes its pages outside any transaction. Narrowing its guard needs the same per-bucket test, applied to every transaction in the stack (not only the innermost one), plus an argument that writing index pages outside a transaction while an unrelated outer transaction holds pages is safe. That deserves its own change and tests.
Activity
fix(#10466): the sorted index build is refused only by pending writes…
robfrank commentedon Oct 21, 2026
Fixed in #10475. The sorted index build was refused whenever any open transaction held any write, so
BEGIN; INSERT INTO Unrelated ...; CREATE INDEX ON Big (id) UNIQUE; COMMITfell back to the much slower record-at-a-time build. The build is now refused only when some open transaction (at any nesting level) wrote to the buckets the index scans, including sub-type buckets. Writes to the indexed type, including updates, deletes and sub-type inserts, are still refused. The fix is complete.❤️ Thanks for helping make ArcadeDB better! ArcadeDB is free and open source, sustained by its community. If it's useful to you or your company, please consider becoming a sponsor to keep development going.
test(#10349): force the record-at-a-time build with a pending record …
fix(#10349, #10309): lazy Gremlin neighbor expansion, always-empty fi…
fix(#10466): the sorted index build is refused only by pending writes…
fix(#10349, #10309): lazy Gremlin neighbor expansion, always-empty fi…