Repository navigation
path.combine rejects its documented two-argument signature #10017
Description
Environment
- ArcadeDB image:
arcadedata/arcadedb:latest - Server version:
26.11.1-SNAPSHOT - Build:
3c83e87406ebd52c256a26f93aeba64ebf553c74/1791967609866/main - Image ID/digest:
sha256:2afd99153a98e2e65383da7b35b06ddc0f060d46cf3b36abf073f610b65017cc
Reproduction
Run the setup, then run the query over Bolt:
CREATE (a:N {id: 1})-[:R]->(b:N {id: 2})-[:R]->(c:N {id: 3})MATCH p1 = (a:N {id: 1})-[:R]->(b:N {id: 2}),
p2 = (b)-[:R]->(c:N {id: 3})
RETURN path.combine(p1, p2) AS combinedThe paths share their endpoint/startpoint b. The documented function
signature is path.combine(path1, path2):
ArcadeDB Path & Algorithm Procedures.
Expected result
One record containing the combined path a → b → c (node IDs 1, 2, 3 and
both R relationships).
Actual result
The query fails before returning a record:
Neo.ClientError.Statement.SemanticError:
Function 'path.combine' expects 1 argument but got 2
Activity
lvca commentedon Oct 14, 2026
Fixed in #10033, available in 26.11.1.
path.combine(path1, path2)now works as documented (the APOC signature). The second path must start where the first one ends, otherwise you get a clear error. If one of the paths isnull, the other one is returned. Your query now returns the combined patha -> b -> c.All the other
path.*functions now accept a path bound byMATCH p = ...and return a real path, sonodes(),relationships(),length()and the drivers work on their result.path.create(start, [rels])now also adds the nodes along the relationships; before, it kept only the start node.❤️ 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: twin lightweight edges in =, DISTINCT and DELETE, path.combine(p…
fix: twin lightweight edges in =, DISTINCT and DELETE, path.combine(p…