This table is marked as visibility: private in the table catalog, that must be updated before this could go forward.

Seems like it was previously available in wiki replicas (added in 2014, see T59491).

I don't think this was exposed in wikireplica recently otherwise it would have been shown in maintain-views (in fullViews or custom ones) neither in filtered_tables.txt. Mid-2010s the whole replication to wikireplicas got revamped.

This is not DBA work. I stay subscribed if you still need one.

We're waiting on Data-Engineering to validate.

I pinged Data-Engineering on slack to get validation.

I have reviewed the table, it contains only a features list with how many users use it. It is safe to replicate.

Thanks @Gehel for asking for clarification. I agree with Joseph and approve the change, please move forward. Thanks!

Change #1298329 had a related patch set uploaded (by SD0001; author: SD0001):

[operations/puppet@production] tables-catalog: set betafeatures_user_counts to public visibility

https://gerrit.wikimedia.org/r/1298329

In https://gerrit.wikimedia.org/r/c/operations/puppet/+/1298329/comments/9648a202_f275769a, @Ladsgroup wrote:

I'd also would need a sign off from the privacy team

Hi @Rsilvola/@Htriedman, could you review and approve adding this table to the public replicas?

For reference, this is the sample content of the table:

mysql:research@dbstore1008.eqiad.wmnet [enwiki]> select * from betafeatures_user_counts limit 10;
+------------------------------------------+--------+
| feature                                  | number |
+------------------------------------------+--------+
|                                          |      0 |
| HHVM                                     |   4957 |
| advancedsearch                           |  18537 |
| betafeatures-geonotahack                 |   9884 |
| betafeatures-vector-compact-personal-bar |  16450 |
| betafeatures-vector-typography-update    |   9117 |
| cirrussearch-completionsuggester         |   9307 |
| cirrussearch-default                     |  21401 |
| codemirror-beta-feature-enable           |  32693 |
| codemirror-syntax-highlight              |  24122 |
+------------------------------------------+--------+
10 rows in set (0.001 sec)

cc: @aranyap

Hi @SD0001 , is there any possible way for this data to be correlated back to an individual?

The table doesn't have any user identifiers, so I don't see a way.

Thank you @SD0001 . The Product Safety & Integrity team has reviewed this table and is considering this to be a low privacy risk with no blockers to proceed.