Nik Spyratos
12/11/2025, 6:27 AMNik Spyratos
12/11/2025, 6:28 AMNik Spyratos
12/11/2025, 6:29 AMNik Spyratos
12/11/2025, 8:06 AMNik Spyratos
12/11/2025, 12:28 PMAlan Martini
12/11/2025, 1:47 PMI'd like my search behaviour to be that latin character queries prioritise exact latin character matches, to then fall back to the locale-specific matches if none is found.On each search, only the first query_by field locale is applied, so this fallback mechanism cannot be normally achieved. Not only that, but on the tokenization process, every word is normalized (so in localized fields, for e.g. café becomes cafe). This process happen both on the indexed fields as in the query. To achieve what you'll want, you'll need the same information duplicated on two fields (as you've guessed), with one being a locale field (which will get normalized) and the other being a non-locale field (which will not get normalized). Then, on your app side, you detect if the query has any diacritics. If yes, query the un-locale field first.
Nik Spyratos
12/11/2025, 2:16 PMNik Spyratos
12/11/2025, 2:21 PMOn each search, only the first query_by field locale is applied, so this fallback mechanism cannot be normally achieved.Am I understanding this correctly: in other words, if I have
title_de and title_fr in my query_by, whichever is defined first will be the only locale applied?
Another idea I've considered is separating the collections entirely per locale and doing a multi_search across them. Would the same limitation apply there?Kishore Nallan
12/12/2025, 7:34 AM