kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omer van Kloeten (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-8553) Kafka Connect Schema Compatibility Checks for Name Changes
Date Tue, 18 Jun 2019 11:55:00 GMT
Omer van Kloeten created KAFKA-8553:
---------------------------------------

             Summary: 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


{{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)

Mime
View raw message