Thanks for the clear explanation, this gives more context for the urgency.
> On Jan 17, 2024, at 3:04 PM, Amir Sarabadani
> wrote:
> What about only dropping it from Commons to reduce the risk of outage and
> leave the rest until the all are finished (or all except Wikidata)? You'd
> have to
Changing queries to support a new database format is one thing.
Writing migration code to deal with a situation that should not exist
(columns being dropped before the migration is completed) is another.
I suppose I am lucky in that the only tool I maintain that queries the
pagelinks table is
Hi!
Am Mi., 17. Jan. 2024 um 19:37 Uhr schrieb Ben Kurtovic <
wikipedia.ear...@gmail.com>:
> Hi Amir & others,
>
> I’m glad we are making changes to improve DB storage/query efficiency. I
> wanted to express my agreement with Tacsipacsi that dropping the data
> before the migration has completed
Hi Amir & others,
I’m glad we are making changes to improve DB storage/query efficiency. I wanted
to express my agreement with Tacsipacsi that dropping the data before the
migration has completed is a really bad outcome. Now tool maintainers need to
deal with multiple migrations depending on
Hi,
Yes that is correct but given the size these tables and the databases (for s4,
see https://phabricator.wikimedia.org/T343131) we don't really have a choice in
this specific case, Commons has grown to 1.8TB already. My apologies for the
inconvenience.
One thing that help here is that s3 and
Hi,
Do I understand correctly that I can’t use the old columns on s3, s4 and
s5 anymore, but I can’t use the new columns on s1 and s8 yet? Please
don’t do that, I don’t want to write code that first needs to consult
some list of wikis to decide how to query the database. I want to
migrate
