Page History

...

Per-segment searching is largely kept under the covers but since LexEVS employs a number of customizations of parameters, particularly filters many queries may break and need refactoring.  At the same time a number of objects have new names, apis and other changes that will require refactoring and updating to an as yet undetermined amount.  Some needed changes are documented in the Lucene 4.0 Migration guide:  https://lucene.apache.org/core/4_0_0/MIGRATE.html

The use of IndexReader in particular will not change, but filters and queries passed into this may break or otherwise be unusable.  Read this article for more information: http://blog.thetaphi.de/2012/02/is-your-indexreader-atomic-major.html

...

• ChainedFilter replaced with BooleanFilter
• HitCollector is replaced by Collector or SimpleCollector
• MultiSearcher will likely be replaced by something like IndexSearcher(MultiReader)
• The interface Searchable has gone away and it's former child classes such as IndexSearcher will have to take it's place.
• TermEnum is replaced by TermsEnum

Updated Objects that have new API's include:

...