[
https://issues.apache.org/jira/browse/KAFKA-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008262#comment-17008262
]
Omer van Kloeten commented on KAFKA-8553:
-----------------------------------------
Thanks for checking in on this issue, [~dongjin].
I fully agree with your points. However, in the issue I wrote (emphasis mine):
{quote}This is either the expected behavior and *is not documented* or
unexpected behavior and is an issue with the implementation.
{quote}
Therefore I believe this issue should address the lack of documentation, rather
than simply be closed as _Not A Problem_ :)
> 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
> Attachments: foo1.png, image-2019-06-18-14-59-54-643.png
>
>
> {{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:
> !foo1.png!!image-2019-06-18-14-59-54-643.png!
> This is either the expected behavior and is not documented or unexpected
> behavior and is an issue with the implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
