Page MenuHomePhabricator

Refactor Elastic TTM Server implementation to allow experimenting new queries without breaking production usage
Closed, DeclinedPublic1 Estimated Story Points


In order to improve TTM suggestions perf and coverage let's first refactor the way we build the query so that production usage remains un-changed while we experiment with new retrieval techniques.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
debt added a subscriber: debt.

We'll need to update our code for the translations now that we've upgraded to the latest version of down this technical debt.

debt lowered the priority of this task from Medium to Low.Oct 17 2017, 5:40 PM
debt moved this task from Up Next to search-icebox on the Discovery-Search board.

Moving to later, as we won't be able to get to this anytime soon. but we'll need it if we want to do new things with the translation server.

This would be a bit of work for this new feature. We might be able to take a look at doing something like this in Q3, FY2017/18, with @dcausse's tech debt workload.

Change 444251 had a related patch set uploaded (by DCausse; owner: DCausse):
[mediawiki/extensions/Translate@master] [WIP] Refactor ElasticTTMServer to accept multiple suggester implementations

If this is still needed, feel free to reopen.

Change 444251 abandoned by DCausse:

[mediawiki/extensions/Translate@master] [WIP] Refactor ElasticTTMServer to accept multiple suggester implementations


does not seem I will make progress on this anytime soon