| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Refactor completion to support elastic5 | mediawiki/extensions/CirrusSearch | es5 | +254 -714 |
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | debt | T151324 [epic] System level upgrade for cirrus / elasticsearch | |||
| Resolved | Deskana | T154501 [Epic, Q3 Goal] Upgrade search systems to Elasticsearch 5 | |||
| Resolved | dcausse | T156010 Migrate the completion suggester client code to elastic 5.x |
Event Timeline
Comment Actions
Change 333971 had a related patch set uploaded (by DCausse):
Refactor completion to support elastic5
Comment Actions
Putting this on hold, basic functionalities have been ported.
To move forward I'd need to have relforge upgraded to es5 to have more data and make sure ranking works as expected.
Comment Actions
When we first deploy this, we might be in the unfortunate situation of having a titlesuggest index built by 2.x, but being served by 5.x. Currently that results in opensearch responses such as:
[ "s", ["147734:t:Shinjuku" ], [ "" ], [ "http://en.wiki.local.wmftest.net:8080/wiki/147734:t:Shinjuku" ] ]
I'm not sure the best way to handle ... perhaps we briefly disable the completion suggester until we have re-built indices with 5.x and allow it to use prefix search instead.