Last modified: 2014-06-16 12:41:04 UTC
This will be caused by https://gerrit.wikimedia.org/r/#/c/108951/ which is a fix for bug 60302 and bug 54937. This seems less bad then not finding them at all given that they are stopwords, after all, so they should be on most pages any way.
The fix for this unfortunately requires me to make some changes to Elasticsearch and get them landed.
Looks like the Elasticsearch folks were already working on it and have got it lined up for 1.1. This one doesn't have an issue for some reason, just a pull request: https://github.com/elasticsearch/elasticsearch/pull/5005
Is this the reason why, if I look for an exact match of a sentence (by quoting it), I'm also provided with many results which don't contain my exact sentence but instead my sentence + stopwords in the middle of it?
We've had 1.1 for a bit now and we're looking at 1.2. Upstream issue seems closed & merged so can we consider this resolved (or possible to resolve) now?
(In reply to Chad H. from comment #4) > We've had 1.1 for a bit now and we're looking at 1.2. Upstream issue seems > closed & merged so can we consider this resolved (or possible to resolve) > now? Nik: ?
This one takes longer to solve then just flipping a switch. IIRC we'd have to rewrite the query parser and I'm not sure we have the energy for that right now. I've removed the keywords but I'm sure its not the most important thing for us to be working on right now.
