[
https://issues.apache.org/jira/browse/KAFKA-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Omer van Kloeten updated KAFKA-8553:
------------------------------------
Attachment:
data-pipelines________code_data-pipelines__idea_pants-projects_a44ff4d5a7b47b280b58163799be5d1547316f03__-___Library_Preferences_IntelliJIdea2019_1_scratches_scratch_30_json.png
> Kafka Connect Schema Compatibility Checks for Name Changes
> ----------------------------------------------------------
>
> Key: KAFKA-8553
> URL: https://issues.apache.org/jira/browse/KAFKA-8553
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Omer van Kloeten
> Priority: Major
>
> {{SchemaProjector.checkMaybeCompatible}} checks whether the Connect schema is
> compatible with another one. This is used for projection when using
> {{schema.compatibility}}.
> Unfortunately, nowhere is it documented that if you change the name of the
> schema, this would break compatibility entirely.
> For instance, the following two Avro schemas are fully compatible, but
> Connect says they're not:
> {
> {{ "type": "record",}}
> {{ "name": "Foo1",}}
> {{ "namespace":"example",}}
> {{ "fields": [}}
> {{ ]}}
> {{}}}
> {{{}}
> {{ "type": "record",}}
> {{ "name": "Foo2",}}
> {{ "namespace":"example",}}
> {{ "fields": [}}
> {{ { "name": "bar", "type": ["null", "string"]}}}
> {{ ]}}
> {{}}}
> This is either the expected behavior and is not documented or unexpected
> behavior and is a bug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
