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

Hudson commented on BOOKKEEPER-582:
-----------------------------------

FAILURE: Integrated in bookkeeper-trunk #716 (See 
[https://builds.apache.org/job/bookkeeper-trunk/716/])
BOOKKEEPER-582: Make bookie and client use protobuf for requests (non-wire 
part) (missing files) (sijie) (sijie: rev 1613567)
* /zookeeper/bookkeeper/trunk/compat-deps/bookkeeper-server-compat-4.2.0
* /zookeeper/bookkeeper/trunk/compat-deps/bookkeeper-server-compat-4.2.0/pom.xml
* /zookeeper/bookkeeper/trunk/compat-deps/hedwig-server-compat-4.2.0
* /zookeeper/bookkeeper/trunk/compat-deps/hedwig-server-compat-4.2.0/pom.xml


> Make bookie and client use protobuf for requests (non-wire part)
> ----------------------------------------------------------------
>
>                 Key: BOOKKEEPER-582
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-582
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-client, bookkeeper-server
>            Reporter: Ivan Kelly
>            Assignee: Sijie Guo
>             Fix For: 4.3.0
>
>         Attachments: 
> 0002-BOOKKEEPER-582-Make-bookie-and-client-use-protobuf-f.patch, 
> 0002-BOOKKEEPER-582-Make-bookie-and-client-use-protobuf-f.patch, 
> 0002-BOOKKEEPER-582-Make-bookie-and-client-use-protobuf-f.patch, 
> 0003-BOOKKEEPER-582-Make-bookie-and-client-use-protobuf-f.patch, 
> BOOKKEEPER-582.diff, BOOKKEEPER-582.v2.diff, BOOKKEEPER-582.v3.diff, 
> BOOKKEEPER-582.v4.diff
>
>
> Make the client and the bookie use protobufs internally. This is the first 
> step to using protobufs on the wire, but for the moment, BookieRequestHandler 
> decodes the old wire protocol into the protobuf messages. Once this is in, 
> enabling on the wire will be very simple, and the old manual serialization 
> can be made "legacy" (still supported, but deprecated).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to