Solr compatibility table


Description

The following tables present the compatibility of different Sitecore CMS/XP versions with different Solr versions.

Solr XP 9.0 XP 9.1 XP 9.2 XP 9.3 XP 10.0 XP 10.1 XP 10.2
6.6.1 [6] [4]
6.6.2 – 6.6.5 [6]
6.6.6 *
7.2.1 [7]
7.5 [7]
8.1.1 [7][8]
8.2.0 [7] *
8.4
8.8.2 - -


Solr CMS 7.0 – XP 8.0 XP 8.1 XP 8.2
4.1 * *
4.2 – 4.7 * * *
4.8 – 4.9 *[1] * *
4.10 *[1] *
5.0[6] *[1] * *
5.1[6] *[1] *
5.2 – 5.4[6] *[1] * *
5.5[6] [3] [3] [3]
5.5.1,
6.0 – 6.1[6]
*[1][2] *[2] *[2]
6.6.1[6] [4][5]
6.6.2 – 6.6.5[6] [5]
6.6.6 *[5]


Legend:

officially tested, recommended
* not officially tested, but expected to work
no compatibility information or does not work


The following table presents the support status of the SolrCloud feature for different Sitecore CMS/XP versions:


CMS 7.0 – XP 8.1 XP 8.2 XP 9.0 Update-1 XP 9.0 Update-2 and later
Support status Not supported Under Experimental Support Officially tested and supported


For information about Experimental Support, read the Sitecore Product Support Lifecycle article. The Solr Index replication feature is not supported. The SolrCloud feature can be used as a replacement.

Notes

Solution [1]

Note: If both solutions apply to your specific Sitecore and Solr version combination, you must implement Solution [2]  before Solution [1].

To resolve the issue:

  1. 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.
  2. To add Sitecore-specific configuration, pass the modified schema.xml file to the Build Solr Schema wizard.
  3. Put the resulting file in the configuration folder of the Solr core.
  4. Find the following dynamic field definition in the schema.xml file:
    <dynamicField name="*_pi" type="pint" indexed="true" stored="true" />
  5. Change the mapping type from "pint" to "tint".
    <dynamicField name="*_pi" type="tint" indexed="true" stored="true" />
  6. Reload the core to apply the schema changes.
  7. Restart the application pool of the website to initialize Sitecore indexes using the updated schema.xml file.

Solution [2]

To resolve the issue:

  1. Create a schema.xml file by duplicating and renaming the managed-schema file.
  2. Switch to the ClassicIndexSchemaFactory setting by adding the following line to the SolrConfig.xml file:
    <schemaFactory class="ClassicIndexSchemaFactory" />
  3. 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.