Specifying the behaviour of the ConsumerID field when configuring Kafka Pub/Sub #3935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
This PR details the behaviour of configuration the
ConsumerID
field in the Apache Kafka Pub/Sub component. It all revolves around this code which basically ignores theConsumerID
field of theConsumerGroup
field is defined. This PR simply updates the field description table to show that a combination of the consumer group and a random unique identifier is used when defining theconsumerId
if the consumer group field is set.Issue reference
Closes #3697