apoc.algo.dijkstra: Failed to call procedure: RELATIONSHIP has no property with propertyKey

[neo4j-contrib]

apoc.algo.dijkstra: Failed to call procedure: RELATIONSHIP has no property with propertyKey

[jexp]

That's what dijkstraWithDefaultWeight is for.

apoc.algo.dijkstraWithDefaultWeight(startNode, endNode, 'KNOWS|<WORKS_WITH|IS_MANAGER_OF>', 'distance', 10) YIELD path, weight

[stdob]

Thank you, but I know about it. I think, nevertheless, it is not quite correct behavior of the procedure: it would be appropriate not to throw an exception if the property is not found, but reject (filter) this pattern (path).

In fact, the output will only include those paths in which every relationship has a property responsible for the weight, and this property is a number.

[jexp]

Ok, fair point.

[sarmbruster]

How about using dijekstraWtihDefaultWeight with a very high default value? This way the given relationship should never become a shortest path. Would this be good enough?

[jexp]

@stdob what do you think about @sarmbruster's suggestion?

[stdob]

@jexp Works, but, in my opinion, this is a workaround ...

[maxlazarus]

I agree, if there is no valid property with a numerical value this should fail properly and filter the path. High default weight is a bit of a hack.