Today we use a suggestion field that is built against the title and redirect data. This field is used by the phrase suggester with a prefix length of 2. In other words if the typo appears in the first two characters all suggestions generated by the phrase suggester would be bad. Reducing the prefix length can hurt performances, another technique is to build a second suggestion field with a "reverse" filter.
|Resolved||Deskana||T125603 EPIC: Review current ElasticSearch configuration, and use relevance lab to run tests to optimise the configuration to improve search result relevance|
|Resolved||dcausse||T107006 Add a "reverse" suggestion field to workaround the prefix length limitation (typos suggestion)|
|Resolved||dcausse||T106692 Allow customization of "Did you mean" suggestions.|
|Resolved||dcausse||T107427 EPIC: Test if a reverse field can help to display more and better suggestions|
|Resolved||dcausse||T108034 Fix a bug in PhraseSuggester that prevents us to use the reverse field|
|Resolved||Gehel||T122697 Upgrade ElasticSearch to 1.7.5|
|Resolved||Gehel||T127074 cirrus browser tests fail on Vagrant (and probably in other places)|
|Resolved||EBernhardson||T127831 Upgrade ruflin/elastica to 2.3.1|
We will have elastic 1.7.5 soon in production, I think it'd be nice to finish what we started on this task.
The top query for the last week of January 2016 was Terry Wigan which is certainly a typo to Terry Wogan (a radio and TV broadcaster who died this week).
I think that the reverse field would have helped in this case.