Repository navigation
docs: the graph_batch space-reuse limitation is fixed in ArcadeDB 26.11.1 - #133
Merged
Merged
Conversation
…11.1 (#132) ArcadeData/arcadedb#10836 fixed #10746 on 2026-10-28; verified on its merge (edge bucket 4 pages after 2,000 sliding-window rounds, against 2,000 before). The section, retitled, now says fixed in 26.11.1, keeps the 26.10.2 measurement for the devN pre-releases (DEV_ENGINE 26.10.2), and limits the CREATE EDGE advice to those. Both graph_batch docstrings say the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #132
ArcadeData/arcadedb#10836 (merged 2026-10-28, ArcadeDB 26.11.1) fixed the engine behavior behind the "Known limitation: graph batches next to deletes" section: a
graph_batch()flush now puts each edge where an ordinary insert would while an existing page has room. It was verified on the merge commit (comment on #10746): after 2,000 sliding-window rounds the edge bucket stays at 4 pages, as with ordinary transactions, instead of 2,000.Changes:
how-to/bulk-loads.adoc: the section is retitled "Graph batches next to deletes (fixed in ArcadeDB 26.11.1)". The WARNING becomes a NOTE that says what changed and that the 26.11.1 packages ship it. The 26.10.2 measurement stays, labeled as 26.10.2, because the26.11.1.devNpre-releases embed that engine (DEV_ENGINEintest-native.yml). TheCREATE EDGE/Vertex.new_edgeadvice is limited to those pre-releases.core.pyand_native/database.py: thegraph_batchdocstring notes say the same and point at the new section title.Found while re-reading the native soak run of 2026-10-29: its wheel embeds 26.10.2, and its edge bucket grew by one page per round, which is the pre-fix behavior.
🤖 Generated with Claude Code