Skip to content

Commit 51ed57d

Browse files
Emrehzl94ali-ince
andauthored
Update modules/ROOT/pages/source/payload-mode.adoc
Co-authored-by: Ali Ince <ali-ince@users.noreply.github.com>
1 parent e3d9361 commit 51ed57d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/ROOT/pages/source/payload-mode.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ For example, a string field will be represented as:
178178

179179
== Configuration Recommendations
180180

181-
For production environments where performance and payload simplicity are important, `COMPACT` mode is recommended. If your environment involves schema evolution, temporal data types, or other complex data requirements, `EXTENDED` mode provides the necessary structure for schema compatibility.
181+
`COMPACT` mode is useful and easier to work with when generated messages are consumed with other connectors or applications, and you can relax your schema compatibility mode on target topics. If your environment requires schema compatibility, temporal data types, or you have strong type safety requirements with different converters (`AVRO`, `JSON Schema`, `PROTOBUF` or `JSON Embedded`), `EXTENDED` mode should be preferred.
182182

183183
== Compatibility with Sink Connectors
184184

0 commit comments

Comments
 (0)