I'm not applying #blocked-on-schema-change to this change per the advice "Other 'cleanup' schema changes (e.g. a column that is stopped being used but it is not blocking code). While those are real schema changes, if they don't block code deployments, just use the #DBA tag to avoid prioritizing them over those that are actual blockers."
From the checklist at https://wikitech.wikimedia.org/wiki/Schema_changes:
# **ALTERs to run:** https://gerrit.wikimedia.org/r/c/393929/14/maintenance/archives/patch-drop-ar_text.sql
# **Where to run those changes:** all.dblist
# **When to run those changes:** After 1.32.0-wmf.1 or later is deployed and Toolforge views are updated. No other time constraints.
# **If the schema change is backwards compatible:** Yes. As of 1.32.0-wmf.1 these columns are no longer used.
# **If the schema change has been tested already on some of the test/beta wikis:** Yes.
# **if the data should be made available on the labs replicas and/or dumps:** No new data is being added. Toolforge views need to be updated to remove reference to ar_flags, see {T189141}
Schema change progress:
[] s1
** [x] codfw
** [] eqiad progress T192926#4275246 (only primary master pending, but it will be failed over the 18th July - so it will get done that day T197069)
[] s2
** [x] codfw
** [x] eqiad progress T192926#4312198
[] s3
** [x] codfw
** [] eqiad
[] s4
** [x] codfw
** [x] eqiad progress T192926#4270988
[] s5
** [x] codfw
** [x] eqiad progress T192926#4248158
[] s6
** [x] codfw
** [x] eqiad progress T192926#4260470
[] s7
** [x] codfw
** [] eqiad progress T192926#4387328
[] s8
** [x] codfw
** [x] eqiad progress T192926#4320910