[
https://issues.apache.org/jira/browse/CAMEL-19789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759622#comment-17759622
]
Karen Lease commented on CAMEL-19789:
-------------------------------------
{quote}Then multi-shard consumption is disregarded ?
{quote}
Not intentionally. But I am not at all an expert on Kinesis so if you have an
example or test case for this, that would be great.
I assume you mean that if there are several shards in a stream which are not
closed, we should read data from all of them? Based on the documentation, it
seems that a shard only gets to a CLOSED state if it is split or merged, which
sets the last sequence number. I didn't try to simulate that.
> Kinesis2Consumer repeatedly reads first record in stream
> --------------------------------------------------------
>
> Key: CAMEL-19789
> URL: https://issues.apache.org/jira/browse/CAMEL-19789
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
> Affects Versions: 4.0.0
> Reporter: Karen Lease
> Assignee: Karen Lease
> Priority: Major
> Fix For: 4.0.1, 4.1.0
>
>
> A route using from:aws2-kinesis produces Exchanges which have identical
> content which correspond to the first record in the Kinesis stream.
> This is due to a change in the way the shardIterator is managed in PR
> https://github.com/apache/camel/pull/10733.
> The issue is not found by KinesisConsumerIT because it doesn't check that it
> receives 20 different records.
> The issue is visible in camel-examples/debezium.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
