Roi Lipman
Roi Lipman
Neo4j version: 4.2.1 `docker run -p7474:7474 -p7687:7687 -e NEO4J_AUTH=neo4j/s3cr3t neo4j` Initial graph: `CREATE (:N {v:2}), (:N {v:1}), (:M {v:2}), (:M {v:3})` Query 1: `MATCH (n:N), (m:M) RETURN n.v + m.v...
Usage: `GRAPH.ALIAS ` A graph alias can be though of as file symbolic link TODO: Add documentation Handle graph schema change due to swap (client side)
Try to estimate graph key memory usage, please note this is just an estimation not an exact evaluation! we're still missing index memory consumption estimation in addition of a way...
This is an example of how we might be able to handle one of the common exceptions we encounter (invalid memory access) the API resembles the Try/Catch mechanism. The idea...
Neo [doc](https://neo4j.com/docs/cypher-manual/current/clauses/foreach/)
``` 127.0.0.1:6379> GRAPH.EXPLAIN g "MATCH (n) OPTIONAL MATCH (a), (b) RETURN *" 1) "Results" 2) " Project" 3) " Apply" 4) " All Node Scan | (n)" 5) " Optional"...
When there are multiple edge connecting `A` to `B` `MATCH (A:L0)-[r]->(B:L1) RETURN count(*)` Differs from `MATCH (A:L0)-[r]->(B:L1) RETURN count(r)` The latter would have count which is greater than the former,...
…s ready to commit
Free resources when failing to decode from RDB. Let Redis know we're able to handle this situation.