[
https://issues.apache.org/jira/browse/BEAM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077614#comment-16077614
]
ASF GitHub Bot commented on BEAM-2534:
--------------------------------------
GitHub user rangadi opened a pull request:
https://github.com/apache/beam/pull/3514
[BEAM-2534] Cherry-pick #3461 into 2.1.0.
Cherry-pick #3461 : Handle offset gaps in Kafka messages.
R: @jbonofre CC: @kennknowles.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rangadi/beam cherrypick-pr-3461
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3514.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3514
----
commit 9ffaf185ceefaf7de51b1197e00d2d54bdbb6760
Author: Raghu Angadi <[email protected]>
Date: 2017-06-28T19:07:06Z
[BEAM-2534] Handle offset gaps in Kafka messages.
KafkaIO logged a warning when there is a gap in offstes for messages.
Kafka also support 'KV' store style topics where some of the messages
are deleted leading gaps in offsets. This PR removes the log and
accounts for offset gaps in backlog estimate.
----
> KafkaIO should allow gaps in message offsets
> --------------------------------------------
>
> Key: BEAM-2534
> URL: https://issues.apache.org/jira/browse/BEAM-2534
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-extensions
> Affects Versions: 2.0.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Priority: Minor
> Fix For: 2.1.0
>
>
> KafkaIO reader logs a warning when it notices gaps in offsets for messages.
> While such gaps are not expected for normal Kafka topics, there could be gaps
> when log compaction is enabled (which deletes older messages for a key).
> This warning log is not very useful. Also we should take such gaps while
> estimating backlog.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
