Repository navigation
Graph analytical view counts an edge twice after a background compaction #11192
Description
A graph analytical view could count an edge twice after a background compaction, and kept the wrong count until the next compaction or rebuild.
A transaction's records become readable as soon as it commits, and the view hears about the change a moment later. If a compaction's scan read the new edge in between, and the change notice arrived after the compaction swapped in its result, the edge was added again on top of a base that already held it. Full builds were protected against this since #8378, but compactions were not. Path counts, degrees and algorithms on the view then answer with the extra edge.
Found through Issue10189AsyncViewServesWhileUpdatingTest, which fails intermittently in CI. Issue10208ViewVertexSubtypesTest also fails intermittently, but there the view is right: the test raced the rebuild its own assertion starts.
Activity
fix(#11192): a GAV compaction checks a change delivered after its swa…
lvca commentedon Nov 3, 2026
Fixed in #11193.
A committed edge is readable right away, but the graph analytical view hears about it a moment later. If a background compaction read the edge and the notice arrived after the compaction had swapped in its result, the view added the edge a second time. Degrees, path counts and algorithms on the view then saw the extra edge until the next compaction.
Compactions now record what their scan read and check every late change against it, the same protection full builds already had. The new regression test reproduced the double count every time before the fix.
❤️ 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.
fix(#11192): a GAV compaction checks a change delivered after its swa…