--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/651eed83-6659-4f0f-9a27-5f8d5220e320%40googlegroups.com.
I believe that is an incompatible change based on the Schema Resolution and Canonical Form rules in the spec: https://avro.apache.org/docs/1.8.1/spec.html#Schema+Resolution (note rules saying records, enums, etc have to have matching names).That said, the best way to find out is to just test it!-Ewen
On Mon, Dec 12, 2016 at 6:07 PM, Andrew Xue <and...@lumoslabs.com> wrote:
no, it will be the same topic.
On Monday, December 12, 2016 at 4:23:56 PM UTC-8, Craig Hooper wrote:Are you talking about the topic name i.e. the subject it will be registered under? If so then the registry will consider them to be unrelated i.e. they are registered as two completely different schemas.
On Tuesday, 13 December 2016 07:11:16 UTC+11, Andrew Xue wrote:we have a k-stream that produced a message of something likex.y.z.MyNameAnow we want to change to likea.b.SomeOtherNameotherwise, the schema remains exactly the same.how will schema-registry react to that?
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.