The former SearchServiceAdapter and corresponding classes were replaced by the new SearchAdapter, featuring a SPI architecture and offering SearchServiceProvider as an ExtensionPoint. The default implementation in DefaultSearchServiceProvider implements the same behaviour as the former SearchServiceAdapter.

This change is considered breaking, because the new SearchAdapter is now used in the search-schema (implementing the former behaviour). If the now outdated SearchServiceAdapter was not extended or changed, this change behaves as nonbreaking.

In case, SearchServiceAdapter was extended or changed, SearchServiceAdapter is just deprecated and still part of HeadlessServer. If necessary, the old adapter may still be used the same way as before simply by changing the search-schema:

// from
search(
  ...
): SearchResult @fetch(from: "@searchServiceAdapter.to().search(#query, #offset, #limit, #docTypes, #sortFields, #siteId, #includeSubTypes, #customFilterQueries)")

// to
search(
  ...
): SearchResult @fetch(from: "@legacySearchServiceAdapter.to().search(#query, #offset, #limit, #docTypes, #sortFields, #siteId, #includeSubTypes, #customFilterQueries)")

(CMS-21256)