I\'m defining the relationship between two entities, Gene and Chromosome, in what I think is the simple and normal way, after importing the data from CSV:
MA
As logisima mentions in the comments, this is just a warning. Matching a cartesian product is slow. In your case it should be OK since you want to connect previously unconnected Gene
and Chromosome
nodes and you know the size of the cartesian product. There are not too many chromosomes and a smallish number of genes. If you would MATCH
e.g. genes on proteins the query might blow.
I think the warning is intended for other problematic queries:
MATCH
a cartesian product but you don't know if there is a relationship you could use OPTIONAL MATCH
MATCH
both a Gene
and a Chromosome
without any relationships, you should split up the queryIn case your query takes too long or does not finish, here is another question giving some hints how to optimize cartesian products: How to optimize Neo4j Cypher queries with multiple node matches (Cartesian Product)
The browser is telling you that:
Gene
instance and every Chromosome
instance. If your DB has G
genes and C
chromosomes, then the complexity of the query is O(GC)
. For instance, if we are working with the human genome, there are 46 chromosomes and maybe 25000 genes, so the DB would have to do 1150000
comparisons.You might be able to improve the complexity (and performance) by altering your query. For example, if we created an index on :Gene(chromosomeID)
, and altered the query so that we initially matched just on the node with the smallest cardinality (the 46 chromosomes), we would only do O(G)
(or 25000
) "comparisons" -- and those comparisons would actually be quick index lookups! This is approach should be much faster.
Once we have created the index, we can use this query:
MATCH (c:Chromosome)
WITH c
MATCH (g:Gene)
WHERE g.chromosomeID = c.chromosomeID
CREATE (g)-[:PART_OF]->(c);
It uses a WITH
clause to force the first MATCH
clause to execute first, avoiding the cartesian product. The second MATCH
(and WHERE
) clause uses the results of the first MATCH
clause and the index to quickly get the exact genes that belong to each chromosome.
[UPDATE]
The WITH
clause was helpful when this answer was originally written. The Cypher planner in newer versions of neo4j (like 4.0.3) now generate the same plan even if the WITH
is omitted, and without creating a cartesian product. You can always PROFILE both versions of your query to see the effect with/without the WITH
.