# Implementation of multi lingual search

**URL:** <https://discuss.elastic.co/t/implementation-of-multi-lingual-search/14167>\
**Category:** Elasticsearch\
**Created:** [October 30, 2013, 7:58am UTC](https://discuss.elastic.co/t/implementation-of-multi-lingual-search/14167 "2013-10-30T07:58:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [October 30, 2013, 7:58am UTC](https://discuss.elastic.co/t/implementation-of-multi-lingual-search/14167/1 "2013-10-30T07:58:00Z")

</div>

Hi everyone - We have been exploring what it would take to implement multi  
lingual search solution using ElasticSearch. In case anyone has already  
done it, it would be great to hear their experience on the same. A few  
questions I have is:

1. Would one have to create separate index for each language?
2. If the index is separate, would it be a very different mapping?
3. Would the queries be constructed in different ways for different  
languages?

I am just keen to listen to the key considerations to be taken into account  
when thinking of implementing it.

Thanks much!

-Amit.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [October 30, 2013, 8:16am UTC](https://discuss.elastic.co/t/implementation-of-multi-lingual-search/14167/2 "2013-10-30T08:16:52Z")

</div>

1. You do not need separate indexes. Language can be per field (or even  
mixed into a single field).

2. You can assign each field different analyzers. If you use index types,  
there is nothing to prevent you from setting up a field "content", and  
assign english analyzer to it in index type "english", german analyzer in  
index type "german", french analyzer in index type "french" and so on. You  
can also use minimal or no stemming at all and use a single field for all  
languages. It can be useful if you do not know what languages you have to  
index. You can also use the langdetect plugin in that case and attach the  
language code in the doc for search filter. This totally depends on your  
requirements.

3. No.

You do not mention the biggest challenge for multilingual search. It is  
language independent normalization and case folding for robust search. The  
ICU analysis plugin is very valuable for this

> **[elastic/elasticsearch-analysis-icu](https://github.com/elastic/elasticsearch-analysis-icu)**
>
> elasticsearch-analysis-icu - ICU Analysis plugin for Elasticsearch

Jörg

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\
**Post date:** [October 30, 2013, 8:18am UTC](https://discuss.elastic.co/t/implementation-of-multi-lingual-search/14167/3 "2013-10-30T08:18:09Z")

</div>

It all really, really depends on your content and business requirements,  
and the amounts of data you have.

For us it makes sense to have everything in one index but use different  
analyzer for each document based on the main language detected for the  
text. But it's just our way of doing that.

On Wed, Oct 30, 2013 at 9:58 AM, Amit Soni [amitsoni29@gmail.com](mailto:amitsoni29@gmail.com) wrote:

> Hi everyone - We have been exploring what it would take to implement multi  
> lingual search solution using Elasticsearch. In case anyone has already  
> done it, it would be great to hear their experience on the same. A few  
> questions I have is:
> 
> 1. Would one have to create separate index for each language?
> 2. If the index is separate, would it be a very different mapping?
> 3. Would the queries be constructed in different ways for different  
> languages?
> 
> I am just keen to listen to the key considerations to be taken into  
> account when thinking of implementing it.
> 
> Thanks much!
> 
> -Amit.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 2:09am UTC](https://discuss.elastic.co/t/implementation-of-multi-lingual-search/14167/4 "2017-07-06T02:09:53Z")

</div>


