The Search API Solr (search_api_solr) Drupal module shows a message like these:
"You are using outdated Solr configuration set. Please follow the instructions described in the README.md file for setting up Solr."
"There are some configuration elements missing in the Solr server schema [Server Name]. This is likely due to using an outdated version of either Drupal or Solr. The recommended version is: [version]. An updated config.zip should be downloaded and deployed to your Solr server."
"A new Solr field type has been installed due to configuration changes. It is advisable to download and deploy an updated config.zip to your Solr server."
Note: even if one or more of these messages is showing, you may still be able to search and index data into your Solr instance; ideally you should still follow the resolution steps below.
To resolve this, you will need to update the Solr configuration files (also known as "configset") used by the Solr index.
- For a non-Acquia Solr installation, you need to follow the provided "README.md" file within the search_api_solr module folder.
- For an Acquia-hosted Solr index, you must file an Acquia Support ticket with the appropriate configset in ZIP format. Here are the steps:
- Log into your Drupal site as an administrator, and go to the admin page for the Search API "Server" mentioned in the above message(s).
- Download the configset by using the "Get Config.zip" button. This will result in a ZIP file containing all of the needed Solr configuration files.
- Optionally, if you require some custom configuration (like synonyms/protected words/etc.) you can edit the appropriate files within the ZIP file at this step.
- Finally, upload the configset to the Acquia Solr instance using the Acquia Cloud UI. See https://docs.acquia.com/acquia-search/config-solr7/
Search API Solr module runs a check that compares the Drupal-side configuration with the Solr-side configuration, and shows this message if doesn't match it's ideal configuration.
Keeping the Solr configuration in sync with your site config (and code) is needed because:
- Different Search API Solr module versions may need a corresponding Solr backend configuration.
- Thus, updating Search API Solr module may require deploying a new configuration.
- Different content languages configured on the Drupal site may require special support on the Solr configuration (e.g. different languages require different configuration for tokenizers, stemmers, etc. for the Solr "text" type fields).