anchor.diff:  [id="confluent-schema-registry"]
   == Confluent Schema Registry
   
  -There is an alternative https://github.com/confluentinc/schema-registry[schema registry] implementation provided by Confluent. The configuration is slightly different.
  +There is an alternative https://github.com/confluentinc/schema-registry[schema registry] implementation provided by Confluent. 
  +The configuration is slightly different.
   
   . In your {prodname} connector configuration, specify the following properties:
   +
  
positive.code: endif::community[]
  
  ifdef::product[]
  {LinkServiceRegistryGetStart}[{registry-name-full}] provides several components that work with Avro:
  endif::product[]
  
  * An Avro converter that you can specify in {prodname} connector configurations. This converter maps Kafka Connect schemas to Avro schemas. The converter then uses the Avro schemas to serialize the record keys and values into Avro's compact binary form.
  
  * An API and schema registry that tracks:
  +
  ** Avro schemas that are used in Kafka topics
  ** Where the Avro converter sends the generated Avro schemas
  
  +
  Since the Avro schemas are stored in this registry, each record needs to contain only a tiny _schema identifier_.
  This makes each record even smaller. For an I/O bound system like Kafka, this means more total throughput for producers and consumers.
  
  * Avro _Serdes_ (serializers and deserializers) for Kafka producers and consumers. Kafka consumer applications that you write to consume change event records can use Avro Serdes to deserialize the change event records.
  
  To use the {registry} with {prodname}, add {registry} converters and their dependencies to the Kafka Connect container image that you are using for running a {prodname} connector.
  
  [NOTE]
  ====
  The {registry} project also provides a JSON converter. This converter combines the advantage of less verbose messages with human-readable JSON. Messages do not contain the schema information themselves, but only a schema ID.
  ====
  
  // Type: concept
  
negative.code: 
  .. Push your custom image to your container registry, for example:
  +
  `docker push _<myregistry.io>_/debezium-container-with-avro:latest`
  
  .. Point to the new container image. Do one of the following:
  +
  * Edit the `KafkaConnect.spec.image` property of the `KafkaConnect` custom resource. 
  If set, this property overrides the `STRIMZI_DEFAULT_KAFKA_CONNECT_IMAGE` variable in the Cluster Operator. 
  For example:
  +
  [source,yaml,subs=attributes+]
  ----
  