CODEWITHSUNDEEP
neo4j
Jakub Licznerski
Jakub Licznerski

Reputation: 1088

Neo4j Graph Algorithms no procedure with the name algo.nodeSimilarity

I wanted to test some graph algorithms, node similarity in particular. So I've setup a docker container using neo4j:3.5 (which is v3.5.14 at the moment) official docker image. Additionally I've downloaded APOC v3.5.0.7 and Graph Algorithms v3.5.4.0 and added this line to the config:

dbms.security.procedures.unrestricted=algo.*

Unfortunately function algo.nodeSimilarity seems not to be present in the registered functions:

CALL algo.nodeSimilarity('Node', 'LABEL', {})
YIELD nodesCompared, relationships, write, writeRelationshipType, writeProperty

yields

There is no procedure with the name algo.nodeSimilarity registered for this database instance. Please ensure you've spelled the procedure name correctly and that the procedure is properly deployed.

Also call dbms.procedures nor call algo.list() does not show nodeSimilarity. The other functions from APOC (e.g. pageRank) and Graph Algorithms (e.g. louvain) are installed and work as expected.

As I can see in the docs, the algo.nodeSimilarity should be present since v3.5. So I'm pretty much confused with this error. Would this be more suitable question for the Github Issues page on Graph Algorithms plugin repo?

Upvotes: 0

Views: 5038

Answers (1)

Pablissimo
Pablissimo

Reputation: 2905

The Github repo for the Graph Algorithms plugin doesn't seem to actually be up to date - the latest version of the plugin is 3.5.14, available from the download centre which definitely contains the algo.nodeSimilarity algorithm. There are other versions available - this JSON file contains all the variants which isn't super discoverable.

The docs are a bit odd in that they claim everything is in v3.5, but don't say exactly which revision of 3.5 they appeared in. I can't tell when algo.nodeSimilarity appeared, but I'm using 3.5.13 in my 3.5.13 database and it's present there at least.

It doesn't appear that the Graph Algorithms library uses any form of semantic versioning, and I have yet to find a source for the historic release notes version-by-version.

Upvotes: 2

Related Questions