Change Details

Flip blacklist for MySQL eventlogging consumer to be a whilelist of allowed schemas. We contiously run into problems with MYSQL processor in eventlogging. (example: https://phabricator.wikimedia.org/T203592) Going fowardds by default all events should go to hadoop and only a whitelist of events should appear on MYSQL, we can build whitelist by looking at the topics in kafka (eventlogging-valid-mixed) from which data to MySQL is persisted.

Flip blacklist for MySQL eventlogging consumer to be a whitelist of allowed schemas. We continuously run into problems with MYSQL processor in eventlogging. (example: https://phabricator.wikimedia.org/T203592) Going forwards by default all events should go to hadoop and only a whitelist of events should appear on MYSQL, we can build whitelist by looking at the topics in kafka (eventlogging-valid-mixed) from which data to MySQL is persisted.

Flip blacklist for MySQL eventlogging consumer to be a whilwhitelist of allowed schemas. We continuously run into problems with MYSQL processor in eventlogging. (example: https://phabricator.wikimedia.org/T203592) Going fowarddsrwards by default all events should go to hadoop and only a whitelist of events should appear on MYSQL, we can build whitelist by looking at the topics in kafka (eventlogging-valid-mixed) from which data to MySQL is persisted.