Big Data/Analytics Zone is brought to you in partnership with:

Rafal Kuc is a team leader and software developer. Right now he is a software architect and Solr and Lucene specialist. Mainly focused on Java, but open on every tool and programming language that will make the achievement of his goal easier and faster. Rafal is also one of the founders of solr.pl site where he tries to share his knowledge and help people with their problems. Rafał is a DZone MVB and is not an employee of DZone and has posted 75 posts at DZone. You can read more from them at their website. View Full User Profile

Apache Lucene and Solr 4.2

03.14.2013
| 2695 views |
  • submit to reddit

Today Apache Lucene and Solr PMC announced another version of Apache Lucene library and Apache Solr search server numbred 4.2. This is a next release continuing the 4th version of both Apache Lucene and Apache Solr.

Here are some of the changes that were made comparing to the 4.1 version:

Lucene

  • New, default codec with default term vectors compression and more efficient DocValues format
  • Refactoring and performance improvement to faceting module
  • FST structure now supports data in size above 2GB

Solr

  • API for index structure allowing for schema.xml elements fetching
  • DocValues support
  • Collections aliasing
  • Custom node names for SolrCloud deployments
  • Enchantments that comes with Apache Lucene 4.2

Full changes list for Lucene can be found at http://wiki.apache.org/lucene-java/ReleaseNote42. Full list of changes in Solr 4.2 can be found at: http://wiki.apache.org/solr/ReleaseNote41.

Apache Lucene 4.2 library can be downloaded from the following address: http://www.apache.org/dyn/closer.cgi/lucene/java/. Apache Solr 4.2 can be downloaded at the following URL address: http://www.apache.org/dyn/closer.cgi/lucene/solr/. Please remember that the mirrors are just starting to update so not all of them will contain the 4.2 version of Lucene and Solr.

Published at DZone with permission of Rafał Kuć, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)