[CONF] Apache Solr Reference Guide > Upgrading Solr

["Hoss Man (Confluence)" <co...@apache.org>]

Space: Apache Solr Reference Guide (https://cwiki.apache.org/confluence/display/solr)
Page: Upgrading Solr (https://cwiki.apache.org/confluence/display/solr/Upgrading+Solr)

Change Comment:
---------------------------------------------------------------------
incorporate current upgrade instructions from CHANGES.txt

Edited by Hoss Man:
---------------------------------------------------------------------
If you are already using Solr 4.4, Solr 4.5 should not present any major problems. However, you should review the [{{CHANGES.txt}}|http://lucene.apache.org/solr/4_5_0/changes/Changes.html] file found in your Solr package for changes and updates that may effect your existing implementation.

h2. Upgrading from 4.4.x

* XML configuration parsing is now more strict about situations where a single setting is allowed but multiple values are found.  In the past, one value would be chosen arbitrarily and silently.  Starting with 4.5, configuration parsing will fail with an error in situations like this.  If you see error messages such as "solrconfig.xml contains more than one value for config path: XXXXX" or "Found Z configuration sections when at most 1 is allowed matching expression: XXXXX" check your solrconfig.xml file for multiple occurrences of XXXXX and delete the ones that you do not wish to use.

* In the past, schema.xml parsing would silently ignore "default" or "required" options specified on {{<dynamicField/>}} declarations.  Begining with 4.5, attempting to do configured these on a dynamic field will cause an init error.  If you encounter one of these errors when upgrading an existing schema.xml, you can safely remove these attributes, regardless of their value, from your config and Solr will continue to bahave exactly as it did in previous versions. 

* The {{UniqFieldsUpdateProcessorFactory}} has been improved to support all of the {{FieldMutatingUpdateProcessorFactory}} selector options.  The {{<lst named="fields">}} init param option is now deprecated and should be replaced with the more standard {{<arr name="fieldName">}}.

* {{UpdateRequestExt}} has been removed as part of SOLR-4816. You should use {{UpdateRequest}} instead.
  
* {{CloudSolrServer}} can now use multiple threads to add documents by default. This is a small change in runtime semantics when using the bulk add method - you will still end up with the same exception on a failure, but some documents beyond the one that failed may have made it in. To get the old, single threaded behavior, set parallel updates to false on the {{CloudSolrServer}} instance.  

As with any Solr update, it is recommended that you re-index your content.

h2. Upgrading from Older Versions of Solr

This is a summary of some of the key issues related to upgrading in previous versions of Solr.  Users upgrading from older versions are strongly encouraged to consult {{CHANGES.txt}} the details of all changes since the version they are upgrading from.

* Begining with 4.4, the use of the Compound File Format is determined by IndexWriter configuration, and not the Merge Policy.  If you have explicitly configured a {{<mergePolicy>}} with the {{setUseCompoundFile}} configuration option, you should changed this to [use the {{useCompoundFile}} configuration option directly in the {{<indexConfig>}} block|IndexConfig in SolrConfig].  Specifying {{setUseCompoundFile}} on the Merge Policy will no longer work in Solr 5.0.
* In Solr 4.4, {{ByteField}} and {{ShortField}} were deprecated, and will be removed in 5.0.  Please switch to using {{TrieIntField}}
* The pre-4.3.0 {{solr.xml}} "legacy" mode and format will no longer be supported in Solr 5.0.  Users are encouraged to migrate from "legacy" to "discovery" {{solr.xml}} configurations, see [Solr Cores and solr.xml].
* As of Solr 4.3 the slf4j/logging jars are no longer included in the Solr webapp to allow for more flexibility in logging.
* Minor changes were made to the Schema API response format in Solr 4.3
* In Solr 4.1 the method Solr uses to identify node names for SolrCloud was changed.  If you are using SolrCloud and upgrading from Solr 4.0, you may have issues with unknown or lost nodes. If this occurs, you can manually set the {{host}} parameter either in {{solr.xml}} or as a system variable. More information can be found in the section on [SolrCloud].
* If you are upgrading from Solr 3.x, you should familiarize yourself with the [Major Changes from Solr 3 to Solr 4]. 


{scrollbar}



Stop watching space: https://cwiki.apache.org/confluence/users/removespacenotification.action?spaceKey=solr
Change email notification preferences: https://cwiki.apache.org/confluence/users/editmyemailsettings.action