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 }}
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
bindings docs: Cypher ordered reads, OR, and parallel scans in 26.10.1 (ArcadeDB #8723, #8724, #8725), and run analytical reads outside a transaction #32
ArcadeData#8771 (26.10.1) fixed our ArcadeData#8723, ArcadeData#8724, and ArcadeData#8725, verified on an engine built from its merge 8a3cec6094 against 2fa02b3dde, both JDKs (replies on each issue). The queries guide is now stale in one place and silent in two:
"Ordered reads over an optional property" (from bindings docs: ordered reads need MANDATORY with NOTNULL, and Cypher reads the index in order only ascending (#26) #27) says openCypher reads the index in order only ascending, with no WHERE, and a default-null-strategy index, and advises a range for descending. From 26.10.1 it also reads it in order in both directions for a MANDATORY + NOTNULL property, under WHERE n.p IS NOT NULL, and for a NULL_STRATEGY INDEX index; only descending over a nullable property with the default index still scans. Luca's note: MANDATORY + NOTNULL is trusted and ALTER PROPERTY does not check earlier records, so declare them before loading.
A Cypher OR of equalities or IN lists on indexed properties now reads the indexes (340 to 430 ms -> 0.5 to 0.9 ms at 1M).
Filtered scans run in parallel in SQL and now Cypher, but only outside a transaction: measured 43 to 57 ms outside against 255 to 291 ms inside db.begin(), both languages, 1M records, 12 cores. Worth telling users to run analytical reads outside an explicit transaction.
Activity
bindings docs: Cypher ordered reads, OR, and parallel scans in 26.10.…