Author: ehatcher
Date: Wed Nov 25 11:18:16 2009
New Revision: 884052
URL: http://svn.apache.org/viewvc?rev=884052&view=rev
Log:
slight reformatting and fixed a typo
Modified:
lucene/solr/trunk/CHANGES.txt
Modified: lucene/solr/trunk/CHANGES.txt
URL:
http://svn.apache.org/viewvc/lucene/solr/trunk/CHANGES.txt?rev=884052&r1=884051&r2=884052&view=diff
==============================================================================
--- lucene/solr/trunk/CHANGES.txt (original)
+++ lucene/solr/trunk/CHANGES.txt Wed Nov 25 11:18:16 2009
@@ -34,8 +34,11 @@
New Features
----------------------
-* SOLR-1302: Added several new distance based functions, including Great
Circle (haversine), Manhattan, Euclidean and String (using the StringDistance
methods in the Lucene Spellchecker).
- Also added geohash(), deg() and rad() convenience functions. See
http://wiki.apache.org/solr/FunctionQuery. (gsingers)
+* SOLR-1302: Added several new distance based functions, including
+ Great Circle (haversine), Manhattan, Euclidean and String (using the
+ StringDistance methods in the Lucene spellchecker).
+ Also added geohash(), deg() and rad() convenience functions.
+ See http://wiki.apache.org/solr/FunctionQuery. (gsingers)
* SOLR-1553: New dismax parser implementation (accessible as "edismax")
that supports full lucene syntax, improved reserved char escaping,
@@ -44,7 +47,8 @@
* SOLR-1574: Add many new functions from java Math (e.g. sin, cos) (yonik)
-* SOLR-1569: Allow functions to take in literal strings by modifying the
FunctionQParser and adding LiteralValueSource (gsingers)
+* SOLR-1569: Allow functions to take in literal strings by modifying the
+ FunctionQParser and adding LiteralValueSource (gsingers)
Optimizations
----------------------
@@ -87,7 +91,7 @@
"SEVERE: SolrIndexWriter was not closed prior to finalize()" although
there were no other consequences. (yonik)
-* SOLR-1595: StreamingUpdateSolrServer used the patform default character
+* SOLR-1595: StreamingUpdateSolrServer used the platform default character
set when streaming updates, rather than using UTF-8 as the HTTP headers
indicated, leading to an encoding mismatch. (hossman, yonik)
