Repository navigation
MERGE-created relationship is missing from the following OPTIONAL MATCH on row 101 #10515
Description
Environment
- Image:
arcadedata/arcadedb:latest - Image digest:
sha256:8783fe27ec732d36d5cab55fa2463a422ea79bf05a1b97892947fd2c2d84cb90 - Server: ArcadeDB
26.11.1-SNAPSHOT, buildb061c8904a99264366178fbadf08d86d4656428d/1792441435124/main - Execution: direct Bolt; start from an empty graph.
Description
After MERGE creates the relationship and ON CREATE SET changes its property, the following OPTIONAL MATCH should find that relationship for the current row. The added no-match OPTIONAL MATCH changes only the query plan, but row 101 changes from a missing binding to a concrete relationship-property map.
Setup
MATCH (n) DETACH DELETE nQuery A
UNWIND range(1, 101) AS i
MERGE (:A)-[r:rt8 {k11: 'before'}]->(n:N)
ON CREATE SET r.k11 = 'after'
OPTIONAL MATCH ()-[r3:rt8]->(n)
RETURN i, properties(r3) AS relationshipPropertiesQuery B
UNWIND range(1, 101) AS i
MERGE (:A)-[r:rt8 {k11: 'before'}]->(n:N)
ON CREATE SET r.k11 = 'after'
OPTIONAL MATCH (:Never)
WHERE false
WITH *
OPTIONAL MATCH ()-[r3:rt8]->(n)
RETURN i, properties(r3) AS relationshipPropertiesExpected
Both queries return 101 rows with equivalent values. For each row, the relationship created by MERGE is present and has relationshipProperties = {k11: 'after'}.
Actual
Both queries return 101 rows. Query A returns relationshipProperties = null for i = 101; Query B returns relationshipProperties = {k11: 'after'} for i = 101. A 100-row control returns equivalent results.
Activity
fix(#10512, #10513, #10515): batch-boundary sensitive writes after a …
lvca commentedon Oct 21, 2026
Fixed in #10549 (merged), shipping in 26.11.1.
Variables created by
MERGE/CREATEwere not treated as already bound by theMATCH/OPTIONAL MATCHafter them, so that clause scanned a stale snapshot and returned nothing from row 101 onward. It now starts from the node the earlier clause produced, which is also cheaper.Not covered: a fully unanchored
OPTIONAL MATCH ()-[r]->()after aMERGEover more than 100 rows can still return fewer rows than Neo4j. That needs a separate change.❤️ 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(#10512, #10513, #10515): batch-boundary sensitive writes after a …