If a tool exists for converting 2.9->3.0.x, it would likely be faster. Do you know if such a tool exists? Remaking the index, in my case, can only be done from the existing index because the original data is no longer available (it is transient network data). I suppose an index 'remaker' might be something like a DIH reader for a Solr index - streams everything out of the existing index, writing it into the new one?
Peter On Fri, Sep 10, 2010 at 4:39 PM, Dennis Gearon <gear...@sbcglobal.net> wrote: > So converting an index would be faster than remaking it? > > Dennis Gearon > > Signature Warning > ---------------- > EARTH has a Right To Life, > otherwise we all die. > > Read 'Hot, Flat, and Crowded' > Laugh at http://www.yert.com/film.php > > > --- On Fri, 9/10/10, peter.stu...@gmail.com <peter.stu...@gmail.com> wrote: > >> From: peter.stu...@gmail.com <peter.stu...@gmail.com> >> Subject: No more trunk support for 2.9 indexes >> To: solr-user@lucene.apache.org >> Date: Friday, September 10, 2010, 8:20 AM >> Hi, >> >> I'm sure there are good reasons for the decision to no >> longer support 2.9 format indexes in 4.0, and not have an >> automatic upgrade as in previous versions. >> >> Since Lucene 3.0.2 is 'out there', does this mean the >> format is nailed down, and some sort of porting is >> possible? >> Does anyone know of a tool that can read the entire >> contents of a Solr index and (re)write it another? (as an >> indexing operation - eg 2.9 -> 3.0.x, so not repl) >> >> Thanks, >> Peter >> >
