David Horn created CAMEL-20682:
----------------------------------
Summary: camel-kafka - KafkaIdempotentRepository misses continuous
updates from its topic after startup
Key: CAMEL-20682
URL: https://issues.apache.org/jira/browse/CAMEL-20682
Project: Camel
Issue Type: Bug
Components: camel-kafka
Affects Versions: 4.5.0, 4.4.1, 4.4.0
Reporter: David Horn
With CAMEL-20218 and CAMEL-20373 the initialization of the
KafkaIdempotentRepository has been changed and seems to work fine.
One purpose of a KafkaIdempotentRepository is to synchronize an idempotence
state over multiple processes (running in parallel on potentially different
machines). So a key feature of a KafkaIdempotentRepository is the continuous
update of the local in-memory cache with add/remove events from the idempotent
repository's topic *after* initialization. With Commit
a407fd82512e6680f4d6d6f97d836e63f76029e6
(https://github.com/apache/camel/commit/a407fd82512e6680f4d6d6f97d836e63f76029e6?diff=split&w=0#diff-8a2c6e5db1f384f93ecfc83f27b90f633d97c0a43775c0b44a75d88b1b74613f)
this capability got lost.
I absolutely hope this happened unintentionally and will be fixed soon.
Side Note: I was surprised to see, that consuming from the idempotent
repository's topic worked without providing a consumer group even though we
have Kafka's access control activated, restricting describe/read access of this
topic to dedicated consumer groups only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
