Neo4j

brandon · 02-19-2021

Small bug-ish thing: in the new Desktop, when I take a 3.5.x database, upgrade to 4.2.x, APOC is still installed as 3.5.x. The right column for plugins still shows APOC compatible version as 3.5.x instead of 4.x APOC. Neo4j 4 cant start with APOC 3.x...

brandon · 06-08-2021

The growth is transaction logs. They will rotate out and delete according to the transaction log rotation policy in the neo configs. Transaction logs contain the data you’re sending in the database. So even if you are throwing the same data at it to ...

brandon · 03-12-2021

Sure! Having indexes allows neo to quickly lookup their array index for specific nodes in memory. In neo, setting a node property constraint will automatically create an index for that property in the DB for you. Every query for 1 specific node ( be ...

brandon · 03-11-2021

Speed that up with indexing nodes. If you have at least one constraint on a node type mapped to a primary key. Set the constraint using cypher on that prop, and it gets faster.

brandon · 02-22-2021

Actually found the issue reported in 2019. Just added that its still an issue but the errors in Neo4j 4.x are different now. github.com/neo4j-devtools/neo4j-desktop DB Upgrade doesn't upgrade APOC which DB...

Neo4j

User Statistics

User Activity

3.5.x Desktop Upgrade to 4.2.x shows APOC compatible version as 3.5.x

Re: Store Size Always Growing?

Re: How do I use LOAD CSV for this scenario

Re: How do I use LOAD CSV for this scenario

Re: 3.5.x Desktop Upgrade to 4.2.x shows APOC compatible version as 3.5.x