lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven A Rowe <>
Subject RE: What replaces IndexReader.openIfChanged in Lucene 4.0?
Date Mon, 05 Mar 2012 16:07:07 GMT
The second item in the top section in trunk CHANGES.txt (back compat policy changes):
* LUCENE-2858, LUCENE-3733: IndexReader was refactored into abstract
  AtomicReader, CompositeReader, and DirectoryReader. To open Directory-
  based indexes use, 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 [] 
Sent: Monday, March 05, 2012 10:54 AM
Subject: What replaces IndexReader.openIfChanged in Lucene 4.0?

Sorry, I'm coming up empty in Google here.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message