anchor.diff:  ...
   ----
   endif::product[]
  -
  -// Type: concept
  -// Title: About Avro name requirements
  -// ModuleID: about-avro-name-requirements
  -[[avro-naming]]
  -== Naming
  -
  -As stated in the Avro link:https://avro.apache.org/docs/current/spec.html#names[documentation], names must adhere to the following rules:
  -
  -* Start with `[A-Za-z_]`
  -* Subsequently contains only `[A-Za-z0-9_]` characters
  -
  -{prodname} uses the column's name as the basis for the corresponding Avro field.
  -This can lead to problems during serialization if the column name does not also adhere to the Avro naming rules.
  -Each {prodname} connector provides a configuration property, `sanitize.field.names` that you can set to `true` if you have columns that do not adhere to Avro rules for names. Setting `sanitize.field.names` to `true` allows serialization of non-conformant fields without having to actually modify your schema.
   
   ifdef::community[]
   [id="confluent-schema-registry"]
  
positive.code:     -e VALUE_CONVERTER=io.apicurio.registry.utils.converter.AvroConverter \
      -e CONNECT_KEY_CONVERTER=io.apicurio.registry.utils.converter.AvroConverter \
      -e CONNECT_KEY_CONVERTER_APICURIO.REGISTRY_URL=http://apicurio:8080 \
      -e CONNECT_KEY_CONVERTER_APICURIO.REGISTRY_GLOBAL-ID=io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy \
      -e CONNECT_VALUE_CONVERTER=io.apicurio.registry.utils.converter.AvroConverter \
      -e CONNECT_VALUE_CONVERTER_APICURIO_REGISTRY_URL=http://apicurio:8080 \
      -e CONNECT_VALUE_CONVERTER_APICURIO_REGISTRY_GLOBAL-ID=io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy \
      -p 8083:8083 debezium/connect-apicurio:{debezium-docker-label}
  ----
  endif::community[]
  
  
negative.code: USER 1001
  ----
  +
  Before Kafka Connect starts running the connector, Kafka Connect loads any third-party plug-ins that are in the `/opt/kafka/plugins` directory.
  
  .. Build the docker container image. For example, if you saved the docker file that you created in the previous step as `debezium-container-with-avro`, then you would run the following command:
  +
  `docker build -t debezium-container-with-avro:latest`
  
  .. Push your custom image to your container registry, for example:
  +
  `docker push 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+]
  ----
  