Cloud Platform
Selecting a language
Acquia Search can index websites in most languages, but it passes content through a language-specific stemmer during indexing, depending on the search schema that you configured for your website.
To use a language-specific Solr configset, you can use the built-in functionality in the Search API Solr Drupal module to generate a new configset optimized for a specific language or languages. You can then deploy it by following Custom Solr configuration.
The Search API Solr module runs a check to compare the configuration in Drupal and Solr, and shows an error message if it detects a mismatch.
If you’re using an outdated version of Drupal and Solr, you get an error message such as You are using outdated Solr configuration set. For more information, see Troubleshooting the Search API Solr message.
The full set of languages supported by Acquia Search is listed at https://solr.apache.org/guide/8_11/language-analysis.html.
Although the default schema of Acquia Search optimizes for English searches, Acquia also provides schemas in other languages. Most of the Latin-based languages have grammatical and linguistic similarities. Therefore, you can use them in a straightforward manner.
Non-Latin languages, such as Chinese, Japanese, and Korean (CJK), use different stemming and spacing rules compared to Latin-based languages. The Solr / Lucene search engine must handle non-latin languages differently than Latin-based languages.
For instructions on how to add support for the Chinese, Japanese, and Korean (CJK) languages, see Custom Solr configuration.
Acquia recommends you to test your configuration before applying them to your Solr instance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform