Thrift 版本之间的数据格式兼容性
我正在尝试升级使用 Thrift 0.2 库进行通信的系统。由于这是相当旧的版本(最新稳定版是 0.5),并且据称性能有显着改进(0.4),我希望升级。但是,我找不到有关基础数据格式是否存在不兼容更改的信息。根据版本控制方案,人们希望没有;但由于这些仍然是 1.0 之前的版本,可能对稳定性的期望较低。
我希望了解数据格式本身向后兼容的原因是它允许对组件进行一一升级。
无论如何:我希望有更多信息的人可以指出我正确的文档。
I am trying to upgrade a system that uses Thrift 0.2 libraries for communication. Since this is rather old version (latest stable is 0.5), and there have been alleged significant improvements to performance (in 0.4) I was hoping to upgrade. However, I could not find information regarding whether there have been incompatible changes to underlying data format. Based on versioning scheme, one would hope there was not; but since these are still pre-1.0 versions, maybe there is less expectation for stability.
The reason I am hoping to learn that data format itself was backwards compatible is that it would allow upgrades to components to occur one by one.
Anyway: I was hoping that someone with more information could point me to right documentation.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
摘自“Thrift 0.4.0 已发布” 文档。源代码中的相关更改:“将二进制字段实现从 byte[] 切换到 ByteBuffer”。
Taken from "Thrift 0.4.0 Released" document. Related changes in the source code: "Switch binary field implementation from byte[] to ByteBuffer".