Due to the release of Acquia's new Solr 7 platform, Acquia and the Drupal community have changed some module requirements and namespaces, which require your action depending on the current Search module version(s) you are using.
If you have the Acquia Search Solr module enabled (for D8 and D9) you will need to run the below instructions.
These will both install new/updated code and also migrate some Drupal configuration objects to the new (and final) namespaces. In summary, the
acquia_search_solr namespace and module are being deprecated, and Acquia has now split off
acquia_search as a separate Drupal project that is now independent from the
These instructions are only to be used if you:
- Are running Drupal 8 or 9...
- ... currently have the acquia_search_solr module enabled in your codebase...
- ... and want to use the new Solr 7 platform.
- ... and have a testing site (we do not recommend running these directly on production).
Remember that Acquia also offers Solr 3/4 for your Drupal sites. If you want to run the latest code, but want to use Solr 3/4, see our documentation.
Like always, we also recommend reading modules' release notes. Releases for Acquia Search.
- Before you start: we always recommend creating a backup before you do this or any other change to your site.
- You will need to change your code using composer:
composer require drupal/acquia_search_solr:3.0.0 drupal/acquia_connector:^3 drupal/acquia_search:^3
- Look out for any composer warnings resulting from the above, and fix.
- Deploy your code to Acquia Cloud. We recommend using a non-production environment for this.
- Run database updates. For this we recommend using drush:
- SSH into your Acquia Cloud environment where you deployed your code.
- Run the drush updb --uri=[domain] command, editing the [domain] part to match your site's URL.
- If you have various Drupal multisite instances, you may need to run database updates once for each instance.
- IMPORTANT NOTE: This will disable
acquia_search_solr.module(now deprecated) and leave
- IMPORTANT NOTE: The Search API index and server names that were created by acquia_search_solr module will change. The default view is adjusted automatically. If you have any Views or other items dependant on these Views, or the Index and Server, you may need to manually edit configuration objects.
You should now test connectivity to your Solr indexes.
After this, it is now safe to remove the deprecated Acquia Search Solr module from your codebase, like this:
composer remove drupal/acquia_search_solr