Acquia Search powered by SearchStax provides quick and relevant search results.
This page provides information about how to get started with Acquia Search powered by SearchStax by using your existing Drupal search configurations and index data.
Key concepts for migration
Before you migrate from Acquia Search (Solr) to SearchStax Site Search, you must understand the shift from infrastructure-managed indexing to an application-centric model. Use the following terminology mapping to align the Drupal configuration:
SearchStax App: In the Site Search ecosystem, an App serves as the logical equivalent of a Solr Core or Collection. It acts as the primary container for index data, relevance rules, and analytics.
Search API Server: In Drupal, a Server represents the remote connection to the SearchStax App API. While Acquia Search typically uses internal authentication, SearchStax uses specific App Endpoints and API Keys to facilitate the connection.
Search API Index: An Index object defines the specific subset of Drupal entities, such as Nodes, Media, and Users, to synchronize with SearchStax App.
Multisite indexing: If a single SearchStax App is shared across multiple Drupal environments or sites, you must implement Unique Index IDs or Site Prefixes. This implementation ensures that data remains logically partitioned in the App, prevents document collision, and ensures that search results scope correctly to the requesting site.
Before you start the migration process, set up a SearchStax account with your Acquia ID. Registration with any other ID returns an authentication error. If you do not have an account or require assistance to access the account, contact the account team or Acquia Support.
Acquia recommends that you use the manual migration guide only in the following scenarios:
Drupal views implementation includes complex configurations.
Site uses a complex language setup with custom language fields.
Modules link directly to the index, such as a custom facets module.
Site is small enough to reindex in minutes and requires a straightforward migration path.
Issues are encountered with the migration module approach.
Note
Manual migration causes downtime on the search page during data reindexing.
FAQs
How do I access a new account after the 24 hour activation window expires?
If you received the email for your new Acquia Search powered by SearchStax application but did not activate it within 24 hours, you can follow the link and select Forgot Password. If you require help, contact Acquia Support for assistance.
Can I extract text from documents?
Yes, you can extract text from the supported file types. In order to do so, use the /extract document extractor endpoint. This endpoint enables you to specify page ranges for paginated files and include file metadata in the response. For additional information, visit Document Extraction API.
How do I integrate the Drupal Key module with SearchStax?
Acquia Search powered by SearchStax supports up to 1,024 nested clauses per query. For additional information, visit Understanding the Nested Clause Limit. If you reach the 1,024 nested clause limit, you can consolidate multiple searchable fields into a single copy field to reduce search complexity. For additional information, visit Reducing Nested Clauses with Copy Fields.
Does SearchStax support Schema modifications?
Yes, Acquia Search powered by SearchStax supports Schema modifications. To modify your schema, use the Schema API and a Read/Write token for the application. For additional information, visit Upload Configurations.
How do I override the connection settings if I do not want to use the Key module to segregate my configuration?
SearchStax does not allow you to block bot traffic at the API level. Acquia will make this function available in an upcoming release. Acquia recommends that you use a Web Application Firewall (WAF) such as Cloudflare.
Is SearchStax FedRAMP compliant?
Acquia Search powered by SearchStax plans to include FedRAMP compliance in one of the upcoming releases.
How do I use multiple language support in Acquia Search powered by SearchStax?
Acquia Search powered by SearchStax provides support for multiple languages. This feature includes language-specific analytics, synonyms, stopwords, and ranking. For additional information, visit Supported languages.
Migrating to Acquia Search powered by SearchStax
Acquia Search powered by SearchStax provides quick and relevant search results.
This page provides information about how to get started with Acquia Search powered by SearchStax by using your existing Drupal search configurations and index data.
Key concepts for migration
Before you migrate from Acquia Search (Solr) to SearchStax Site Search, you must understand the shift from infrastructure-managed indexing to an application-centric model. Use the following terminology mapping to align the Drupal configuration:
SearchStax App: In the Site Search ecosystem, an App serves as the logical equivalent of a Solr Core or Collection. It acts as the primary container for index data, relevance rules, and analytics.
Search API Server: In Drupal, a Server represents the remote connection to the SearchStax App API. While Acquia Search typically uses internal authentication, SearchStax uses specific App Endpoints and API Keys to facilitate the connection.
Search API Index: An Index object defines the specific subset of Drupal entities, such as Nodes, Media, and Users, to synchronize with SearchStax App.
Multisite indexing: If a single SearchStax App is shared across multiple Drupal environments or sites, you must implement Unique Index IDs or Site Prefixes. This implementation ensures that data remains logically partitioned in the App, prevents document collision, and ensures that search results scope correctly to the requesting site.
Before you start the migration process, set up a SearchStax account with your Acquia ID. Registration with any other ID returns an authentication error. If you do not have an account or require assistance to access the account, contact the account team or Acquia Support.
Acquia recommends that you use the manual migration guide only in the following scenarios:
Drupal views implementation includes complex configurations.
Site uses a complex language setup with custom language fields.
Modules link directly to the index, such as a custom facets module.
Site is small enough to reindex in minutes and requires a straightforward migration path.
Issues are encountered with the migration module approach.
Note
Manual migration causes downtime on the search page during data reindexing.
FAQs
How do I access a new account after the 24 hour activation window expires?
If you received the email for your new Acquia Search powered by SearchStax application but did not activate it within 24 hours, you can follow the link and select Forgot Password. If you require help, contact Acquia Support for assistance.
Can I extract text from documents?
Yes, you can extract text from the supported file types. In order to do so, use the /extract document extractor endpoint. This endpoint enables you to specify page ranges for paginated files and include file metadata in the response. For additional information, visit Document Extraction API.
How do I integrate the Drupal Key module with SearchStax?
Acquia Search powered by SearchStax supports up to 1,024 nested clauses per query. For additional information, visit Understanding the Nested Clause Limit. If you reach the 1,024 nested clause limit, you can consolidate multiple searchable fields into a single copy field to reduce search complexity. For additional information, visit Reducing Nested Clauses with Copy Fields.
Does SearchStax support Schema modifications?
Yes, Acquia Search powered by SearchStax supports Schema modifications. To modify your schema, use the Schema API and a Read/Write token for the application. For additional information, visit Upload Configurations.
How do I override the connection settings if I do not want to use the Key module to segregate my configuration?
SearchStax does not allow you to block bot traffic at the API level. Acquia will make this function available in an upcoming release. Acquia recommends that you use a Web Application Firewall (WAF) such as Cloudflare.
Is SearchStax FedRAMP compliant?
Acquia Search powered by SearchStax plans to include FedRAMP compliance in one of the upcoming releases.
How do I use multiple language support in Acquia Search powered by SearchStax?
Acquia Search powered by SearchStax provides support for multiple languages. This feature includes language-specific analytics, synonyms, stopwords, and ranking. For additional information, visit Supported languages.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Migrating to Acquia Search powered by SearchStax | Acquia Product Documentation
Cloud Platform
Migrating to Acquia Search powered by SearchStax
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform