apache / apache/pulsar-client-node
Add method to get the schema (version) used for serialization of a message
- 主要语言
- C++
- 星标
- 164
- 派生
- 98
- PR 合并指标
- 30 天内没有已合并 PR
描述
There are client libraries for other languages (e.g. java) that support automatic (de)serialization of message data based on a schema (https://pulsar.apache.org/docs/3.1.x/schema-overview/).
The node client does not have this feature yet (https://github.com/apache/pulsar-client-node/issues/242).
In theory it should be possible to deserialize the message data manually, BUT...
Some serialization formats like Avro require to know the exact schema that was used for serialization (https://github.com/mtth/avsc/issues/447). In order to deal with schema evolution the client needs to know it's own compatible schema AND the schema used for serialization.
As far I understand, the automatic (de)serialization feature of Pulsar solves this problem by keeping a schema registry and tagging the messages with the used schema version.
If I understand right, the node client does not provide a method to get the schema used for serialization and not even a method to get the schema version of a message.
Assuming the need for schema evolution, this makes it impossible to deserialize reliably messages written by a java client library using an Avro schema,
I'm new to Pulsar and Avro, so please forgive (and correct) me if my understanding is wrong.
If my understanding is right, I wonder how difficult it would be to add a method to lookup the serialization schema on an message.
贡献指南
这个仓库没有索引到贡献指南
调研方向
从 Pulsar schema 概览和关联的 node-client issue 开始,确认 schema 版本是如何附加到消息上的,以及 Node 客户端是否公开这些版本。定义获取序列化 schema 或版本所需的 API,然后确认它支持在 schema 演进过程中可靠地进行 Avro 反序列化。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, nodejs
- 领域
- distributed-systems
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100