Re: svn commit: r641573 - /lucene/solr/trunk/CHANGES.txt

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r641573 - /lucene/solr/trunk/CHANGES.txt

Yonik Seeley-2
Perhaps use the 1.2 upgrading statement as a template?  It mentions
how to handle master/slave upgrading.

-Yonik

On Wed, Mar 26, 2008 at 4:59 PM,  <[hidden email]> wrote:

> Author: ryan
>  Date: Wed Mar 26 13:59:40 2008
>  New Revision: 641573
>
>  URL: http://svn.apache.org/viewvc?rev=641573&view=rev
>  Log:
>  adding an upgrade note about the lucene format changes
>
>  Modified:
>     lucene/solr/trunk/CHANGES.txt
>
>  Modified: lucene/solr/trunk/CHANGES.txt
>  URL: http://svn.apache.org/viewvc/lucene/solr/trunk/CHANGES.txt?rev=641573&r1=641572&r2=641573&view=diff
>  ==============================================================================
>  --- lucene/solr/trunk/CHANGES.txt (original)
>  +++ lucene/solr/trunk/CHANGES.txt Wed Mar 26 13:59:40 2008
>  @@ -26,6 +26,12 @@
>   Upgrading from Solr 1.2
>   -----------------------
>
>  +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.
>  +
>   Solr now recognizes HTTP Request headers related to HTTP Caching (see
>   RFC 2616 sec13) and will by default respond with "304 Not Modified"
>   when appropriate.  This should only affect users who access Solr via
>
>
>