Bug when calling a procedure within a CALL { ... } sub-query #429
Labels
community
community
Effort - High
Effort - High
Frequency - Monthly
Frequency - Monthly
Priority - Later
Priority - Later
Reach - VeryFew
Reach - VeryFew
Severity - S3
Severity - S3
There appears to be a bug when calling any procedure within a CALL { ... } sub-query, in the context of a loop (where cardinality/rows are greater than 1). The error message received is: "Query failed: Procedure 'algo.all_simple_paths' did not yield all fields as required by its signature."
Example dataset:
Example queries that return error message:
It may be connected to the fact that
MATCH (user:User) RETURN user
returns three rows.Example dataset that work well:
The text was updated successfully, but these errors were encountered: