>Dynamically added EL tables make it all a little more complex, but not a problem technically, since I understand each new >EL table would require Legal OK first, just like mediawiki tables do
Ok, for the sake of clarity let's make sure we are talking about the same thing: EL tables are created per schema version, so, let's say, table NavigationTiming_1000 is being replicated. An schema version change happens and then there is a new table NavigationTiming_1001 that has couple additional fields but other than that is identical to the prior table.

Will the replication of this second table be automatic or will it need manual intervention?






On Fri, Aug 22, 2014 at 8:49 AM, Sean Pringle <springle@wikimedia.org> wrote:
On Fri, Aug 22, 2014 at 4:05 PM, Nuria Ruiz <nuria@wikimedia.org> wrote:
>While I realize that only certain EL tables will be replicated,
Not only that, only "some" fields from "some" tables will be replicated. Also as you know EL creates new tables on demand so the number of tables to replicate is dynamically changing.  
Do these points affect the request in any way?

My points all still apply regardless.

The filtering of specific fields is the task of the sanitarium servers which sit between production and labsdb. We use a combination of replication rules to filter tables and triggers to null out sensitive fields, then SQL views and specific permissions to hide some fields entirely.

Dynamically added EL tables make it all a little more complex, but not a problem technically, since I understand each new EL table would require Legal OK first, just like mediawiki tables do. There is (I hope) no expectation of instant or automated changes to the replication setup.