Hi, I'm one of the main authors of the import tool and I find this issue quite interesting.
Would you be able to share your dataset with me personally, for the single purpose of trying to find the root cause? On Friday, June 5, 2015 at 5:12:43 AM UTC+2, Zongheng Yang wrote: > > Hi all, > > I'm using neo4j-import to import nodes and relationships from csv files. > Let's say node id 538398 has about 100 edges and > > 538398 -> 370047 > 538398 -> 379981 > > are just two of them. After the import, the neo4j database actually > > - *loses* these two edges > - instead *corrupts* the destination ids, as follows > > 538398 -> 380047 > 538398 -> 389981 > > - *keeps* all other outgoing edges of 538398 correct > > The problem seems to be non-deterministic: doing a `rm -rf dbPath` and > re-running neo4j-import seems to fix the issue, for this particular node -- > but I've not done extensive tests to see whether other nodes get corrupted > in this way. > > Has anyone seen this before? The graph has on the order of 1 million node, > average degree 40. > > Zongheng > -- 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.
