The renameuser_queue table doesn't appear to be replicated to the Labsdb replicas — this makes sense, as these requests often contain private information.
However, it would be useful to have access to the following, non-sensitive, columns in the table:
- rq_id
- rq_requested_ts
- rq_status
- rq_completed_ts
- rq_performer
The initial usecase I can think of is checking global renamer's activity (i.e. to see if the right needs to be revoked for inactivity) — we're unable to check queue rejections as these aren't searchable.
I have a patch almost ready to submit which adds
renameuser_queue,req_id,K renameuser_queue,rq_name,F renameuser_queue,rq_wiki,F renameuser_queue,rq_newname,F renameuser_queue,rq_reason,F renameuser_queue,rq_requested_ts,K renameuser_queue,rq_status,K renameuser_queue,rq_completed_ts,K renameuser_queue,rq_deleted,F renameuser_queue,rq_performer,K renameuser_queue,rq_comments,F
to modules/role/files/mariadb/filtered_tables.txt, which I think is correct per the Labsdb redaction page (though I think I'm missing "step 2"?)
I'm not really sure who "looks after" this, nor if we need to get Legal's approval — guidance there would be appreciated 🙂