[
https://issues.apache.org/jira/browse/FLUME-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438282#comment-15438282
]
Hudson commented on FLUME-2972:
-------------------------------
FAILURE: Integrated in Jenkins build Flume-trunk-hbase-1 #199 (See
[https://builds.apache.org/job/Flume-trunk-hbase-1/199/])
FLUME-2972. Handle offset migration in the new Kafka Channel (mpercy:
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=1e8f2651dacf5daef55d75c7b9b12492962e7921])
* (edit)
flume-ng-channels/flume-kafka-channel/src/main/java/org/apache/flume/channel/kafka/KafkaChannel.java
* (edit)
flume-ng-channels/flume-kafka-channel/src/main/java/org/apache/flume/channel/kafka/KafkaChannelConfiguration.java
* (edit)
flume-ng-channels/flume-kafka-channel/src/test/java/org/apache/flume/channel/kafka/TestKafkaChannel.java
* (edit) flume-ng-doc/sphinx/FlumeUserGuide.rst
* (edit) flume-ng-channels/flume-kafka-channel/pom.xml
> Handle offset migration in the new Kafka Channel
> ------------------------------------------------
>
> Key: FLUME-2972
> URL: https://issues.apache.org/jira/browse/FLUME-2972
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.7.0
> Reporter: Grant Henke
> Assignee: Grant Henke
> Fix For: v1.7.0
>
> Attachments: FLUME-2972-1.patch, FLUME-2972-2.patch, FLUME-2972.patch
>
>
> Offsets tracking the position in Kafka consumers change from using zookeeper
> for offset storage to Kafka when moving from 0.8.x to 0.9.x.
> FLUME-2823 makes the client change in the Kafka Channel but does not ensure
> existing offsets get migrated in order to continue consuming where it left
> off.
> Flume should have some automated logic on startup to check if Kafka offsets
> exist, if not and migration is enabled (by default) then copy the offsets
> from Zookeeper and commit them to Kafka.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
