[CAMEL-20682] camel-kafka - KafkaIdempotentRepository misses continuous updates from its topic after startup

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.4.0, 4.4.1, 4.5.0, 4.6.0
• Fix Version/s: 4.8.0
• Component/s: camel-kafka
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: David Horn
• Created: 16/Apr/24 12:18
• Updated: 4 days ago 08:22
• Resolved: 07/Jul/24 10:24

Description

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 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.

Issue Links

• links to: GitHub Pull Request #14750
• links to: GitHub Pull Request #16581