Indexing and normalisation of Cyrillic characters about api

[missinglink]

Hmm yes I can confirm the issue you are seeing, it seems to be affecting queries to the /v1/autocomplete endpoint but not the /v1/search endpoint, which helps narrow down the scope.

We use the icu-folding filter in elasticsearch to 'fold' the Cyrillic form to the Latin form.

It seems as though we are using this filter correctly in all of the analyzers, with the exception of peliasHousenumber which has a numeric character filter, and so it doesn't apply.

I'm not really sure what's going on here, the expected behaviour is that we fold Cyrillic to ASCII for precisely this purpose.

[orangejulius]

Ah, very nice discovery @missinglink. I think we originally discovered this issue back in pelias/pelias#833 but never narrowed down the cause.

It feels like adding the icu-folding filter is relatively safe, maybe we should try that out?