Federico Mariani created CAMEL-27075:
----------------------------------------
Summary: camel-kafka - a group.id set in additionalProperties is
replaced by a generated group id
Key: CAMEL-27075
URL: https://issues.apache.org/jira/browse/CAMEL-27075
Project: Camel
Issue Type: Bug
Components: camel-kafka
Reporter: Federico Mariani
A Kafka consumer without the {{groupId}} option ignores a {{group.id}} set in
{{additionalProperties}}. The consumer puts its generated group id (a new UUID
at each start) into the Kafka properties after the additional properties, so
the generated id wins, and nothing says so. Other consumer properties set this
way, such as {{group.instance.id}}, are kept.
{code:java}
from("kafka:orders?brokers=localhost:9092&additionalProperties.group.id=billing")
.to("log:orders"); // the consumer joins a group named after a random UUID,
not billing
{code}
The same happens with
{{camel.component.kafka.additional-properties[group.id]=billing}}. The consumer
does not resume from the offsets committed by the group after a restart (with
the default {{autoOffsetReset=latest}}, the records sent during the restart are
not consumed), and each instance of the application receives every record. The
WARN of CAMEL-27059 for a consumer without {{groupId}} would also fire for it.
Expected: without {{groupId}}, the consumer uses the {{group.id}} of
{{additionalProperties}}, and generates a group id only when neither sets one.
When both are set, {{groupId}} is used, as today.
_Claude Code on behalf of Federico Mariani_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)