41b389e574
Since the listener may take some time for records processing, there is a possibility that checkpoint will be stored too late after the process and thus we are able to get the same records in different channel adapter for the same shard, even if they are in the same consumer group and use shared `MetadataStore` This solution is some compromise for the current state of things and has to be reconsidered in the future in favor of proper rebalance and shard leader election solution As a workaround for the duplicate records an additional `@IdempotentReceiver` approach can be used * Upgrade to Gradle 4.2.1, Checkstyle 8.3, AssertJ 3.8.0 * Fix race condition in the `KinesisMessageDrivenChannelAdapterTests`
14 lines
103 B
Plaintext
14 lines
103 B
Plaintext
target
|
|
.settings
|
|
.springBeans
|
|
.classpath
|
|
.project
|
|
/.idea
|
|
/.gradle
|
|
/build
|
|
/*.iml
|
|
/*.ipr
|
|
/*.iws
|
|
bin/
|
|
out
|