spring-cloud / spring-cloud/spring-cloud-stream
Add support to StreamBridge to send to a binding rather then destination
Open
Nobody has claimed this yet.
Backport 4.3.x
enhancement
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
In the following configuration the message will go straight to consume-in-0 because input is bound to testQueue and hence to consume-in-0. which is confusing. . .
StreamBridge bridge = context.getBean(StreamBridge.class);
bridge.send("input", "foo");
spring.cloud.stream.bindings.consume-in-0.destination=testQueue
spring.cloud.stream.bindings.consume-in-0.group=myGroup
spring.cloud.stream.function.bindings.uppercase|concat-out-0=input
spring.cloud.stream.bindings.input.destination=testQueue
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the StreamBridge.send("input", "foo") entry point and trace how the shown binding and destination configuration are resolved. The change is complete when StreamBridge can target a binding separately from its destination, while preserving the existing configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100