Before we stop writing old on WMF production, the value in extension.json should be changed to no longer write old.
Acceptance criteria
- Set wgCheckUserEventTablesMigrationStage to SCHEMA_COMPAT_NEW in extension.json
Before we stop writing old on WMF production, the value in extension.json should be changed to no longer write old.
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Dreamy_Jazz | T360686 Stop writing old on testwiki | ||
| Resolved | Dreamy_Jazz | T353953 Don't use actor IDs for private CheckUser events when these actions are performed by IP addresses | ||
| Resolved | Dreamy_Jazz | T366505 Stop writing old for event table migration in extension.json | ||
| Resolved | Dreamy_Jazz | T329189 Add read new support to Special:Investigate for event table migration | ||
| Resolved | Dreamy_Jazz | T341827 Add read new support to the CheckUser API | ||
| Resolved | Dreamy_Jazz | T341829 Enable read new for the event table migration | ||
| Resolved | Dreamy_Jazz | T328992 Add read new support to Special:CheckUser for event table migration | ||
| · · · |
Change #1038398 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):
[mediawiki/extensions/CheckUser@master] Set event tables migration to SCHEMA_COMPAT_NEW in extension.json
Change #1038397 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):
[mediawiki/extensions/CheckUser@master] Update comments to reflect event table migration
Change #1038396 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):
[mediawiki/extensions/CheckUser@master] Add UserMerge support for cu_log_event and cu_private_event
Change #1038396 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Add UserMerge support for cu_log_event and cu_private_event
Change #1038397 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Update comments to reflect event table migration
Change #1038398 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Set event tables migration to SCHEMA_COMPAT_NEW in extension.json
For QA, you can check that for a variety of actions the database does not store any rows with cuc_only_for_read_old in the cu_changes table.
You can also check that no actions are in cu_changes with cuc_type as RC_LOG.
It is important to note that rows may not meet the above conditions if they were already in the database before you started QA'ing this ticket. As such, you may want to note when you started QA'ing this ticket and filter out rows that were made before that by using cuc_timestamp > YYYYMMDDHHMMSS as a condition in the query.