, 2014 at 1:21 PM, Mattias Persson matt...@neotechnology.com
wrote:
Yup looks like a bug to me. I'm one of the authors of that algo
implementation, so I'll see if I can have a look at it soon.
On Tue, Sep 16, 2014 at 7:17 PM, Jatin Puri purija...@gmail.com wrote:
There is a bug https://github.com
There is a bug https://github.com/neo4j/neo4j/issues/2987 in
GraphAlgoFactory (trivial but never the less irritating). Basically if you
try finding a single shortest path from a node to itself, it gives
following behavior:
Using `GraphAlgoFactory.astar`, it throws:
This is a consistent behavior since a loong time. I think its a bug.
When you try finding a path from a node to itself using `astar` it throws
exception when it should just return null. To verify:
import org.neo4j.graphalgo.*;
import org.neo4j.graphdb.*;
import
Oops incomplete question. It throws below exception:
Exception in thread main org.neo4j.graphdb.NotFoundException:
Relationship -1 not found
79
at
org.neo4j.kernel.InternalAbstractGraphDatabase.getRelationshipById(InternalAbstractGraphDatabase.java:1175)
at
Am 03.09.2014 um 20:50 schrieb Jatin Puri puri...@gmail.com javascript:
:
Oops incomplete question. It throws below exception:
Exception in thread main org.neo4j.graphdb.NotFoundException:
Relationship -1 not found
79
at
org.neo4j.kernel.InternalAbstractGraphDatabase.getRelationshipById
