When upgrading Solr from 1.x to 3.x it is *highly* recommended to re-index your data.
The tool Uwe is referring to is a low level, advanced tool -- it *may* work to get your index updated, but unless you really know the inner workings of things I would strongly suggest just reindexing. On Fri, Jun 3, 2011 at 2:33 PM, <johnmu...@aol.com> wrote: > I'm confused. So, if I'm upgrading from Solr 1.2 to 3.2 and I don't change > my <analyzer type="index"> and <analyzer type="query"> sections, I don't > have to re-index my data?! I was told otherwise (i'm trying to find that > post) because the analyzers have changed. In case it matters, i'm using > EnglishPorterFilterFactory. > > > -JM > > -----Original Message----- > From: Uwe Schindler <u...@thetaphi.de> > To: dev@lucene.apache.org > Sent: Fri, Jun 3, 2011 12:04 pm > Subject: RE: tentative! release notes drafts > > You must only reindex, if you *change* the Analyzers to different ones. If > you keep the old schemas and ensure that tokenizer luceneMatchVersion > settings keep alive, you don’t need to. > > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > From: johnmu...@aol.com [mailto:johnmu...@aol.com] > Sent: Friday, June 03, 2011 5:01 PM > To: dev@lucene.apache.org > Subject: Re: tentative! release notes drafts > > So, in my case, upgrading from Solr 1.2 to 3.2, I must re-index. OK, I got > that, thanks. > > Btw, where can I learn more about the "new IndexUpgrader tool"? Is there a > doc/wiki for it? > > -JM > > -----Original Message----- > From: Uwe Schindler <u...@thetaphi.de> > To: dev@lucene.apache.org > Sent: Fri, Jun 3, 2011 10:52 am > Subject: RE: tentative! release notes drafts > Hi, > > When analyzers change behavior you have to reindex, there is no way around. > The index-upgrader tool simply rewrites index segments to the new file > format, but does not change contents. > > Uwe > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > From: johnmu...@aol.com [mailto:johnmu...@aol.com] > Sent: Friday, June 03, 2011 4:47 PM > To: dev@lucene.apache.org > Subject: Re: tentative! release notes drafts > > Hi, > > Looking at http://wiki.apache.org/lucene-java/ReleaseNote32, the item: > > * A new IndexUpgrader tool fully converts an old index to the > current format. > Where can I learn more about this? Is this for upgrading the Lucene index > from Lucene 2.1 to 3.2 due to the analyze change? > > My question is around the fact that an index created using Solr 1.2 is not > compatible with Solr 3.2, and I'm trying to see if the above will solve my > problem or must I re-index. > > Thanks in advanced !!! > > -JM > > -----Original Message----- > From: Robert Muir <rcm...@gmail.com> > To: dev@lucene.apache.org > Sent: Thu, Jun 2, 2011 7:02 pm > Subject: tentative! release notes drafts > > Hello, > > > > While we await the results of the vote (72 hours), I thought it would > > be good to propose something new for the release emails, by putting > > something up on the wiki where anyone can just edit it. In the past, > > we would email each other back and forth and I think that's not the > > easiest way to build up a document. > > > > So, if you are motivated, please review and improve: > > > > http://wiki.apache.org/lucene-java/ReleaseNote32 > > http://wiki.apache.org/solr/ReleaseNote32 > > > > Again, this is a little premature and tentative since the vote still > > has not passed, but it looks like it stands a good chance of doing so, > > and it would be good to incorporate more feedback... these little > > "marketing"-type things probably deserve more attention than we > > normally give them. > > > > Also for discussion: for the next release, we could consider copying > > the templates to ReleaseNote33 and make these live documents that we > > edit as we work towards the release, instead of at the end (we could > > always fix them up at the end too). So if we add a really huge feature > > we could add it when its actually committed. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
