Hi, The fastest way to upgrade is to leave luceneMatchVersion as LUCENE_40. Then you will not get any surprises wrt changed behavior for existing functionality. but you will get all the bug fixes. You can test it out on your dev box.
The first time Solr reads the existing index, it will be converted to 4.3 format, so keep a backup in case you wish to downgrade again, since 4.0 will not read this index. I'm not 100% sure if this auto conversion will compressed stored fields for you or if you need a re-index for that. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 10. mai 2013 kl. 11:49 skrev Andreas Hubold <andreas.hub...@coremedia.com>: > Hi, > > we are planning to update Solr installations from 4.0 to 4.3 and want to > avoid reindexing. But solrconfig.xml contains the following comment for > <luceneMatchVersion>: > > "... Generally, you want to use the latest version to get all bug fixes and > improvements. It is highly recommended that you fully re-index after changing > this setting ..." > > What bug fixes / improvements do we loose if we'd stay at > <luceneMatchVersion>LUCENE_40</luceneMatchVersion>? > Or is it safe to change it from LUCENE_40 to LUCENE_43 without reindexing? > > The release notes do no mention index format incompatibilites. However, the > compression of stored fields introduced in 4.1 is definitely an index change. > Is it correct that Solr 4.3 can still read a Solr 4.0 index? > > I would think that it is not possible for Solr 4.0 to read an index from Solr > 4.3, right? This is important to know - just in case an update from 4.0 to > 4.3 needs to be rolled back. > > Thank you, > Andreas
