8 April 2016, Apache Lucene™ 6.0.0 available The Lucene PMC is pleased to announce the release of Apache Lucene 6.0.0.
Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.
This release contains numerous bug fixes, optimizations, and improvements, some of which are highlighted below. The release is available for immediate download at:
Please read CHANGES.txt for a full list of new features and changes:
Lucene 6.0.0 Release Highlights:
- Java 8 is the minimum Java version required.
- Dimensional points, replacing legacy numeric fields, provides fast and space-efficient support for both single- and multi-dimension range and shape filtering. This includes numeric (int, float, long, double), InetAddress, BigInteger and binary range filtering, as well as geo-spatial shape search over indexed 2D LatLonPoints. See https://www.elastic.co/blog/lucene-points-6.0 for details. Dependent classes and modules (e.g., MemoryIndex, Spatial Strategies, Join module) have been refactored to use new point types.
- Lucene classification module now works on Lucene Documents using a KNearestNeighborClassifier or SimpleNaiveBayesClassifier.
- The spatial module no longer depends on third-party libraries. Previous spatial classes have been moved to a new spatial-extras module.
- Spatial4j has been updated to a new 0.6 version hosted by locationtech.
- TermsQuery performance boost by a more aggressive default query caching policy.
- IndexSearcher's default Similarity is now changed to BM25Similarity.
- Easier method of defining custom CharTokenizer instances.
Further details of changes are available in the change log available at: http://lucene.apache.org/core/6_0_0/changes/Changes.html
Please report any feedback to the mailing lists (http://lucene.apache.org/core/discussion.html)
Note: The Apache Software Foundation uses an extensive mirroring network for distributing releases. It is possible that the mirror you are using may not have replicated the release yet. If that is the case, please try another mirror. This also applies to Maven access.