Language Optimization

When creating a new Engine during signup, from within your dashboard, or via API, you may select a language type:

Language Optimization - Creating a Korean Engine.

curl -X POST 'https://[instance id].ent-search.[region].[provider].cloud.es.io:443/api/as/v1/engines' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer private-xxxxxxxxxxxxxxxx' \
-d '{
  "name": "national-parks-demo",
  "language": "ko"
}'

If your Engine spans multiple languages, consider using the default Universal option.

Language optimization works best when using the ICU Analysis plugin. To use this plugin, you must add it to your deployment before you create the engine you’d like to optimize in Enterprise Search.

To add the plugin, refer to the documentation for your deployment type:

Once you have selected your language, no further configuration is required — your Engine is optimized for that language.

What does it mean to be language optimized?

Features like stemming, bigram matching, phrase matching, and typo tolerance will be fine-tuned for your chosen language when making search requests.

If the ICU Analysis Plugin is available, Enterprise Search is able to leverage the extended support for Asian languages as text is indexed into your Engine.

You can select from one of the supported language settings:

The language codes adhere to a subset of the IETF RFC 5646, which coincide with ISO 639-1 and ISO 3166-1.

Design your Engines in advance for your language requirements, as once it has been created with a specific language, it cannot be changed. Any changes would require the creation of a new Engine and migration of desired settings.

Selecting "Universal" is a great option for Engines needing multiple language support. However, for a fully optimized language experience, it is recommended to create an engine per language. Meta Engines will take those language settings into consideration for a consolidated search experience.