Change Details

Apply T312266 to wmf wikis # **ALTERs to run:** https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/817875/1/sql/mysql/patch-cx_translators-unique-to-pk.sql # **Where to run those changes:** All wikipedias (tables on x1.wikishared) + testwiki # **When to run those changes:** any time # **If the schema change is backwards compatible:** Yes # **If the schema change has been tested already on some of the test/beta wikis:** beta already running with the new schema # **if the data should be made available on the labs replicas and/or dumps:** no change of the existing rules Maybe it is better to apply the DROP + ALTER in reverse order in production to avoid that there is a time gap without unique constraint, because both statement as written in the linked file are not atomic (as far as I know, not sure if a atomic way is possible) Progress [x] s3 (testwiki) [] x1 (wikishared) ** [] eqiad ** [x] codfw

Apply T312266 to wmf wikis # **ALTERs to run:** https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/817875/1/sql/mysql/patch-cx_translators-unique-to-pk.sql # **Where to run those changes:** All wikipedias (tables on x1.wikishared) + testwiki # **When to run those changes:** any time # **If the schema change is backwards compatible:** Yes # **If the schema change has been tested already on some of the test/beta wikis:** beta already running with the new schema # **if the data should be made available on the labs replicas and/or dumps:** no change of the existing rules Maybe it is better to apply the DROP + ALTER in reverse order in production to avoid that there is a time gap without unique constraint, because both statement as written in the linked file are not atomic (as far as I know, not sure if a atomic way is possible) Progress [x] s3 (testwiki) [x] x1 (wikishared) ** [x] eqiad ** [x] codfw

Apply T312266 to wmf wikis # **ALTERs to run:** https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/817875/1/sql/mysql/patch-cx_translators-unique-to-pk.sql # **Where to run those changes:** All wikipedias (tables on x1.wikishared) + testwiki # **When to run those changes:** any time # **If the schema change is backwards compatible:** Yes # **If the schema change has been tested already on some of the test/beta wikis:** beta already running with the new schema # **if the data should be made available on the labs replicas and/or dumps:** no change of the existing rules Maybe it is better to apply the DROP + ALTER in reverse order in production to avoid that there is a time gap without unique constraint, because both statement as written in the linked file are not atomic (as far as I know, not sure if a atomic way is possible) Progress [x] s3 (testwiki) [x] x1 (wikishared) ** [x] eqiad ** [x] codfw