If you use manual batch-insertion you should insert your nodes first, then the relationships.
You can either set the cache size on the batch-inserter-index to a sensible number like 1 or 5M Or you just use a simple intermediate cache like a hashmap to store the index->node-id values. Michael Am 19.06.2014 um 09:27 schrieb Alex winter <[email protected]>: > Hi. > I need to import data to neo4j with around 10 millions nodes. > In the neo4j document: > http://docs.neo4j.org/chunked/milestone/indexing-batchinsert.html. > they have > Note > Changes to the index are available for reading first after they are flushed > to disk. Thus, for optimal performance, read and lookup operations should be > kept to a minimum during batchinsertion since they involve IO and impact > speed negatively. > > But in the process of importing data, I always need to check node is exist or > not, find node to create relationship. So what kind of batch insertion, index > I should use? > > THanks > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
