PROFILE MATCH (p:Person)-[:HAS_JOB]->(j:Hobby)
RETURN p.name, j.name
If you execute the code above, the j node becomes an anchor
PROFILE MATCH (p:Person)-[:HAS_JOB]->(j)
RETURN p.name, j.name
If you execute the above code, node person becomes an anchor
There are 400 person nodes, 40 job nodes, much more person nodes
By what criteria will the anchors be determined?
Please understand that I used a translator
Yeah, but you have not specified the label of the 'j' node in the second query. All nodes in the database are candidates if the query starts with 'j'.
Can you provide the PROFILEs for each? I assume it depends on your database. I get a "directed relationship scan" as my first step for both variables, meaning it starts will all relationships of that type. I presume because I have no data with these labels nor "HAS_JOB" relationship type, thus it optimized that that approach.