{"push_id":1268556983,"size":1,"distinct_size":1,"ref":"refs/heads/trunk","head":"1e8f2651dacf5daef55d75c7b9b12492962e7921","before":"9eb92dab0d24813e9a3871f0c7038920797c0466","commits":[{"sha":"1e8f2651dacf5daef55d75c7b9b12492962e7921","author":{"name":"Grant Henke","email":"92cb0c65dbf8ff1baaf010de530f6f36b8383062@gmail.com"},"message":"FLUME-2972. Handle offset migration in the new Kafka Channel\n\nOffsets tracking the position in Kafka consumers change from using\nZookeeper for offset storage to Kafka when moving from Kafka 0.8.x to\n0.9.x.\n\nFLUME-2823 makes the client change in the Kafka Channel but does not\nensure existing offsets get migrated in order to continue consuming\nwhere it left off.\n\nFlume should have some automated logic on startup to check if Kafka\noffsets exist, if not and migration is enabled (by default) then copy\nthe offsets from Zookeeper and commit them to Kafka.\n\nReviewers: Balázs Donát Bessenyei, Denes Arvay, Mike Percy\n\n(Grant Henke via Mike Percy)","distinct":true,"url":"https://api.github.com/repos/mapr/flume/commits/1e8f2651dacf5daef55d75c7b9b12492962e7921"}]}
{"actor":{"display_login":"jfota"}}