search_api_solr 4.2.1

Install

Works with Drupal: ^8.8 || ^9

Using Composer to manage Drupal site dependencies

Alternative installation files

Download search_api_solr-4.2.1.tar.gztar.gz 3.23 MB

MD5: b44c62c1305e99e8c5a6082d3efa2be9

SHA-1: 33501b446b74effc779169e37c5ab561c7cc19ab

SHA-256: 92b33ac525545ab4cd1af9618789f5281d82a767ac42e690d74117d9f4427615

Download search_api_solr-4.2.1.zipzip 3.84 MB

MD5: 057691b78e261228302a2dc220d24827

SHA-1: 54e40c7ce41cef8edfb92807f87db06b0b13e9c8

SHA-256: 9a3b4f74a683cfe0fac4c3939396dc82b5e3a8a0cc5d873fd082bef499b68785

Release notes

Search API Solr 4.x is the unified release that supports Drupal 8 and 9 and a wide range of Solr versions.

The big changes in 4.x compared to 3.x:

semantic versioning
compatible to Drupal 8.8, 8.9 and 9.x
We upgraded to solarium 6.1 and therefore require at least PHP 7.3
basic support for selected older Solr versions between 3.6 and 5.5 via the new search_api_solr_legacy sub-module
jump-start Solr config-sets you could simply copy and deploy on you're Solr sever to create a core or a collection
Automated configset upload and collection creation for Solr Cloud using the search_api_solr_admin sub-module

Like Search API Solr Search 8.x-3.x, it supports upgrade paths from any previous 8.x version including Search API Solr Multilingual 8.x-1.x!

BTW there's a new user contributed documentation: https://www.drupal.org/docs/8/modules/search-api-solr

The big changes in 3.x compared to 2.x:

We collapsed the features of the Standard Backend, both Multilingual Backends and the "Any Schema" Backend into a one new unified Solr Backend. There's a migration path :-)
Mulitisite is back! Select "Clone for Multisite" in an Index' operations, save the Clone Form, export the cloned index config (and probably the server config), deploy the config to a different site, configure a search View as usual, enjoy! ;-)
Spellchecking is now configurable like Suggesters. Use the standard filed configuration to decide which fields should feed the spellcheck catalog
We now distinguish between NGram and EdgeNGram. Both field types are fully configurable via Drupal config files.
Solr 7/8 compatible implementation of index time boosting of terms and documents
Configurable MoreLikeThis parameters per index
Support for Solr Cloud exclusive features

The big changes in 3.x compared to 1.x:

The module doesn't include ready to use Solr config-sets anymore! These were too limited for the changes mentioned above. In 3.x the config-sets will be "generated" individually for your site. See
Native support for Solr Cloud
Multingual

Important: Since solarium 5.0 and later supports Solr v2 API, the connector settings need to be adjusted when updating from Search API Solr 1.x or 2.x! The "path" must not end with "/solr" but "/" without "solr" because that is the v1 API endpoint!
Your existing configs will be adjusted automatically via an update hook implementation. But if you've overwritten the connection settings (for example in settings.php) you must adjust the path by yourself!

Important: You need to update your Solr config files if you update from any previous version! After deploying the config set to your Solr server(s) you need to re-index your content!

Important: You might need to adjust the solrcore.properties file to your needs. If you get errors about missing classes you should adjust the solr.install.dir.

PHP 7.3 or newer required!

Due to the requirements of the libraries we use we can't support PHP 5, PHP 7.0, PHP 7.1 or PHP 7.2 anymore! These versions reached EOL anyway.

The recommended way to install this module properly is the usage of composer!

To install the module including its dependencies simply change into your drupal directory and run composer require drupal/search_api_solr:^4.2.
But if you just download the module it won't work because the required external libraries are not part of this package!

The Drupal 8 symfony/event-dispatcher issue!

See #3085196: How to upgrade to solarium 5.1.x, 5.2.x or 6.0.x for details. But with the Search API Solr 4.1.0 release (and later) we solved that issue! So it doesn't exist anymore for new installations.
If you applied one of the workarounds before, don't forget to revert them!
Drupal 8 users should for example update like this to revert to the original event-dispatcher:
composer require symfony/event-dispatcher:~3.4.0 solarium/solarium:^6.1 search_api_solr:^4.2