[
https://issues.apache.org/jira/browse/CAMEL-11473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066997#comment-16066997
]
Jyrki Ruuskanen commented on CAMEL-11473:
-----------------------------------------
With the current camel-kafka behavior, if a user wants multiple consumers to
receive messages from a (single partition) topic, i.e. a publish-subcribe
pattern, they have to create a unique id for each consumer and set that value
as the value of the groupId parameter.
Instead, this unique id could be created by the component when groupId is not
given. This behavior is also logical: when user creates a consumer with only
the topic parameter, the expected outcome is to get all messages from that
topic. Right now, that is an error (=groupId is required).
> camel-kafka - Use unique groupId by default
> -------------------------------------------
>
> Key: CAMEL-11473
> URL: https://issues.apache.org/jira/browse/CAMEL-11473
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Reporter: Jyrki Ruuskanen
> Priority: Minor
>
> In the spirit of providing useful defaults instead of error messages
> camel-kafka consumer should generate a unique groupId if one is not given.
> This way {{from("kafka:host:9092?topic=test")}} consumers would behave in a
> pub-sub manner, and {{from("kafka:host:9092?topic=test&groupId=something}}
> consumers would behave like, well, like consumer groups on kafka do.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
