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.
Description
Details
Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
mediawiki/extensions/Translate | master | +638 -173 | [WIP] Refactor ElasticTTMServer to accept multiple suggester implementations |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T195760 Language Annual Plan 2018-2019 | |||
Resolved | Nikerabbit | T204818 Language tools maintenance intervention: Improve the quality of translations for Translate extension | |||
Open | None | T101236 TTMServer performance and coverage issues | |||
Declined | dcausse | T177774 Refactor Elastic TTM Server implementation to allow experimenting new queries without breaking production usage |
Event Timeline
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.
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
Change 444251 abandoned by DCausse:
[mediawiki/extensions/Translate@master] [WIP] Refactor ElasticTTMServer to accept multiple suggester implementations
Reason:
does not seem I will make progress on this anytime soon