Page MenuHomePhabricator

Refactor Elastic TTM Server implementation to allow experimenting new queries without breaking production usage
Open, LowPublic1 Story Points

Description

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

dcausse created this task.Oct 9 2017, 2:20 PM
Restricted Application added a project: Discovery. · View Herald TranscriptOct 9 2017, 2:20 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Stryn added a subscriber: Stryn.Oct 9 2017, 3:01 PM
debt moved this task from needs triage to Up Next on the Discovery-Search board.Oct 12 2017, 5:11 PM
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 ElasticSearch...pay down this technical debt.

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

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.

debt added a comment.Nov 30 2017, 8:06 PM

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

https://gerrit.wikimedia.org/r/444251

dcausse claimed this task.Jul 6 2018, 4:37 PM