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
Docs: the graph_batch space-reuse limitation (arcadedb#10746) is fixed in ArcadeDB 26.11.1 #132
The "Known limitation: graph batches next to deletes" section of how-to/bulk-loads.adoc, and the notes in the graph_batch docstrings of core.py and _native/database.py, say that a graph_batch() flush never reuses the space of deleted edges (ArcadeData/arcadedb#10746). ArcadeDB fixed that in ArcadeData/arcadedb#10836 (merged 2026-10-28, part of 26.11.1), and the fix was verified on its merge commit: after 2,000 sliding-window rounds the batch's edge bucket stays at 4 pages, as with ordinary transactions, instead of 2,000.
The 26.11.1 packages will embed the fixed engine, so the warning no longer describes them. The 26.11.1.devN pre-releases still embed engine 26.10.2 (DEV_ENGINE in test-native.yml), so the old behavior should stay documented for those, and the advice to use SQL CREATE EDGE or Vertex.new_edge should apply only there.
Activity
docs: the graph_batch space-reuse limitation is fixed in ArcadeDB 26.…