Change Details

Move eventlogging backend to hadoop The eventlogging mysql consumer and storage have many issues and perhaps the most poignant is scaling when it comes to tech but also the lack of DBA resources to dedicate to general upkeeping to the eventlogging boxes. Eventloggindg data is already on hadoop but needs a lot more friendlness when it comes to queries. This is the parent task to keep track of the work to move EL backend to hadoop.

Move eventlogging backend to hadoop The eventlogging mysql consumer and storage have many issues and perhaps the most poignant is scaling when it comes to tech but also the lack of DBA resources to dedicate to general upkeeping to the eventlogging boxes. Also, there are significant scalability issues, it is been about 6 months that all new data from eventlogging is only persisted in hadoop and schemas need to be whitelisted to be persisted in eventlogging. This is the parent task to keep track of the work to deprecate entirely the mysql eventlogging consumer in prod.

Move eventlogging backend to hadoop The eventlogging mysql consumer and storage have many issues and perhaps the most poignant is scaling when it comes to tech but also the lack of DBA resources to dedicate to general upkeeping to the eventlogging boxes. Also, Eventloggindg data is already on hadoop but needs a lot more friendlness when it comes to queries.there are significant scalability issues, it is been about 6 months that all new data from eventlogging is only persisted in hadoop and schemas need to be whitelisted to be persisted in eventlogging. This is the parent task to keep track of the work to move EL backend to hadoop. deprecate entirely the mysql eventlogging consumer in prod.