Re: [Neo] Lucene version

2009-11-25 Thread Tobias Ivarsson
This is a serious bug. Thanks for finding it. Apparently the remote-neo jar contains ALL the classes of its dependencies. My guess is that this problem was introduced in revision 2980 when the packaging changed from jar to bundle. I'll get on to fixing it later today. /Tobias On Tue, Nov 24, 2

Re: [Neo] Lucene version

2009-11-24 Thread Jakub Kotowski
Mattias Persson schrieb: > Thanks, there seems to be some known problems with lucene on NFS. If > you're calling getNodes on a non-existing index then I committed a fix Yes, it's a getNodes call on non-existing index. > for that (added one extra null check), but if that index should exist > it co

Re: [Neo] Lucene version

2009-11-18 Thread Mattias Persson
Thanks, there seems to be some known problems with lucene on NFS. If you're calling getNodes on a non-existing index then I committed a fix for that (added one extra null check), but if that index should exist it could just be that lucene is having trouble with NFS. I'll look into this further to

Re: [Neo] Lucene version

2009-11-18 Thread Jakub Kotowski
Mattias Persson schrieb: >>> After playing with it more, the culprit seems to be not the symbolic >>> link but the local drive :-/ When I delete the neo4j directory with the >>> db and start the application from the local drive then I'm getting the >>> NPEs - even if I shut the server down and star

Re: [Neo] Lucene version

2009-11-18 Thread Mattias Persson
>> After playing with it more, the culprit seems to be not the symbolic >> link but the local drive :-/ When I delete the neo4j directory with the >> db and start the application from the local drive then I'm getting the >> NPEs - even if I shut the server down and start it again. When I delete >>

Re: [Neo] Lucene version

2009-11-17 Thread Jakub Kotowski
Jakub Kotowski schrieb: > Jakub Kotowski schrieb: >> Mattias Persson schrieb: >>> I updated the version and corrected some tests which were troublesome >>> with the new version so it should be available in index-util (version >>> 0.9-SNAPSHOT) within an hour. >>> >>> It'd be great if you could repo

Re: [Neo] Lucene version

2009-11-17 Thread Jakub Kotowski
Jakub Kotowski schrieb: > Mattias Persson schrieb: >> I updated the version and corrected some tests which were troublesome >> with the new version so it should be available in index-util (version >> 0.9-SNAPSHOT) within an hour. >> >> It'd be great if you could report back about any encountered pr

Re: [Neo] Lucene version

2009-11-17 Thread Jakub Kotowski
Mattias Persson schrieb: > I updated the version and corrected some tests which were troublesome > with the new version so it should be available in index-util (version > 0.9-SNAPSHOT) within an hour. > > It'd be great if you could report back about any encountered problem! Thanks again for the q

Re: [Neo] Lucene version

2009-11-12 Thread Mattias Persson
I updated the version and corrected some tests which were troublesome with the new version so it should be available in index-util (version 0.9-SNAPSHOT) within an hour. It'd be great if you could report back about any encountered problem! / Mattias 2009/11/12 Jakub Kotowski : > Mattias Persson

Re: [Neo] Lucene version

2009-11-12 Thread Jakub Kotowski
Mattias Persson schrieb: > Yep, I'm looking at it right now and I think it's a minor operation to > do... I'll let you know! Great and thanks for the fast answer! Jakub > > 2009/11/12 Jakub Kotowski : >> Hi, >> >> I'm new to Neo4j and I'm trying to use it in our project where we >> already are

Re: [Neo] Lucene version

2009-11-12 Thread Mattias Persson
Yep, I'm looking at it right now and I think it's a minor operation to do... I'll let you know! 2009/11/12 Jakub Kotowski : > Hi, > > I'm new to Neo4j and I'm trying to use it in our project where we > already are using lucene-core-2.9.1.jar. The problem is that when using > this jar version I'm g

[Neo] Lucene version

2009-11-12 Thread Jakub Kotowski
Hi, I'm new to Neo4j and I'm trying to use it in our project where we already are using lucene-core-2.9.1.jar. The problem is that when using this jar version I'm getting a NullPointerException upon a call to indexService.getSingleNode(). This does not happen with the lucene-core-2.4.0.jar library