Page MenuHomePhabricator

Add "wikishared" database to wiki replicas
Open, LowPublicFeature

Description

Why

What

  • Add wikishared to Quarry
  • Add wikishared to wiki replicas

Event Timeline

JJMC89 renamed this task from Add "wikishared" database to Quarry and to wiki replicas to Add "wikishared" database to wiki replicas.May 22 2025, 6:38 PM
JJMC89 added a project: Data-Services.
taavi triaged this task as Low priority.May 23 2025, 7:35 AM
taavi edited projects, added DBA; removed Quarry.
taavi moved this task from Inbox to Watching on the cloud-services-team board.
taavi subscribed.

wikishared resides on the x1 section which currently does not exist on the WMCS Wiki Replicas. My understanding is that this is something the DBAs have declined in the past, but I couldn't find any definitive answer on that except some "this is unlikely to happen" comments from almost a decade ago so tagging DBA to confirm.

I think this was more security related than anything else to be honest. We would need the green light from Security team on what can be exposed, what needs filtering, what needs redaction, what views can be created and how etc.

I think there is already a ticket for adding x1 to wikireplicas. We definitely should do that which helps us DBAs argue for moving data out of core sections that are pressured for capacity to x1. For example, I want to move wbc_entity_usage tables out of core dbs but x1 not replicating to the cloud blocks the move.

And I emphaisze that I agree with Manuel, privacy subteam of security must sign off on which tables can be replicated and which can't (and what views are needed) before we can make any move

fnegri subscribed.

I think there is already a ticket for adding x1 to wikireplicas.

I couldn't find one, so I created T395881: Set up x1 replication to Wiki Replicas.

Does anybody have a specific use case that needs to access these tables? If yes, that might help in bumping the priority of T395881: Set up x1 replication to Wiki Replicas.

We still have to get a review from Security before we can even think about implementing this.