Known issues in Acquia Search¶

Using the Acquia Connector module in combination with the Search API attachments module results in attachment indexing not working as expected.
Workaround – Reverse-apply this patch available on Drupal.org, and then run drush cr.

Search API cannot display result snippets—the full node output displays as the search result.
Workaround – Create a Search result view mode to output something smaller than the full node. To add the workaround, complete the following steps:

1. Go to Structure > Content types > Article > Manage display.

2. In the Custom display settings section, select the Search result highlighting input checkbox.

3. Click Save.

4. Go to Structure > Content types > Article > Manage display > Search result highlighting input. The following settings control each search result’s output.

5. To display result snippets, edit the appropriate field. For example, to make the Body field display result snippets, complete the following steps:

   1. In Format, click Trimmed.
   2. Click the gear icon. The webpage displays the Trimmed limit field.
   3. In the Trimmed limit field, enter 200 to trim the body field to 200 characters.
   4. Click Update.

   You have now configured the Body field to display trimmed output as the search result.

Users must be aware of Views problems with non-SQL query plugins.

The Search API Multilingual Solr Search module requires a patch to properly interact with the field schema.
Workaround – apply the Search API Multilingual Solr Search patch available on Drupal.org which disables the AbstractSearchApiSolrMultilingualBackend::isPartOfSchema() function.

Views exposed filters, such as search results and blocks with facets, must not have caching enabled alongside AJAX. For more information, see the Drupal.org issue on Ajax facet block seems to lose views context.

Content types are indexed when not intended.
Workaround – Add a content type filter to an Acquia Search view.