For what it's worth, the only changes that I've had to deal with so far are:
* Certain Tokenizer/Analyzer methods have to be final. < https://issues.apache.org/jira/browse/LUCENE-2389> * A PhraseQuery behavior change if your first term is at offset > 0. (Haven't tracked down bug for that.) * FieldDoc.fields returns Object[] instead of Comparable[]. < https://issues.apache.org/jira/browse/LUCENE-3191> With that, all of my code compiles and all of my tests pass; really, it's been a quite smooth transition, I'm impressed. There are still some deprecation warnings that I want to fix (TermAttribute -> CharTermAttribute <https://issues.apache.org/jira/browse/LUCENE-2302>, IndexWriter constructors <https://issues.apache.org/jira/browse/LUCENE-2294>), but in total it's less than a day's work. (3.0.1 -> 3.0.3 actually had me pulling out my hair a bit more with the change from < https://issues.apache.org/jira/browse/LUCENE-2387>.) On Thu, Jan 19, 2012 at 9:25 PM, Ganesh <emailg...@yahoo.co.in> wrote: > > I am also in the way to upgrade from 3.0.3 to 3.5. Any other API changes > we need to care about? I use ParallelMultiSearcher. > > Regards > Ganesh > > > > ----- Original Message ----- > From: "Uwe Schindler" <u...@thetaphi.de> > To: <java-user@lucene.apache.org> > Sent: Friday, January 20, 2012 5:18 AM > Subject: [Bulk] RE: any tips for upgrading Lucene 3.0.3 -> 3.5.0? > > > > -----Original Message----- > > From: earlh...@gmail.com [mailto:earlh...@gmail.com] On Behalf Of Earl > > Hood > > Sent: Friday, January 20, 2012 12:41 AM > > To: java-user@lucene.apache.org > > Subject: Re: any tips for upgrading Lucene 3.0.3 -> 3.5.0? > > > > On Thu, Jan 19, 2012 at 4:59 PM, Uwe Schindler <u...@thetaphi.de> wrote: > > > Lucene 3.5 can read any index going back to 2.0. The IndexUpgrader is > > > only needed to "forcefully" upgrade indexes for maximum performance > > > and safe migration to Lucene 4.0 (that can only read indexs >= 3.0). > > > > Question: Will Lucene 3.5 automatically upgrade an older index when it is > > opened? > > > > Just clarifying if actual index data on disk is changed automatically or > if an > > explicit operations must be done. > > No it will not, all index segments keep as they are. They are only > upgraded to the new format once they are merged to new segments (when e.g. > adding new docs and a merge is triggered). The IndexUpgrader is simply a > forced merge of all segments that are on an older version (it's implemented > as a MergePolicy). > > > > > Thanks, > > > > --ewh > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > -- David Carlton carl...@sumologic.com
