This table presents compatibility of different Sitecore CMS/XP versions with different Solr versions. Solr Sitecore 7.0 - 8.0 Sitecore 8.1 Sitecore 8.2 1.1 - 4.0 – – – 4.1 ✓ * * 4.2 - 4.7 * * * 4.8 - 4.9 *[1] * * 4.10 *[1] ✓ * 5.0 *[1] * * 5.1 *[1] * ✓ 5.2 - 5.4 *[1] * * 5.5 –[3] –[3] –[3] 5.5.1, 6.0 - 6.1 *[1][2] *[2] *[2] Legend: ✓ officially tested, recommended * not officially tested, but expected to work – no compatibility information or does not work Note: SolrCloud setups are under experimental support starting from Sitecore XP 8.2, meaning some issues are possible. In case of related issues, Sitecore Support will help with troubleshooting, while there is no guarantee that a fix will be available. In earlier versions of Sitecore CMS/XP only standalone Solr setups are supported.
[1] Changes in the default schema.xml file shipped with Solr 4.8 and later can cause the following issues: Sitecore cannot be initialized due to the following error: [NullReferenceException: Object reference not set to an instance of an object.] SolrNet.Schema.SolrSchemaParser.Parse(XDocument solrSchemaXml) +425 SolrNet.Impl.SolrBasicServer`1.GetSchema() +207 Sitecore.ContentSearch.SolrProvider.SolrSearchIndex.Initialize() +1125 Sitecore.ContentSearch.SolrProvider.SolrContentSearchManager.Initialize() +168 Sitecore.ContentSearch.SolrProvider.CastleWindsorIntegration.WindsorSolrStartUp.Initialize() +757 Build Solr Schema Wizard successfully completes building the schema, but the resulting schema.xml file lacks Sitecore specific configuration. To resolve the issue, apply the corresponding solution described below. [2] Starting from Solr 6 default Config Sets are distributed without the schema.xml file. To resolve the issue, apply the corresponding solution described below. [3]Known issue for Solr 5.5 (https://issues.apache.org/jira/browse/SOLR-8793) results in the following error on Sitecore side: WARN Unable to connect to Solr: [http://{hostname}:{port}/solr], the [SolrNet.Exceptions.SolrConnectionException] was caught. Exception: SolrNet.Exceptions.SolrConnectionException Message: Error handling 'status' actionorg.apache.solr.common.SolrException: Error handling 'status' action To resolve issue, upgrade Solr to 5.5.1 or later version.
Note: Solution [2] should be implemented before Solution [1] if both of them apply to the XP and Solr version combination. To resolve the issue, follow the steps below: Make the following changes in the default schema.xml file distributed with Solr: enclose all <field> and <dynamicField> elements in the <fields> tag. enclose all <fieldType> elements in the <types> tag. Pass the modified schema.xml file to the Build Solr Schema Wizard to add the Sitecore-specific configuration. Put the resulting file to the configuration folder of the Solr core. Find the following dynamic field definition in the schema.xml file: <dynamicField name="*_pi" type="pint" indexed="true" stored="true" /> change the mapping type from "pint" to "tint" <dynamicField name="*_pi" type="tint" indexed="true" stored="true" /> Reload the core to apply schema changes. Restart the application pool of the website to initialize Sitecore indexes using the updated schema.xml file.
To resolve the issue, follow the steps below: Create schema.xml file by duplicating and renaming the managed-schema file. Switch to ClassicIndexSchemaFactory by adding the following line to the SolrConfig.xml file: <schemaFactory class="ClassicIndexSchemaFactory" /> If the SolrConfig.xml file contains the following UpdateRequestProcessorChain <updateRequestProcessorChain name="add-unknown-fields-to-the-schema"> then find and comment out its AddSchemaFieldsUpdateProcessorFactory processor.