anchor.diff:  <3> The `data` attribute contains base64-encoded Avro binary data.
   
   It is also possible to use Avro for the envelope as well as the `data` attribute.
  +endif::community[]
   
   // Type: concept
   // ModuleID: example-of-configuring-cloudevents-converter
   // Title: Example of configuring `CloudEventsConverter`
   == Example configuration
   
  +ifdef::community[]
   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
  +* Use the schema registry at `\http://my-registry/schemas/ids/1` 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. 
   
  
positive.code: <3> The CloudEvents specification version. 
  <4> Connector type that generated the change event. The format of this field is `io.debezium._CONNECTOR_TYPE_.datachangeevent`. The value of `_CONNECTOR_TYPE_` is `mongodb`, `mysql`, `postgresql`, or `sqlserver`.
  <5> Time of the change in the source database.
  <6> Describes the content type of the `data` attribute, which is JSON in this example. The only alternative is Avro. 
  <7> An operation identifier. Possible values are `r` for read, `c` for create, `u` for update, or `d` for delete. 
  <8> All `source` attributes that are known from {prodname} change events are mapped to CloudEvents extension attributes by using the `iodebezium` prefix for the attribute name.
  <9> When enabled in the connector, each `transaction` attribute that is known from {prodname} change events is mapped to a CloudEvents extension attribute by using the `iodebeziumtx` prefix for the attribute name.
  <10> The actual data change itself. Depending on the operation and the connector, the data might contain `before`, `after` and/or `patch` fields.
  
  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,subs="attributes"]
  
negative.code: 
  * A set of standardized event attributes
  * Rules for defining custom attributes
  ifdef::community[]
  * Encoding rules for mapping event formats to serialized representations such as JSON or Avro
  endif::community[]
  ifdef::product[]
  * Encoding rules for mapping event formats to serialized representations such as JSON
  endif::product[]
  * Protocol bindings for transport layers such as Apache Kafka, HTTP or AMQP
  
  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. 
  
  ifdef::community[]
  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. 
  endif::community[]
  ifdef::product[]
  Currently, only structured mapping mode is supported. The CloudEvents change event envelope must be JSON and  the `data` format must be JSON. It is expected that a future {prodname} release will support binary mapping mode. 
  endif::product[]
  
  ifdef::community[]
  For information about using Avro, see: 
  
  * {link-prefix}:{link-avro-serialization}#avro-serialization[Avro serialization] 
  
  * 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
  