# Multilingual completion suggester best practise

**URL:** <https://discuss.elastic.co/t/multilingual-completion-suggester-best-practise/97799>\
**Category:** Elasticsearch\
**Created:** [August 21, 2017, 4:37pm UTC](https://discuss.elastic.co/t/multilingual-completion-suggester-best-practise/97799 "2017-08-21T16:37:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sliu](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@sliu](https://discuss.elastic.co/u/sliu)\
**Post date:** [August 21, 2017, 4:37pm UTC](https://discuss.elastic.co/t/multilingual-completion-suggester-best-practise/97799/1 "2017-08-21T16:37:19Z")

</div>

We use a cluster for completion suggester. It needs to support auto-complete in multiple languages. I'm looking for best practice in index design. Here are two options:

1. a single index field for words and phrases in all languages, with standard analyzer. For instance both "solar eclipse" and "éclipse solaire" would be indexed in this field.
2. an index with multiple fields, each for a different language and that language analyzer applied. For instance, "solar eclipse" goes to suggester-en field which is analyzed by "english" analyzer. And "éclipse solaire" goes to suggester-fr field which is analyzed by "french" analyzer.

Any suggestions, preference? Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 18, 2017, 4:37pm UTC](https://discuss.elastic.co/t/multilingual-completion-suggester-best-practise/97799/2 "2017-09-18T16:37:23Z")

</div>

Closed on September 18, 2017, 4:37pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
