You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just pushed a fix for this on branch 2.2.x (porting it to develop).
Just a couple of notes:
The fix is just an optimization, the old algorithm used an inefficient API to retrieve neighbor vertices.
Please, use the following as a query
SELECT dijkstra(#40:55, #33:0, 'Score')
instead of
SELECT dijkstra(#40:55, #33:0, 'Score') from V
you definitely don't need the from V here.
On my machine it's still much slower than a simple ShortestPath (it takes a few minutes to execute), but the algorithm of a weighted path is more complex than a simple shortestPath, so it makes sense
OrientDB Version, operating system, or hardware.
Operating System
Expected behavior
comparing with another function ...
orientdb {db=HumanPPI2}> SELECT shortestPath(#40:55,#33:0)
+----+---------------------------+
|# |shortestPath |
+----+---------------------------+
|0 |[#40:55,#34:133,#33:0]|
+----+----------------------------+
1 item(s) found. Query executed in 0.078 sec(s).
Actual behavior
orientdb {db=HumanPPI2}> SELECT dijkstra(#40:55, #33:0, 'Scale') FROM V
never returns- now 30 minutes, and counting...
Steps to reproduce the problem
download my database from google disk and check. please request share.
The text was updated successfully, but these errors were encountered: