融合架构注册表持久性 [英] Confluent Schema Registry Persistence

查看:63
本文介绍了融合架构注册表持久性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

即使服务器重新启动,我也希望能够保留具有固定ID的架构.

I would like to be able to keep a schema with a fixed id even if the server is restarted.

是否可以将模式持久保存在模式注册表中,以便在服务器崩溃后使它们具有相同的ID?

Is it possible to persist the schemas in the Schema Registry in order to have them with the same id after the server crashes?

否则,当模式注册服务器启动时,是否可以对具有固定ID的模式进行硬编码?

Otherwise, is it possible to hardcode a schema with a fixed id when the schema registry server starts?

推荐答案

这是架构注册表的目的:架构具有固定的ID.SchemaRegistry实际上不会在磁盘上存储任何内容.它利用kafka将所有信息存储在一个压缩的主题中(默认情况下在代理上为 _schemas ).

This is the purpose of schema registry: a schema has a fixed id. SchemaRegistry doesn't store anything on disk actually. It leverages on kafka to store all information in a compacted topic (on broker, _schemas by default).

只要您注册了一个架构,每当您请求相同的架构时,即使崩溃/重新启动后,您也将获得相同的ID

So as long as you have register a schema, whenever you asked for this same schema, you will get the same id, even after crash / restart

这篇关于融合架构注册表持久性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆