Update patch set 14

Authored by Tgr on Aug 25 2017, 9:00 PM.

Unpublished Commit · Learn More

Not On Permanent Ref: This commit is not an ancestor of any permanent ref.


Update patch set 14

Patch Set 14:

I would actually recommend against that- schema changes on

> production are hard, and any optimization normally requires those.

I was thinking of index changes - are those hard to do, as well? Initially the Android app will be the only one to use the feature, so even if everyone opts in, we would be looking at a million lists and ten million list entries. Adding a new index to something of that size should be on the scale of a few hours (annoying, but not impossible) I think?

> For production testing (assuming beta has already been done),
> smaller deployment would be required (e.g. only deploy to
> testwiki).

Not sure how much sense it would make, given that there all sites will use a single shared database. I guess we could configure testwiki to have a separate database of its own.
(Beta deployment is planned around end of Q1. The apps will use this extension through a RESTBase proxy which still needs to be written.)

> Which shard are you thinking to deploy this to?

x1, per T164990#3264314.

Patch-set: 14


Gerrit Code Review <gerrit@wikimedia.org>Aug 25 2017, 9:00 PM
rERLSa460c29fac15: Update patch set 14

Event Timeline

Gerrit Code Review <gerrit@wikimedia.org> committed rERLSde02d3b201f1: Update patch set 14 (authored by Tgr).Aug 25 2017, 9:00 PM

Empty Commit

This commit is empty and does not affect any paths.