When you configure Acquia Search, you decide what entity types get included in the search index and are available to return to users as search results. Examples include nodes like articles, pages, and blocks, taxonomy terms, users, and files. You can include file attachments, if you install and configure the Drupal 7 Apache Solr Search Attachments module.
Yes, Acquia Search uses the Apache Lucene Query Parser Syntax.
Yes, you may use \*
(several characters) and ?
(single character)
wildcards. Searches may not begin with wildcards or other logical operators.
Yes. This feature requires installing and configuring the Apache Solr Search Attachments module. For setup and configuration information, see Indexing attachments with Apache Solr Search module.
Yes. This feature requires installing and configuring the Apache Solr Multisite Search module.
No, Acquia Search does not support near-realtime search. The required
configuration would jeopardize the Search-as-a-service platform and cause
issues with performance and stability. Also, Acquia does not allow the
modification of the solrconfig.xml
file to increase the frequency of
auto commits.
Acquia Search can index websites in most languages, but Acquia Search passes content through a language-specific stemmer during indexing, depending on the search schema you have configured for your website. Acquia Search offers search schemas for Dutch, French, German, Spanish, and English. You can search other languages, but the search may produce less relevant search results because partial words, plurals and other variations may not be indexed as expected. For more information, see Selecting a language.
If your website is in a language other than Dutch, English, French, German, or Spanish, contact Acquia Support to see whether a search schema specific to that language is available for you.
You can select standard configurations on the Search page of the Acquia
user interface. If you are an Enterprise customer who needs a custom
configuration (typically a schema.xml
or synonyms.txt
file), you
can upload your own custom configuration directly in the Cloud Platform user
interface. For more information, see Custom Solr configuration with Solr 7. If you need
help developing a custom configuration, contact Acquia sales to discuss your
needs and implementation possibilities through Acquia’s professional services
division.
Yes, you can use the Search API module with Acquia Search. This is an alternative to using the Apache Solr Search module. Acquia Search for Drupal 9 or later requires the use of Search API, and won’t use the ApacheSolr module.
Don’t use both the Search API module and the Apache Solr Search module in the same environment.
For more information, read Using the Search API.
Acquia Search does not support using Nutch to index external data. For data security, the Acquia Search architecture requires authentication, which Nutch does not natively support.
Acquia recommends exporting your non-Drupal content into a Drupal website using contributed modules such as Feeds or Migrate to transform your data into Drupal entities, which Acquia Search may then index.
Acquia counts select
(searching) and update
(indexing) requests
reaching the Acquia Search back end.
Yes, Drupal modules can index more than one item at a time in a single Solr update request.