Re: [Neo4j] Issue with lucene index

2011-03-14 Thread Axel Morgner
That would be great! Or Frankfurt? It's a little more central (but Berlin is ok for me, too) BTW: We should change the subject (it sounds so negative) ;-) Since I created the original post, I'll start a new thread. On 14.03.2011 13:02, Peter Neubauer wrote: > Berlin sounds great. > Last year a

Re: [Neo4j] Issue with lucene index

2011-03-14 Thread Peter Neubauer
Berlin sounds great. Last year a couple of guys met up at StudiVZ, and suddenly we were 30 people. Go for it, there is a LOT of good vibe in Beerlin! Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 LinkedIn   http://www.linkedin.com/in/neu

Re: [Neo4j] Issue with lucene index

2011-03-14 Thread Michael Hunger
They guys could create at least one in Malmö? Isn't Andreas there as well, and certainly some more fine folks? We can do one locally here in Gemany, perhaps Berlin (perhaps we can combine that with our monthly flight to CPH). Cheers Michael Am 14.03.2011 um 11:50 schrieb Jim Webber: > Hey Ri

Re: [Neo4j] Issue with lucene index

2011-03-14 Thread Jim Webber
Hey Rick, It was a pleasure to meet you too. And this got me thinking - it would be great to meet more folks from this list, or to form user groups, or generally just get a beer and talk Neo4j graphs. Is there, for example, a strong London contingent on this list? I only know me and Nat Pryce

Re: [Neo4j] Issue with lucene index

2011-03-13 Thread Rick Bullotta
PM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index Hi Rick, > That prompts two more questions: Any chance of backporting this to Neo4J > 1.2? If not, any rough estimate of the 1.3 release timetable? Full releases are every quarter, M05 is due next week, and the fol

Re: [Neo4j] Issue with lucene index

2011-03-13 Thread Jim Webber
Hi Rick, > That prompts two more questions: Any chance of backporting this to Neo4J > 1.2? If not, any rough estimate of the 1.3 release timetable? Full releases are every quarter, M05 is due next week, and the following release will be 1.3 GA. So you're looking at about 3 weeks. Jim

Re: [Neo4j] Issue with lucene index

2011-03-13 Thread Rick Bullotta
: Thursday, March 10, 2011 2:21 AM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index 2011/3/9 Rick Bullotta > Hi, Mattias. > > Is the ability to delete a node from a Lucene fulltext index "the old way" > (just provide node + key name) in M03 and M04? &g

Re: [Neo4j] Issue with lucene index

2011-03-10 Thread Mattias Persson
2011/3/10 Massimo Lusetti > On Wed, Mar 9, 2011 at 8:24 PM, Mattias Persson > wrote: > > > Correct, and go with the M03 milestone first because M04 will > > introduce changes which requires an upgrade from a cleanly shut down > > database. > > Not so gentle from yours to force an upgrade from M0

Re: [Neo4j] Issue with lucene index

2011-03-10 Thread Massimo Lusetti
On Wed, Mar 9, 2011 at 8:24 PM, Mattias Persson wrote: > Correct, and go with the M03 milestone first because M04 will > introduce changes which requires an upgrade from a cleanly shut down > database. Not so gentle from yours to force an upgrade from M03 to M04 sir... ;-) did it will take a lon

Re: [Neo4j] Issue with lucene index

2011-03-09 Thread Mattias Persson
rom: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] > On Behalf Of Mattias Persson > Sent: Wednesday, March 09, 2011 2:24 PM > To: Neo4j user discussions > Subject: Re: [Neo4j] Issue with lucene index > > Den onsdagen den 9:e mars 2011 skrev David > Montag

Re: [Neo4j] Issue with lucene index

2011-03-09 Thread Rick Bullotta
Wednesday, March 09, 2011 2:24 PM To: Neo4j user discussions Subject: Re: [Neo4j] Issue with lucene index Den onsdagen den 9:e mars 2011 skrev David Montag: > Alex, > > That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to > the latest milestone, you will no lon

Re: [Neo4j] Issue with lucene index

2011-03-09 Thread Axel Morgner
Upgraded to 1.3.M03, issue is gone. Thanks a lot! Axel Am 09.03.2011 20:24, schrieb Mattias Persson: > Den onsdagen den 9:e mars 2011 skrev David > Montag: >> Alex, >> >> That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to >> the latest milestone, you will no longer get

Re: [Neo4j] Issue with lucene index

2011-03-09 Thread Mattias Persson
Den onsdagen den 9:e mars 2011 skrev David Montag: > Alex, > > That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to > the latest milestone, you will no longer get this exception. Also, the > latest milestone will recover the store to a clean state. Your data will be > safe.

Re: [Neo4j] Issue with lucene index

2011-03-09 Thread David Montag
Alex, That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to the latest milestone, you will no longer get this exception. Also, the latest milestone will recover the store to a clean state. Your data will be safe. David On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner wrote:

[Neo4j] Issue with lucene index

2011-03-09 Thread Axel Morgner
Hi out there, is there a caveat when concurrently accessing a lucene index for writing? From time to time, in rare cases, I'm getting an exception when committing and indexing a series of nodes to Neo4j (1.2). The transaction is triggered by a log service thread while the main thread (web app