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."
Note: even if this message is showing, you may still be able to search and index data into your Solr instance.
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 linked to from the message.
- 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 and go to the Search API "Server".
- Download the configset from the Search API "Server" page by using the "Get Config.zip" button.
- Optionally, if you require some custom configuration (like synonyms/protected words/etc.) you can edit the appropriate files at this step.
- Attach the ZIP archive with the Solr configset into a new Acquia Support ticket. You MUST also specify the list of Search indexes (URLs) to apply the configuration to.
- Please consult https://docs.acquia.com/acquia-search/config/ on what to expect regarding turnaround times.
Note: We are working to make this process self-service via the Cloud UI. Stay tuned!
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).