[
https://issues.apache.org/jira/browse/CAMEL-19789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760494#comment-17760494
]
Karen Lease commented on CAMEL-19789:
-------------------------------------
bq. CLOSED state happens when the connection is broken or discontinued right ?
No, I don't think it is related to the connection, at least according to this
explanation:
[Resharding|docs.aws.amazon.com/streams/latest/dev/kinesis-using-sdk-java-after-resharding.html#kinesis-using-sdk-java-resharding-data-routing]
But I agree that my correction for reading multiple records from one shard
broke the multi-shard handling. So I will fix it in CAMEL-19811.
> 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)
