alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-7418 Remove references that imply downstream support for CloudEvents

Browse Source
This commit is contained in:
roldanbob 2024-02-05 22:54:58 -05:00
parent 093bb3f999
commit 77fba3068f
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
documentation/modules/ROOT/pages/integrations/cloudevents.adoc
View File

@ -45,8 +45,11 @@ The CloudEvents specification defines:
To configure a {prodname} connector to emit change event records that conform to the CloudEvents specification, {prodname} provides the `io.debezium.converters.CloudEventsConverter`, which is a Kafka Connect message converter. To configure a {prodname} connector to emit change event records that conform to the CloudEvents specification, {prodname} provides the `io.debezium.converters.CloudEventsConverter`, which is a Kafka Connect message converter.
Currently, only structured mapping mode is supported. The CloudEvents change event envelope can be JSON or Avro and each envelope type supports JSON or Avro as the `data` format. It is expected that a future {prodname} release will support binary mapping mode. Currently, only structured mapping mode can be used.
The CloudEvents change event envelope can be JSON or Avro, and you can use JSON or Avro as the `data` format for each envelope type.
ifdef::community[]
It is expected that a future {prodname} release will support binary mapping mode.
endif::community[]
ifdef::product[] ifdef::product[]
Information about emitting change events in CloudEvents format is organized as follows: Information about emitting change events in CloudEvents format is organized as follows: