Hi Yuva, This is a cool feature. We can create a new PIP to discuss and support it.
Thanks. Penghui Yuva raj <uvar...@gmail.com> 于2019年9月9日周一 下午2:22写道： > Hi PengHui , > Can we add support for this also > https://github.com/confluentinc/schema-registry/pull/680 . > Compatibility resolution strategy is right now at per topic level. For > Event sourcing, we would like to have different types of event in the same > topic with an AVRO name to each of the record. So compatibility can be > enforced between identically named events in the same topic, not between > differently named events. For more details > https://martin.kleppmann.com/2018/01/18/event-types-in-kafka-topic.html > `Schema > Management Section`. > > On Sat, 7 Sep 2019 at 03:17, Sijie Guo <guosi...@gmail.com> wrote: > > > Penghui, > > > > Thank you for sharing this proposal. I agreed that the compatibility > check > > strategy is different between producers and consumers. > > We should separate them and make it more clearly. The proposal overall > > looks good. +1 > > > > Thank you and your team for driving this! > > > > -Sijie > > > > On Fri, Sep 6, 2019 at 2:19 AM PengHui Li <peng...@apache.org> wrote: > > > > > Hi all; > > > > > > Bo Cong and i are drafting a proposal to separate schema compatibility > > > checker for producer and consumer > > > > > > Here is the link of PIP-44 > > > < > > > > > > https://github.com/apache/pulsar/wiki/PIP-44%3A-Separate-schema-compatibility-checker-for-producer-and-consumer > > > > > > > > > > Looking forward feedbacks. > > > > > > Thanks, > > > Penghui > > > > > > > > -- > *Thanks* > > *Yuvaraj L* >
