https://builds.apache.org//job/Lucene-trunk/lastSuccessfulBuild/artifact/artifacts/changes/Changes.html
-----Original Message----- From: Benson Margulies [mailto:[email protected]] Sent: Monday, March 05, 2012 11:11 AM To: [email protected] Subject: Re: What replaces IndexReader.openIfChanged in Lucene 4.0? On Mon, Mar 5, 2012 at 11:07 AM, Steven A Rowe <[email protected]> wrote: > The second item in the top section in trunk CHANGES.txt (back compat policy > changes): Could you guys put this on the web site (or a link to it)? Or try to get it to SEO more prominently? > > * LUCENE-2858, LUCENE-3733: IndexReader was refactored into abstract > AtomicReader, CompositeReader, and DirectoryReader. To open > Directory- > based indexes use DirectoryReader.open(), the corresponding method in > IndexReader is now deprecated for easier migration. Only > DirectoryReader > supports commits, versions, and reopening with openIfChanged(). > Terms, > postings, docvalues, and norms can from now on only be retrieved > using > AtomicReader; DirectoryReader and MultiReader extend CompositeReader, > only offering stored fields and access to the sub-readers (which may > be > composite or atomic). SlowCompositeReaderWrapper (LUCENE-2597) can be > used to emulate atomic readers on top of composites. > Please review MIGRATE.txt for information how to migrate old code. > (Uwe Schindler, Robert Muir, Mike McCandless) > > -----Original Message----- > From: Benson Margulies [mailto:[email protected]] > Sent: Monday, March 05, 2012 10:54 AM > To: [email protected] > Subject: What replaces IndexReader.openIfChanged in Lucene 4.0? > > Sorry, I'm coming up empty in Google here. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
