Spring Cloud Stream Binder EH - change the way to supply extended properties for binding #25330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… user to specify event hub name or consumer group
saragluna
requested review from
backwind1233,
chenrujun,
moarychan,
stliu,
yiliuTo and
zhichengliu12581
as code owners
ghost
added
the
|
/azp run java - spring - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
saragluna
deleted the
xiada/fix/spring-cloud-azure-binder-eh-extended-properties
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current implementation of eh binder needs users to specify the destination/group in the properties of namespace
spring.cloud.stream.eventhub.binding.xxx, however these could already be read from thespring.cloud.stream.binding.xxx. This PR is to fix this issue and refactor the producer/consumer properties defined in eh binder.