Install

Works with Drupal: ^10.1 || ^11.0

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 4.72 MB
MD5: da2cf124a85c86962d7a8668e3ed808a
SHA-1: c0039903fe50a74fe4bd902e3446580376eee93b
SHA-256: 6f4dc1f57dc0d32f5b7696f5fc390051950d52bc46917308160171a6d9ed5cde
Download zip 5.45 MB
MD5: 636fd4e557ae6fe048ffdaa50dc060bc
SHA-1: ea15725d12aa9481e8f1650324d2585eec766f67
SHA-256: 0ce830a9d7a222a27fd3fca47848f38b616344129a37caaac9a10e370f695bb4

Release notes

Search API Solr 4.3.x is a unified release that supports Drupal 9 and 10 in combination with a wide range of Solr versions from 3.6 to 9.x.

The big changes in 4.3.x compared to 4.2.x:

  • Solr 9 support
  • Usage of StandardTokenizer and storeOffsetsWithPositions for better search results and highlighting
  • Field Formatter Plugin to highlight search results in field and entity rendering
  • Solarium 6.3
  • Removal of all deprecated hooks, use Events instead, including Solarium Events

How to upgrade from 4.2.x or earlier

In order to support advanced highlighting and other features, the Solr schema provided by Search API Solr 4.3 got some fundamental changes, for example the usage of StandardTokenizer and storeOffsetsWithPositions.
When upgrading the module to 4.3.x from 4.2.x and earlier you still can read an existing Solr index and perform searches.
But if you write (index) data you'll run into errors like cannot change field "xyz" from index options=DOCS_AND_FREQS_AND_POSITIONS to inconsistent index options=DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS.
There're different ways to deal with the required update. But all require Solr knowledge.
But the safest way is to delete the existing core (or collection in case of Solr Cloud) and to create a new core (or collection) using a new Solr config-set generated by Search API Solr 4.3.x and to re-index your data afterwards.
If you want to avoid downtime of your service, you can also create a new core (or collection), clone and adjust the Search API server and index configs and index all your data twice, while users can still search via the old core (or collection). Afterwards you can use Solr's rename or alias capabilities to switch both cores (or collections) and delete the cloned Search API server and index configs.

Changelog

Changes since 4.3.1:

Changes since 4.3.0:

Changes since 4.3.0-alpha1:

Changes since 4.2.12:

Created by: mkalkbrenner
Created on: 18 Jan 2024 at 10:27 UTC
Last updated: 18 Jan 2024 at 10:27 UTC
Bug fixes
New features
Insecure

Other releases