Known issues in Acquia Search¶

Solr search has difficulty handling large attachments¶

For more information, see Issues with large attachments and Solr search in the Acquia Support Knowledge Base.

Acquia Search can’t be included in a dedicated virtual private cloud¶

Acquia Search is hosted within Acquia’s shared virtual private cloud (VPC). Although you can access Acquia Search from your Acquia Shield applications, the Acquia Search servers are located outside of your Acquia Shield dedicated section. Due to the Acquia Search servers’ location, Acquia Shield doesn’t protect your search index. For more information about how Acquia uses VPCs, see Virtual Private Cloud.

Internal Solr error with Eastern European languages¶

Advanced search functionalities, such as Acquia internal backups and select all queries, may fail if the dynamic field sort_X3b_* has class type defined as solr.ICUCollationField, and contains unicode characters from Eastern European languages. This will not affect regular indexing and search operations. For more information, see the Solr ticket.

The Workbench Moderation module can cause search integration problems¶

For more information about the Workbench Moderation module, see its project page on Drupal.org.

Search API has memory errors when indexing¶

For more information about this issue, see Better memory usage on indexing on Drupal.org.

Search API provides fewer configuration options¶

The Search API module provides fewer configuration options than ApacheSolr integration in Drupal 7.

Acquia Search module rejects valid responses¶

Subscribers using Acquia Connector version 8.x-1.20 may see Authentication of search content failed url errors in the Drupal watchdog log.

Workaround: Downgrade to Acquia Connector version 8.x-1.19.

The Search API module can’t display result snippets¶

The Search API module can’t 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.

Non-SQL query plugins for Views cause PHP errors¶

For more information about this issue, see Views problems with non-SQL query plugins on Drupal.org.

The Search API Multilingual Solr Search module requires a patch¶

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 must not be cached¶

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

Content types are unintentionally indexed¶

Acquia Search indexes content types, when that is not the intended behavior.

Workaround: Add a content type filter to an Acquia Search view.