@JKhondhu, Thanks for replay;
No in this case I am not thinking of using synonyms because I already provided synonyms per each analyzer of different languages.
My question is more from data model point of view, it is just like project structures nowadays is a question, by-feature or by-type where in our case the first approach is more like by-feature and the second approach is like by-type
Please also tell me more what goes in your mind, maybe I did not get your hint and question
Thanks in advance
@JKhondhu, In my queries, I will always have locale (en, de, ...) here we define it type, for example, let's assume a request comes in and it has the locale set to en, then the query clauses will target fields for en.
please tell me some also what you have in mind for queries by feature?
and one more question, if we define data model by type we will have all fields (field1, field2, field3) several times defined with the same name in the mapping (same index) but with different analyzers, it could be a problem?
This schema is much easier for search. In a multimatch you can use the wildcard en.*. So the recommendation would be to do this by language, absolutely.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.