英文:
Is there a schema registry specification?
问题
关于模式注册表的一般问题，是否有通用的规范？我的意思是，如果我从Confluent切换到Cloudera，会有问题吗？它们是否遵循相同的REST API？如果是这样，谁负责定义这个规范，我如何查看特定实现是否兼容？
英文:
I have a simple question about schema registry in general. Is there a common specification for a schema registry? I mean if I switch from confluent to cloudera can I have a problem? Do they follow the same REST API? If so, who is responsible for define this specification and how can I see if a specific implementation is compatible?
答案1
得分: 0
尽管关于超新版本或其他方面可能会有一些注意事项，但总的来说，Cloudera Schema Registry的设计是这样的，使用它而不是Confluent Schema Registry应该不会有任何问题。
明确声明：我是Cloudera的员工。
英文:
Though there may always be caveats regarding super new versions or so, in general the Cloudera Schema Registry is designed so there should not be any problem to use this instead of the Confluent Schema Registry.
Explicit disclosure: I am an employee of Cloudera.
答案2
得分: 0
回答我的问题，我没有找到一个通用的模式注册规范，但我发现Cloudera模式注册表（hortonworks模式注册表）与confluent兼容。我的意思是，有一个特定的端点提供了某种兼容性。我使用confluent客户端进行了一堆测试，效果非常好。事实上，甚至KafkaAvroSerdes也可以正常工作。
英文:
Answering my own question, I didn't find a common specification for schema registries but I found out the Cloudera Schema Registry (hortonworks schema registry) is compatible with confluent. I mean, there is a specific endpoint that provides some sort of compatibility. I performed a bunch of tests with a confluent client and it worked pretty well. In fact, even KafkaAvroSerdes worked without problems.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论