lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r...@apache.org
Subject svn commit: r641660 - /lucene/solr/trunk/CHANGES.txt
Date Thu, 27 Mar 2008 00:31:22 GMT
Author: ryan
Date: Wed Mar 26 17:31:21 2008
New Revision: 641660

URL: http://svn.apache.org/viewvc?rev=641660&view=rev
Log:
adding master/slave upgrade notice

Modified:
    lucene/solr/trunk/CHANGES.txt

Modified: lucene/solr/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/solr/trunk/CHANGES.txt?rev=641660&r1=641659&r2=641660&view=diff
==============================================================================
--- lucene/solr/trunk/CHANGES.txt (original)
+++ lucene/solr/trunk/CHANGES.txt Wed Mar 26 17:31:21 2008
@@ -25,12 +25,19 @@
 
 Upgrading from Solr 1.2
 -----------------------
+IMPORTANT UPGRADE NOTE: In a master/slave configuration, all searchers/slaves
+should be upgraded before the master!  If the master were to be updated
+first, the older searchers would not be able to read the new index format.
 
-Solr 1.3 includes a newer version of Lucene (2.3.1).  The new index 
-format is not readable by older versions of Lucene. Existing indexes 
-will be automatically converted to the new format after the first 
-<update> command.  Be sure to backup your index before upgrading in 
-case you need to downgrade.
+Older Apache Solr installations can be upgraded by replacing
+the relevant war file with the new version.  No changes to configuration
+files should be needed.  
+
+This version of Solr contains a new version of Lucene implementing
+an updated index format.  This version of Solr/Lucene can still read
+and update indexes in the older formats, and will convert them to the new
+format on the first index change.  Be sure to backup your index before 
+upgrading in case you need to downgrade.
 
 Solr now recognizes HTTP Request headers related to HTTP Caching (see
 RFC 2616 sec13) and will by default respond with "304 Not Modified"



Mime
View raw message