Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.
I'm going through the materials here:
which refers to the step-by-step instructions here:
https://guides.neo4j.com/applied_graph_algorithms/02_category_hierarchy.html
It appears that the function algo.similarity.overlap()
has already been run on the Yelp DB. I see there are already relationships [:NARROWER_THAN]
prior to me running the function on the sandbox (as part of the exercise.)
Also...
The sandbox is running version Neo4J 3.5.17 which doesn't seem to be mentioned.
This is important as the new version seems to have a different function call:
CALL algo.similarity.overlap()
// takes a write parameter
vs.
CALL gds.alpha.similarity.overlap()
// actually, a separate write function
https://neo4j.com/docs/graph-data-science/1.5-preview/alpha-algorithms/overlap/
Also...
It appears that this has also been run on the YELP DB that's gets loaded into the SandBox.
MATCH (g1:Category)-[:NARROWER_THAN*2..]->(g3:Category),
(g1)-[d:NARROWER_THAN]->(g3)
DELETE d
The Browser reports that no changes were made.
Also... Running the last query before running the other overlap queries returns nodes, which definitely means the Yelp DB already has the overlap relationships precreated:
MATCH path = (category:Category)-[:NARROWER_THAN*]->(superCategory:Category)
RETURN path
LIMIT 10