From bc354d622e9960ee6c081341474694c98580da66 Mon Sep 17 00:00:00 2001 From: Taewoon Kim Date: Fri, 6 Nov 2026 15:06:31 +0900 Subject: [PATCH] Docs: bulk-loads names the older engine, not a 26.11.1.devN pre-release No 26.11.1.devN is on PyPI: the first release of arcadedb and arcadedb-jvm is the 26.11.1 final, so every wheel from this repository carries the engine fix (ArcadeData/arcadedb#10746). The workaround applies to an engine older than 26.11.1. Co-Authored-By: Claude Sonnet 5.5 --- docs/modules/ROOT/pages/how-to/bulk-loads.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/how-to/bulk-loads.adoc b/docs/modules/ROOT/pages/how-to/bulk-loads.adoc index ace65a4..8acbadf 100644 --- a/docs/modules/ROOT/pages/how-to/bulk-loads.adoc +++ b/docs/modules/ROOT/pages/how-to/bulk-loads.adoc @@ -164,7 +164,7 @@ An engine-level Java run of the same shape confirms the split: after 2,000 round The engine-level Java run, repeated on the merge of the fix, kept the batch's edge bucket at 4 pages after 2,000 rounds, the same as `newEdge` in ordinary transactions, against 2,000 pages on its parent (https://github.com/ArcadeData/arcadedb/issues/10746#issuecomment-6462354150[verification on #10746]). -From 26.11.1 on, `graph_batch()` is fine for a workload that deletes and inserts again. On a `26.11.1.devN` pre-release, write the edges with SQL (`CREATE EDGE`) or with `Vertex.new_edge` inside `db.transaction()` instead. Both stayed flat in the measurement (0.25 MiB in the table). +From 26.11.1 on, `graph_batch()` is fine for a workload that deletes and inserts again. On an engine older than 26.11.1, write the edges with SQL (`CREATE EDGE`) or with `Vertex.new_edge` inside `db.transaction()` instead. Both stayed flat in the measurement (0.25 MiB in the table). == If a graph batch is interrupted