On Mon, Jul 18, 2022 at 12:42 PM Roy Smith roy@panix.com wrote:

What are the user-visible changes in 7.10? More specifically, does this address the lack of access control I discussed in https://wikitech.wikimedia.org/wiki/Help_talk:Toolforge/Elasticsearch?

There are lots of user-visible changes in 7.10 (too numerous to mention, see the elasticsearch release notes for more info) if you are talking to the elasticsearch api's directly, but critically the mentioned upgrade to elastic 7.10 is unrelated to the Toolforge cluster. This upgrade to 7.10 is specifically for the CirrusSearch clusters in wmf production that support on-site search.

Erik B.

On Jul 18, 2022, at 3:23 PM, Mike Pham mpham@wikimedia.org wrote:

Hi all,

I originally sent this email out on 20 May, 2022, but it seems like it didn’t go out to everybody, unfortunately.

We are beginning the process of undeploying API Feature Usage https://phabricator.wikimedia.org/T313248 this week, and apologize for the confusion, and what is now short notice for those of you who were not aware of this announcement previously.

Best,

—

*Mike Pham* (he/him) Sr Product Manager, Search Wikimedia Foundation https://wikimediafoundation.org/

On 20May, 2022 at 10:18:44, Mike Pham (mpham@wikimedia.org) wrote:

Hi all,

The Wikimedia Foundation Search team is currently working on updating our Elasticsearch version to 7.10 https://phabricator.wikimedia.org/T263142 from version 6.8.20. Our goal is to finish this work in the next couple of months. Being on the latest (license-compatible) version will help ensure the stability and reliability of our search infrastructure.

This update will include 2 breaking changes:

1. Cloudelastic will be affected by breaking changes, with more

details below. The interface might also change slightly.

1. https://www.elastic.co/guide/en/elasticsearch/reference/7.17/breaking-change... 2. https://www.elastic.co/guide/en/elasticsearch/reference/7.10/migrating-7.10....

   2. The API Feature Usage extension

https://www.mediawiki.org/wiki/Extension:ApiFeatureUsage, whose functionality is unrelated to search, will no longer be supported. This low-usage extension is currently implemented in a complicated and brittle way that depends on Elasticsearch, which creates development drag on the Search team’s work in order to continuously maintain and upkeep.

While in the short term API Feature Usage will be sunsetted, we recognize that it’s probably useful for some users, and we encourage others to continue to support and develop this extension in the longer term, without its brittle dependency on Elasticsearch.

Though the Elasticsearch upgrade will provide overall net benefits, we recognize that these breaking changes will unfortunately affect some users, and appreciate your understanding as we improve our search infrastructure.

Best, Search Platform

—

*Mike Pham* (he/him) Sr Product Manager, Search Wikimedia Foundation https://wikimediafoundation.org/

---

Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

---

Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

On Tue, 2022-07-19 at 11:00 +0100, Cigaryno wrote:

Is the ApiFeatureUsage extension going to work on newer versions of MediaWiki even if it will be undeployed from WMF wikis?

Assumption in short: "Yes" if someone steps up and volunteers to maintain that code base. If not, then probably "Not anymore at some unknown point in the future" as code will bitrot.

Cheers, andre