[
https://issues.apache.org/jira/browse/FLINK-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336767#comment-17336767
]
Flink Jira Bot commented on FLINK-6316:
---------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Kinesis connector docs should mention that FlinkKinesisConsumer does not
> provide strong ordering guarantees on resharding
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-6316
> URL: https://issues.apache.org/jira/browse/FLINK-6316
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis, Documentation
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Major
> Labels: stale-major
>
> Since the {{FlinkKinesisConsumer}} depends only on local information to
> determine whether or not a new shard due to resharding should be subscribed
> by a subtask, there is no coordination wrt parent-child shard relationship
> across subtasks.
> Therefore, {{FlinkKinesisConsumer}} does not provide any strong processing
> ordering guarantees.
> Take for example, if initially the assignment is:
> Subtask #1 --> Shard A
> Subtask #2 --> Shard B
> Assume A & B is merged to create shard C, and subtask #1 locally determines
> that it should be assigned shard C.
> Since Flink generally does not provide coordinating facilities between
> subtask instances, there is no means of coordinating that shard C is consumed
> only after shard B is also fully consumed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
