zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "tison (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-102) Need to replace Jute with supported code
Date Fri, 20 Sep 2019 15:13:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934484#comment-16934484
] 

tison commented on ZOOKEEPER-102:
---------------------------------

Here is a important question: shall we want an immediate stage support both jute and the other
serialization framework?

I have visited jute abstraction and its {{readInt}}/{{writeInt}} etc. are hard to adopt in
other frameworks. kyro may have a near abstraction(for {{serialize}}/{{deserialize}}) but
neither protobuf nor thrift seems compatible with jute abstractly.

> Need to replace Jute with supported code
> ----------------------------------------
>
>                 Key: ZOOKEEPER-102
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-102
>             Project: ZooKeeper
>          Issue Type: Improvement
>            Reporter: Benjamin Reed
>            Priority: Major
>             Fix For: 4.0.0
>
>
> ZooKeeper currently uses Jute to serialize objects to put on the wire and on disk. We
pulled Jute out of Hadoop and added a C binding. Both versions of Jute have evolved (although
Hadoop still doesn't have a C binding). It would be nice to use a more standard serialization
library. Some options include Thrift or Google's protocol buffers.
> Our main requirements would be Java and C bindings and good performance. (For example,
serializing to XML would give us incredibly bad performance and would not be acceptible!)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message