spring-cloud / spring-cloud/spring-cloud-stream
Add Transactional Support for Reactive Binder
Open
Nobody has claimed this yet.
feature
REACTIVE-KAFKA-BINDER
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
This is a feature request for reactive binder.
We could provide transactional support for the following type.
@Bean
Function<Flux<Flux<T>>, Flux<Flux<R>>> transform(){
return outerFlux -> outerFlux
.map(innerFlux -> innerFlux.map(...));
}
then the innerFlux can be sent transactionally.
kafkaSender.sendTransactionally(..)
`
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 by tracing the reactive binder entry point for Function<Flux<Flux>, Flux<Flux>> and the kafkaSender.sendTransactionally(..) call. Done means this function shape supports sending each innerFlux transactionally, with the resulting behavior validated in the relevant reactive binder tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, spring
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100