svn commit: r1072020 - /lucene/dev/trunk/solr/CHANGES.txt

[yo...@apache.org]

Author: yonik
Date: Fri Feb 18 15:20:39 2011
New Revision: 1072020

URL: http://svn.apache.org/viewvc?rev=1072020&view=rev
Log:
docs: move entry to 3.1 from 4.0

Modified:
    lucene/dev/trunk/solr/CHANGES.txt

Modified: lucene/dev/trunk/solr/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/solr/CHANGES.txt?rev=1072020&r1=1072019&r2=1072020&view=diff
==============================================================================
--- lucene/dev/trunk/solr/CHANGES.txt (original)
+++ lucene/dev/trunk/solr/CHANGES.txt Fri Feb 18 15:20:39 2011
@@ -53,14 +53,6 @@ Upgrading from Solr 3.1-dev
   legacy behavior should set a default value for the 'mm' param in
   their solrconfig.xml file.
 
-* In previous releases, sorting or evaluating function queries on 
-  fields that were "multiValued" (either by explicit declaration in
-  schema.xml or by implict behavior because the "version" attribute on
-  the schema was less then 1.2) did not generally work, but it would
-  sometimes silently act as if it succeeded and order the docs
-  arbitrarily.  Solr will now fail on any attempt to sort, or apply a
-  function to, multi-valued fields 
-
 
 
 Detailed Change List
@@ -268,6 +260,14 @@ Upgrading from Solr 1.4
 
 * readercycle script was removed. (SOLR-2046)
 
+* In previous releases, sorting or evaluating function queries on 
+  fields that were "multiValued" (either by explicit declaration in
+  schema.xml or by implict behavior because the "version" attribute on
+  the schema was less then 1.2) did not generally work, but it would
+  sometimes silently act as if it succeeded and order the docs
+  arbitrarily.  Solr will now fail on any attempt to sort, or apply a
+  function to, multi-valued fields 
+
 Detailed Change List
 ----------------------