# Globalization with Elastic Search

**URL:** <https://discuss.elastic.co/t/globalization-with-elastic-search/234694>\
**Category:** Elasticsearch\
**Created:** [May 28, 2020, 8:46am UTC](https://discuss.elastic.co/t/globalization-with-elastic-search/234694 "2020-05-28T08:46:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![srikanthkadem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/srikanthkadem/32/40018_2.png) [@srikanthkadem](https://discuss.elastic.co/u/srikanthkadem)\
**Post date:** [May 28, 2020, 8:46am UTC](https://discuss.elastic.co/t/globalization-with-elastic-search/234694/1 "2020-05-28T08:46:56Z")

</div>

Hi All,

We have implemented ES Last Year(most of the information I gather from this discussion forum only 🙂 ) . We have implemented custom application to sync data from DB to ES indexes at regular intervals.  
At High level we have 2 indexes  
1 for Jobs  
2 for files  
Currently we are trying to implement Globalization in our application. Earlier application used to support English only.  
in order to support Globalization for search queries , how should I design the indexes . is it like having different index for each language like jobs\_en ,jobs\_fr.  
or Can I include new flag in jobs index to have different record for each language.  
Any other suggestions Also welcome.

Regards,  
Srikanth

---

<div class="post-metadata">

**Author:** ![srikanthkadem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/srikanthkadem/32/40018_2.png) [@srikanthkadem](https://discuss.elastic.co/u/srikanthkadem)\
**Post date:** [May 28, 2020, 2:10pm UTC](https://discuss.elastic.co/t/globalization-with-elastic-search/234694/2 "2020-05-28T14:10:50Z")

</div>

any help here is appreciated. Thanks in advance.

---

<div class="post-metadata">

**Author:** ![ssouris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ssouris/32/68657_2.png) [@ssouris](https://discuss.elastic.co/u/ssouris)\
**Post date:** [May 28, 2020, 2:57pm UTC](https://discuss.elastic.co/t/globalization-with-elastic-search/234694/3 "2020-05-28T14:57:06Z")

</div>

There are two good options:

1. Create an index per language, every index will have its own mapping and language analyzer on the relevant field
2. Create one index for all, but have multiple fields for each language, each with its own analyzer.

---

<div class="post-metadata">

**Author:** ![srikanthkadem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/srikanthkadem/32/40018_2.png) [@srikanthkadem](https://discuss.elastic.co/u/srikanthkadem)\
**Post date:** [June 3, 2020, 10:29am UTC](https://discuss.elastic.co/t/globalization-with-elastic-search/234694/4 "2020-06-03T10:29:09Z")

</div>

Yes @ssouris, I was thinking of same. Looking for opinions on this approach before starting. Thanks for the reply.

---

<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 1, 2020, 10:40am UTC](https://discuss.elastic.co/t/globalization-with-elastic-search/234694/5 "2020-07-01T10:40:49Z")

</div>

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