Now that WMF is going to setup ElasticSearch cluster, we cannot take advantage of it if we only support solr.
Version: master
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=54200
Now that WMF is going to setup ElasticSearch cluster, we cannot take advantage of it if we only support solr.
Version: master
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=54200
Merged:
f0d28a74dcb8ca3bc6b79e92e668bc1b9d2eac03
fe22ddf52c9693c46e354f451c93d8612d9f72af
See also:
http://laxstrom.name/blag/2014/07/07/translatewiki-net-summer-update/
Anything else to do here?
SearchTranslations was switched too, for translatewiki.net, with https://gerrit.wikimedia.org/r/#/c/145437/ ; is there a bug for it to support ES, and should one be created? See bug 68518.
SearchTranslations does support ES, what makes you think it doesn't?
The main remaining issue is translation memory query performance. Planned work is at:
https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4285
https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4286
https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4287