Import tool - stillExecuting errormessage

[Rene Rath]

Now that the import tool became a regular feature of neo4j (2.2 Milestone 1), I gave it a go and ran into problems pretty early on. When I try to import the attached files, I get an error:

./neo4j-import --into /media/data/neo4j/test.db --nodes /Users/d063333/tmp/neo4j_2.2/products_head2.csv --nodes /Users/d063333/tmp/neo4j_2.2/brands_head2.csv --relationships /Users/d063333/tmp/neo4j_2.2/products2brands_head2.csv --id-type STRING --stacktrace 

Nodes

Import error: Failure:[1] 14e97a7f652be887:4449eead7c7422cf | 715130:2247150

java.lang.RuntimeException: Failure:[1] 14e97a7f652be887:4449eead7c7422cf | 715130:2247150

at org.neo4j.unsafe.impl.batchimport.staging.StageExecution.stillExecuting(StageExecution.java:54)

at org.neo4j.unsafe.impl.batchimport.staging.PollingExecutionMonitor.anyStillExecuting(PollingExecutionMonitor.java:71)

at org.neo4j.unsafe.impl.batchimport.staging.PollingExecutionMonitor.finishAwareSleep(PollingExecutionMonitor.java:94)

at org.neo4j.unsafe.impl.batchimport.staging.PollingExecutionMonitor.monitor(PollingExecutionMonitor.java:62)

at org.neo4j.unsafe.impl.batchimport.ParallelBatchImporter.executeStages(ParallelBatchImporter.java:221)

at org.neo4j.unsafe.impl.batchimport.ParallelBatchImporter.doImport(ParallelBatchImporter.java:138)

at org.neo4j.tooling.ImportTool.main(ImportTool.java:212)

Caused by: java.lang.IllegalStateException: Failure:[1] 14e97a7f652be887:4449eead7c7422cf | 715130:2247150

at org.neo4j.unsafe.impl.batchimport.cache.idmapping.string.EncodingIdMapper.detectAndMarkCollisions(EncodingIdMapper.java:185)

at org.neo4j.unsafe.impl.batchimport.cache.idmapping.string.EncodingIdMapper.prepare(EncodingIdMapper.java:121)

at org.neo4j.unsafe.impl.batchimport.NodeEncoderStep.done(NodeEncoderStep.java:124)

at org.neo4j.unsafe.impl.batchimport.staging.AbstractStep.checkNotifyEndDownstream(AbstractStep.java:204)

at org.neo4j.unsafe.impl.batchimport.staging.ExecutorServiceStep$2.run(ExecutorServiceStep.java:96)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.run(FutureTask.java:262)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)

at org.neo4j.helpers.NamedThreadFactory$2.run(NamedThreadFactory.java:99)

When I tried the import with some manually created (and therefore somewhat simpler) files, it went through. Is there something wrong with the data? Are the strings too long? Is it a concurrency problem? I am aware that this milestone is not bug-free. I'm just posting this to find out if it is something I can fix myself. Cheers!

[Rene Rath]

Mac OS X 10.9.5 by the way...

[Rene Rath]

... 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 

[Rene Rath]

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>:

... 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.
For more options, visit https://groups.google.com/d/optout.

[Mattias Persson]

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.