SpringCloud/spring-cloud-stream
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix documentation typos

Browse Source 
Signed-off-by: Nayan Hajratwala <nayan@chikli.com>

Resolves #3110
This commit is contained in:
Nayan Hajratwala
2025-04-25 14:23:33 -04:00
committed by Oleg Zhurakousky
parent 96eb4eed3f
commit 3c5113f3da
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/modules/ROOT/pages/kafka/kafka-reactive-binder/examples.adoc
View File

@@ -11,7 +11,7 @@ public Function<Flux<String>, Flux<String>> uppercase() {
}
----
You can use the above `upppercase` function with both message channel based Kafka binder (`spring-cloud-stream-binder-kafka`) as well as the reactive Kafka binder (`spring-cloud-stream-binder-kafka-reactive`), the topic of discussion in this section.
You can use the above `uppercase` function with both message channel based Kafka binder (`spring-cloud-stream-binder-kafka`) as well as the reactive Kafka binder (`spring-cloud-stream-binder-kafka-reactive`), the topic of discussion in this section.
When using this function with the regular Kafka binder, although you are using reactive types in the application (i.e., in the `uppercase` function), you only get the reactive streams within the execution of your function.
Outside the function's execution context, there is no reactive benefits since the underlying binder is not based on the reactive stack.
Therefore, although this might look like it is bringing a full end-to-end reactive stack, this application is only partially reactive.
@@ -34,7 +34,7 @@ Starting with version 4.0.2, the `KafkaHeaders.ACKNOWLEDGMENT` header contains a
[source, java]
----
@Bean
public Consumer<Flux<Message<String>> consume() {
public Consumer<Flux<Message<String>>> consume() {
return msg -> {
process(msg.getPayload());
msg.getHeaders().get(KafkaHeaders.ACKNOWLEDGMENT, ReceiverOffset.class).acknowledge();