Thanks! I haven't been able to do any real testing against 2.2 yet due to the
couple of issues I've hit. Any way I could get a new build prior to the GA
release?
Sent from my iPhone
On Mar 12, 2015, at 7:09 AM, Mattias Persson
mailto:matt...@neotechnology.com>> wrote:
Hi, I've found and fixed
I'm trying to use the Neo4j 2.1.5 regex matching in Cypher and running into
problems.
I need to implement a full text search on specific fields that a user has
access to. The access requirement is key and is what prevents me from just
dumping everything into a Lucene instance and querying that
t;> More info is in the online docs here:
>>
>> http://docs.neo4j.org/chunked/stable/deployment-upgrading.html
>>
>> Hope this helps
>> dave fauth
>>
>> On Wednesday, August 6, 2014 9:11:03 PM UTC-4, Bill Scheidel wrote:
>>>
>>> Hi Mic
Bill,
>
> could you share your full messages.log file? And please keep the db around.
> Can you work around by using 2.1.2 on your server while we look at the
> issue?
>
> Thanks so much.
>
>
> On Wed, Aug 6, 2014 at 9:27 PM, Bill Scheidel > wrote:
>
>> Just n
is version 'NeoStore v0.A.3'.
2014-08-06 19:13:13.104+ INFO [o.n.k.EmbeddedGraphDatabase]: Shutdown
started
On Wednesday, August 6, 2014 11:23:23 AM UTC-7, Bill Scheidel wrote:
>
> I'm trying to copy over a database that I've been using with Neo4j 2.1.2
> to a
I'm trying to copy over a database that I've been using with Neo4j 2.1.2 to
a new machine that is running Neo4j 2.1.3. I shut down my 2.1.2 server and
made sure it was a clean shutdown. I then copied over the graph.db
directory to my new server and chown'd the files to the neo4j user.
However
Looks like you just need to remove the MATCH statement now. WHERE can
immediately follow WITH.
On Thursday, June 26, 2014 5:11:43 PM UTC-7, Bill Scheidel wrote:
>
> I recently upgraded from Neo4j 2.0.1 and immediately hit this new error:
>
>
> {Code:"Neo.ClientError.Sta
match (c: Client)-[WORKS_FOR]->(co: Company) return c, co limit 10
This query is doing a full graph lookup and capturing 100's of millions of
results and then only returning 10 of them. This will never return with
Neo4j. You need to pick a starting point in your graph and start executing
quer
I ran into this same problem trying to upgrade from 2.0.1 to 2.1.2.
On Tuesday, June 24, 2014 1:52:46 AM UTC-7, Denys Hryvastov wrote:
>
> Ok,
>
> After having an email thread with neo4j support team (thanks them for
> quick and full responses for all my questions) I have decided to use
> neo4
I recently upgraded from Neo4j 2.0.1 and immediately hit this new error:
{Code:"Neo.ClientError.Statement.InvalidSyntax", Message:"Cannot match on a
pattern containing only already bound identifiers (line 26, column 3)\n\"
MATCH (m)\"\n ^"},
I didn't see this new incompatibility in the rel
I've set up a Graph gist at http://gist.neo4j.org/?9494429e3cbbbeda2b11
which is one example of the types of queries I'm trying to do.
I have lots of queries where I want to collect information from related
nodes, where the relationships are optional. Even with small databases
(10's of thousan
t;
>> https://github.com/jexp/neo4j-in-memory-server
>>
>> Cheers
>>
>> Michael
>>
>> Am 17.01.2014 um 02:52 schrieb Michael Hunger <
>> michael...@neopersistence.com >:
>>
>> Good question, not sure about that.
>>
>> Indexi
So during your tx whenever things are changed / created that correspond to
> the configured auto-indexing properties they are written to the index.
>
> Michael
>
> Am 17.01.2014 um 02:35 schrieb Bill Scheidel
> >:
>
> Hmm... turning off node_auto_indexing drops it from 150m
Hmm... turning off node_auto_indexing drops it from 150ms to 40ms. Why
would auto indexing block a request?
On Thursday, January 16, 2014 5:07:48 PM UTC-8, Bill Scheidel wrote:
>
> My hdparm results are 118 MB/sec which isn't horrible, but it seems like
> disk latency is the o
RAM, using Neo4j stock settings.
>
> Wes
>
> On Thu, Jan 16, 2014 at 7:08 PM, Bill Scheidel
> > wrote:
>
>> Yeah, definitely not great. Odd though since I never had a problem when
>> working with Postgres or Mongo and they force things to disk as well.
>> N
t; 11 requests completed in 10.2 s, 32.1 k iops, 125.3 mb/s
> min/avg/max/mdev = 21 us / 31 us / 50 us / 7 us
>
> w ab
> 29 requests completed in 29.0 s, 33.1 k iops, 129.3 mb/s
> min/avg/max/mdev = 20 us / 30 us / 109 us / 17 us
>
> Am 17.01.2014 um 00:54 schrieb Bill Sc
And this is ioping without the ab test running:
31 requests completed in 30.5 s, 3.2 k iops, 12.5 mb/s
min/avg/max/mdev = 190 us / 312 us / 477 us / 63 us
On Thursday, January 16, 2014 3:51:32 PM UTC-8, Bill Scheidel wrote:
>
> I ran vmstat while running the ab test:
>
> procs -
I ran vmstat while running the ab test:
procs ---memory-- ---swap-- -io -system--
cpu
r b swpd free buff cache si sobibo in cs us sy id
wa
0 1 0 2429284 161572 2133284002275 98 354 9 8
80 2
I also ran ioping
I posted this on StackOverflow but thought I would put here as well in case
anybody has any ideas. Creating 2 nodes and one relationship in an empty
database is taking 150ms to 170ms. This is making it really hard to run
unit tests efficiently so I'm looking for any suggestions to speed things
19 matches
Mail list logo
