[Neo4j] Re: Neo4j jmeter test

2014-12-05 Thread Daniel Alvarado
Hi, I'd like to know how were you running your tests, did you use any driver to connect your neo4j DB to JMeter? Cheers. On Tuesday, April 3, 2012 8:26:06 PM UTC-6, metamoi wrote: > > I ran the Apache JMeter of neo4j. > The number of nodes is about 7,300,000, properties are 41,000,000 and > re

Re: [Neo4j] Re: Import tool - stillExecuting errormessage

2014-12-05 Thread 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. 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 1

Re: [Neo4j] Re: large cypher statements

2014-12-05 Thread José F . Morales
Hey M, Just to make sure... i have my Node csv which has columns for labels. One label is DESC. The DESC column has two values... "s" and "t". The Node csv file has 18k nodes, 146 of which have the "s" label and the rest have the "t" label. Since I created relationships between "s" and

[Neo4j] neo4j-import - error message format is bad

2014-12-05 Thread Rene Rath
When a list of node or relationship files is specified on the command line, and the command fails (e.g. because some start node has not been imported, but is used in a relationship), then the resulting message is very hard to read. This is what I currently get: Calculate dense nodes Import er

Re: [Neo4j] Re: Script to migrate relational DB to Neo4j

2014-12-05 Thread Ioannis Theodossis
Thank you all! :) Michael, blogpost + screencast. OK! Just give me some time, and I'll do it. Now, dump.sql to csv files, this is a great idea. What really concerns me, though, is parsing SQL. While it will not take an elaborated SQL parser (it would need only a subset of sql commands), it's de

Re: [Neo4j] Re: Import tool - stillExecuting errormessage

2014-12-05 Thread 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 : > ... and same behaviour using the other argument syntax. > > ./neo4j-import --into /media/data/neo4j/test.db --nodes > "/Users/d06/tmp/neo4j_2.

[Neo4j] Re: Import tool - stillExecuting errormessage

2014-12-05 Thread Rene Rath
... and same behaviour using the other argument syntax. ./neo4j-import --into /media/data/neo4j/test.db --nodes "/Users/d06/tmp/neo4j_2.2/products_head2.csv /Users/d06/tmp/neo4j_2.2/brands_head2.csv" --relationships /Users/d06/tmp/neo4j_2.2/products2brands_head2.csv --id-type STRING

[Neo4j] Re: Import tool - stillExecuting errormessage

2014-12-05 Thread Rene Rath
Mac OS X 10.9.5 by the way... -- 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/op

[Neo4j] Import tool - stillExecuting errormessage

2014-12-05 Thread 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/d06/tmp/neo4j_2.2/products_head2.csv --

[Neo4j] [ANN] Neo4j Spatial for 2.2.0-M01

2014-12-05 Thread Axel Morgner
Hi, just uploaded a new version of Neo4j Spatial to https://github.com/neo4j-contrib/m2/tree/master/releases/org/neo4j/neo4j-spatial/0.14-neo4j-2.2.0-M01, so you can test it with the brand-new milestone of Neo4j 2.2 (2.2.0-M01). There are Spatial versions for 2.1.5 and 2.1.6 also. Cheers,

[Neo4j] Re: Problems with first step of the batch-import tool

2014-12-05 Thread Rene Rath
not really an answer, but a nudge: with Neo4j 2.2 Milestone 1, which was released this week, the batch-insert tool got integrated. You might want to take a look at this: http://neo4j.com/docs/milestone/import-tool.html Am Mittwoch, 17. September 2014 13:23:40 UTC+2 schrieb Curtis Mosters: > > I