anchor.diff:  
   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. 
   
  +For information about using Avro, see: 
  +
  +* {link-prefix}:{link-avro-serialization}#avro-serialization[Avro serialization] 
  +
  +ifdef::community[]
  +* link:https://github.com/Apicurio/apicurio-registry[Apicurio Registry]
  +endif::community[]
  +ifdef::product[]
  +* link:{LinkServiceRegistryGetStart}[{NameServiceRegistryGetStart}]
  +endif::product[]
  +
   // Type: concept
   // ModuleID: example-change-event-records-in-cloudevents-format
   // Title: Example change event records in CloudEvents format
  
positive.code: 
  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.  
  
  [source,json,indent=0]
  ----
  {
    "id" : "name:test_server;lsn:29274832;txId:565",   <1>
  
negative.code: // Title: Example of configuring `CloudEventsConverter`
  == Example configuration
  
  Configure `io.debezium.converters.CloudEventsConverter` in your {prodname} connector configuration. Following is an example of configuring `CloudEventsConverter` to emit change event records that:
  
  * Use JSON as the envelope
  * Use the schema registry at \http://schema-registry:8081 to serialize the `data` attribute as binary Avro data
  
  In this example, you could omit the specification of `serializer.type` because `json` is the default. 
  
  