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

Merge pull request #3096 from wwalters12/patch-1

Browse Source 
Fix typo in record-serialization-and-deserialization doc
This commit is contained in:
Oleg Zhurakousky
2025-03-13 16:59:24 +01:00
committed by GitHub
parent d6cc07df97 8990e7e4b9
commit 8ff2757941
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/modules/ROOT/pages/kafka/kafka-streams-binder/record-serialization-and-deserialization.adoc
View File

@@ -118,7 +118,7 @@ If your application uses the branching feature and has multiple output bindings,
Once again, if the binder is capable of inferring the `Serde` types, you don't need to do this configuration.
If you don't want the native encoding provided by Kafka, but want to use the framework provided message conversion, then you need to explicitly disable native encoding since since native encoding is the default.
For e.g. if you have the same BiFunction processor as above, then `spring.cloud.stream.bindings.process-out-0.producer.nativeEncoding: false`
For e.g. if you have the same BiFunction processor as above, then `spring.cloud.stream.bindings.process-out-0.producer.useNativeEncoding: false`
You need to disable native encoding for all the output individually in the case of branching. Otherwise, native encoding will still be applied for those you don't disable.
When conversion is done by Spring Cloud Stream, by default, it will use `application/json` as the content type and use an appropriate json message converter.