Thanks Otis, but this is not my case. Most of my fields are not stored , but I do have the original data in case I need to reindex. My question is do I need to? If my 1.4.1 can be read by 3.1, I assume 3.1 can continue to write to it? In that case, I continue assuming that 4.0 will know how to read only the new segments, and if I optimize it, than I will have only one new segment, created by 3.1, thus readable by 4.0. It makes sense to me, the only question is if my guesses are right:-) Thanks.
On Friday, April 22, 2011, Otis Gospodnetic <otis_gospodne...@yahoo.com> wrote: > Hi Ofer, > > We recently helped a customer go through just such an upgrade (or maybe even > from 1.3.*). We used a tool that read data from one index and indexed it to > the > new index without having to reindex the data from the original sources. All > fields in the source index were obviously stored. :) > > Otis > ---- > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > Lucene ecosystem search :: http://search-lucene.com/ > > > > ----- Original Message ---- >> From: Ofer Fort <o...@tra.cx> >> To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> >> Sent: Fri, April 22, 2011 10:34:26 AM >> Subject: Re: Index upgrade from 1.4.1 to 3.1 and 4.0 >> >> Nobody? >> Am I the only one in need of upgrading an index that was created with 1.4.1? >> >> Thanks for any info >> Ofer >> >> On Friday, April 22, 2011, Ofer Fort <o...@tra.cx> wrote: >> > Hi all, >> > While doing some tests, I realized that an index that was created with >> > solr 1.4.1 is readable by solr 3.1, but nt readable by solr 4.0. >> > If I plan to migrate my index to 4.0, and I prefer not to reindex it >> > all, what would be my best course of action? >> > Will it be possible to continue to write to the index with 3.1? Will >> > that make it readable from 4.0 or only the newly created segments? >> > If I optimize it using 3.1, will that make it readable also from 4.0? >> > Thanks >> > Ofer >> > >> >
