anchor.diff:    "datacontenttype" : "application/avro",            <1>
     "dataschema" : "http://my-registry/schemas/ids/1", <2>
     "iodebeziumop" : "r",
  -  "iodebeziumversion" : "1.1.0-SNAPSHOT",
  +  "iodebeziumversion" : "{debezium-version}",
     "iodebeziumconnector" : "postgresql",
     "iodebeziumname" : "test_server",
     "iodebeziumtsms" : "1578924258597",
  
positive.code: 
  The following example also shows what a CloudEvents change event record emitted by a PostgreSQL connector looks like. In this example, the PostgreSQL connector is again configured to use JSON as the CloudEvents format envelope, but this time the connector is configured to use Avro for the `data` format. 
  
  [source,json,indent=0]
  ----
  {
    "id" : "name:test_server;lsn:33227720;txId:578",
  
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. 
  
  