You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/02/19 19:50:18 UTC
[jira] [Resolved] (FLINK-3386) Kafka consumers are not properly
respecting the "auto.offset.reset" behavior
[ https://issues.apache.org/jira/browse/FLINK-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger resolved FLINK-3386.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Closed in http://git-wip-us.apache.org/repos/asf/flink/commit/3a8717fd
> Kafka consumers are not properly respecting the "auto.offset.reset" behavior
> ----------------------------------------------------------------------------
>
> Key: FLINK-3386
> URL: https://issues.apache.org/jira/browse/FLINK-3386
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector, Streaming Connectors
> Affects Versions: 1.0.0
> Reporter: Gyula Fora
> Assignee: Robert Metzger
> Fix For: 1.0.0
>
>
> Currently if the data in a kafka topic expires while reading from it, it causes an unrecoverable failure as subsequent retries will also fail on invalid offsets.
> While this might be the desired behaviour under some circumstances, it would probably be better in most cases to automatically jump to the earliest valid offset in these cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)