Re: [Neo4j] upgrade 1.4 -> 1.4.1 losses indexes

2011-08-22 Thread Mattias Persson
I think lucene stores indices in a machine-specific (or at least OS/architecture-specific) way so moving indices over may not work. 2011/8/21 Boris Kizelshteyn > update ... it doesn't seem to be an upgrade issue: I moved my datastore to > a > new server of the same version (1.4) and it can't sea

Re: [Neo4j] upgrade 1.4 -> 1.4.1 losses indexes

2011-08-22 Thread Peter Neubauer
Mmh, that is strange. Are you sure you are even moving the graph.db subdirectories (the indexes are nested under the database dir), and they have write permissions for your new server? Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 Linked

Re: [Neo4j] upgrade 1.4 -> 1.4.1 losses indexes

2011-08-20 Thread Boris Kizelshteyn
update ... it doesn't seem to be an upgrade issue: I moved my datastore to a new server of the same version (1.4) and it can't search the index either, I moved teh graph.db dir, do I need to move something else? Thanks! On Sat, Aug 20, 2011 at 6:13 PM, Boris Kizelshteyn wrote: > Howdy, > > I ju

[Neo4j] upgrade 1.4 -> 1.4.1 losses indexes

2011-08-20 Thread Boris Kizelshteyn
Howdy, I just tried to move my 1.4 datastore to 1.4.1 and I can start up the db and see my nodes, relationships and indexes, but I can't search the indexes. I tried this on mac and linux and verified the installations (started default datatstore). Any thoughts? Thanks! ___