anchor.diff:  * link:https://github.com/Apicurio/apicurio-registry[Apicurio Registry]
   
   // Type: concept
  -// ModuleID: example-change-event-records-in-cloudevents-format
  -// Title: Example change event records in CloudEvents format
  +// ModuleID: example-debezium-change-event-records-in-cloudevents-format
  +// Title: Example {prodname} change event records in CloudEvents format
   == Example event format
   
   The following example shows what a CloudEvents change event record emitted by a PostgreSQL connector looks like. In this example, the PostgreSQL connector is configured to use JSON as the CloudEvents format envelope and also as the `data` format.  
  
positive.code: The value can be `json` or `avro`.
  
  [id="cloud-events-converter-data-serializer-type"]
  |{link-prefix}:{link-cloud-events}#cloud-events-converter-data-serializer-type[`data.serializer.type`]
  |`json`
  |The encoding type to use for the `data` attribute. 
  The value can be `json` or `avro`.
  
negative.code: 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. 
  
  ifdef::product[]
  Information about emmitting change events in CloudEvents format is organized as follows:  
  
  * xref:example-debezium-change-event-records-in-cloudevents-format[]
  * xref:example-of-configuring-debezium-cloudevents-converter[]
  * xref:debezium-cloudevents-converter-configuration-options[]
  endif::product[]
  
  For information about using Avro, see: 
  
  * {link-prefix}:{link-avro-serialization}#avro-serialization[Avro serialization] 
  