[BUG] The base level event-hub-name
property should be overridden when sub-level event-hub-name
property configured
#43593
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Event Hubs
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Describe the bug
When using the
spring-cloud-azure-starter-eventhubs
dependency, if I specify the properties in the application.yaml as follows, I think the expected result is that theevent-hub-name
in theproducer
andconsumer
section will override the baseevent-hub-name
, that is, the application will eventually use theaaaa
event hub, notbbbb
.But for the following code,
The application logs show that it still use
bbbb
, not theaaaa
, which is inconsistent as above expectation.Exception or Stack Trace
No exception, just inconsistent behavior.
To Reproduce
Steps to reproduce the behavior:
Run this repo code: https://github.com/haoozhang/spring-cloud-azure-starter-eventhubs-sample
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
spring-cloud-azure-starter-eventhubs
5.18.0If you suspect a dependency version mismatch (e.g. you see
NoClassDefFoundError
,NoSuchMethodError
or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:mvn dependency:tree -Dverbose
)Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: