[
https://issues.apache.org/jira/browse/FLINK-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692971#comment-15692971
]
Tzu-Li (Gordon) Tai commented on FLINK-5075:
--------------------------------------------
Resolved for {{master}} via
http://git-wip-us.apache.org/repos/asf/flink/commit/f5f4f7a
Resolved for {{release-1.1}} via
http://git-wip-us.apache.org/repos/asf/flink/commit/b9e6dcc
> Kinesis consumer incorrectly determines shards as newly discovered when
> tested against Kinesalite
> -------------------------------------------------------------------------------------------------
>
> Key: FLINK-5075
> URL: https://issues.apache.org/jira/browse/FLINK-5075
> Project: Flink
> Issue Type: Bug
> Components: Kinesis Connector
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Fix For: 1.2.0, 1.1.4
>
>
> A user reported that when our Kinesis connector is used against Kinesalite
> (https://github.com/mhart/kinesalite), we're incorrectly determining already
> found shards as newly discovered:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Subtask-keeps-on-discovering-new-Kinesis-shard-when-using-Kinesalite-td10133.html
> I suspect the problem to be the mock Kinesis API implementations of
> Kinesalite doesn't completely match with the official AWS Kinesis behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
