This schema MobileWikiAppShareAFact is sending a lot of events, maybe is
worth thinking whether we need that many. It is again a case where tables
are becoming huge and hard to query fast.
cc-ing Jon as schema owner.
Can this data be sampled at a higher sampling rate? I have filed a ticket
to this fact:
On Tue, Dec 22, 2015 at 8:35 AM, Adam Baso <abaso(a)wikimedia.org> wrote:
> Replacing mobile-tech with mobile-l (internal mobile-tech list
> On Tuesday, December 22, 2015, Nuria Ruiz <nuria(a)wikimedia.org> wrote:
>> As part of our effort of converting eventlogging mysql database to the
>> tokudb engine we need to stop eventlogging events from flowing into the MobileWikiAppShareAFact
>> table, we are using this one table to see how long the conversion will take
>> in order to plan for a larger outage window.
>> Let us know if data should be backfilled as it can be, we anticipate
>> events will not flow into table for the better part of one day.
> Mobile-l mailing list