Hmm good question, right now there is no (post-)duplication during the import.
If you do a manual import (using the parallelinserter for a Java API) you could keep the information in a hashmap and check against that. Perhaps you can just take the source code of ImportTool.java and adapt? Or use the normal BatchInserter API which is easy enough to use: http://neo4j.com/docs/stable/batchinsert-examples.html Cheers, Michael On Wed, Dec 10, 2014 at 8:30 AM, Максим Присяжнюк <[email protected]> wrote: > Good day! > I'm a beginner in Neo4j. > I have more than 300 million nods and 6 billion relationships in my base. > Relationships: e.g. NOD 2 knows NOD 12564, and so on. But NOD 12564 also > may to know NOD 2. In this case I have 2 equal relationships. > Please, give me advice. How to avoid duplicate relationships during import > base to Neo4j, using batchinserter. > May be some config exceptions? > I use Neo4j v. 2.2.0-M01. > > Thanks a lot for your reply! > > -- > 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.
