Change Details

Similar to {T268861} and {T268862}; Translate uses Elastica's Match class in ElasticSearchTTMServer

Similar to {T268861} and {T268862}; Translate uses Elastica's Match class in ElasticSearchTTMServer I note the #mediawiki_language_extension_bundle/translate support here might be a problem. The replacement MatchQuery class is now in master, and backported to 1.35.... But it's not in 1.34 (of Elastica); but that is EOL for most purposes. We could just backport {290255cc67b07d11b21a850404203adb5acd8de2} and then {65ac9f8baa7bbcc52754c6c033d9e1b003b4e688} to 1.34 if it's needed.. Or if the next release of MLEB is going to require MW >= 1.35, we don't need to worry about this anyway

Similar to {T268861} and {T268862}; Translate uses Elastica's Match class in ElasticSearchTTMServer I note the #mediawiki_language_extension_bundle/translate support here might be a problem. The replacement MatchQuery class is now in master, and backported to 1.35.... But it's not in 1.34 (of Elastica); but that is EOL for most purposes. We could just backport {290255cc67b07d11b21a850404203adb5acd8de2} and then {65ac9f8baa7bbcc52754c6c033d9e1b003b4e688} to 1.34 if it's needed.. Or if the next release of MLEB is going to require MW >= 1.35, we don't need to worry about this anyway