fyi. At some point we'll need to use some search fwk that sits on top of Lucene.
-Vincent
Begin forwarded message:
From: Grant Ingersoll <gsingers(a)apache.org>
Date: March 31, 2011 8:45:18 PM GMT+02:00
To: announce(a)apache.org, dev(a)lucene.apache.org, solr-user(a)lucene.apache.org, general list
<general(a)lucene.apache.org>
Subject: Apache Solr 3.1.0
March 2011, Apache Solr 3.1 available
The Lucene PMC is pleased to announce the release of Apache Solr 3.1.
This release contains numerous bug fixes, optimizations, and
improvements, some of which are highlighted below. The release is
available for immediate download at
http://www.apache.org/dyn/closer.cgi/lucene/solr (see
note below).
See the CHANGES.txt file included with the release for a full list of
details as well as instructions on upgrading.
What's in a Version?
The version number for Solr 3.1 was chosen to reflect the merge of
development with Lucene, which is currently also on 3.1. Going
forward, we expect the Solr version to be the same as the Lucene
version. Solr 3.1 contains Lucene 3.1 and is the release after Solr 1.4.1.
Solr 3.1 Release Highlights
* Numeric range facets (similar to date faceting).
* New spatial search, including spatial filtering, boosting and sorting capabilities.
* Example Velocity driven search UI at
http://localhost:8983/solr/browse
* A new termvector-based highlighter
* Extend dismax (edismax) query parser which addresses some
missing features in the dismax query parser along with some
extensions.
* Several more components now support distributed mode:
TermsComponent, SpellCheckComponent.
* A new Auto Suggest component.
* Ability to sort by functions.
* JSON document indexing
* CSV response format
* Apache UIMA integration for metadata extraction
* Leverages Lucene 3.1 and it's inherent optimizations and bug fixes
as well as new analysis capabilities.
* Numerous improvements, bug fixes, and optimizations.
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 goes for Maven
access.