Thanks for reporting. This was a bug in encoding collision handling and has now been fixed. Any next release of 2.2 version will have this fix in it.
On Friday, December 5, 2014 1:50:06 PM UTC+1, Rene Rath wrote: > > Problem arises as soon as an ID exceeds the length of 128 characters. Up > to 128 chars, it seems to work fine. > > 2014-12-05 13:05 GMT+01:00 Rene Rath <rene.alex...@googlemail.com > <javascript:>>: > >> ... and same behaviour using the other argument syntax. >> >> ./neo4j-import --into /media/data/neo4j/test.db --nodes >> "/Users/d063333/tmp/neo4j_2.2/products_head2.csv >> /Users/d063333/tmp/neo4j_2.2/brands_head2.csv" --relationships >> /Users/d063333/tmp/neo4j_2.2/products2brands_head2.csv --id-type STRING >> --stacktrace >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Neo4j" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/neo4j/b1T66sf8oyY/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> neo4j+un...@googlegroups.com <javascript:>. >> 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 neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
