[jira] [Resolved] (KAFKA-4390) Replace MessageSet usage with client-side equivalents

["Jason Gustafson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-4390.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.2.0

Issue resolved by pull request 2140
[https://github.com/apache/kafka/pull/2140]

> Replace MessageSet usage with client-side equivalents
> -----------------------------------------------------
>
>                 Key: KAFKA-4390
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4390
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.10.2.0
>
>
> Currently we have two separate implementations of Kafka's message format and log structure, one on the client side and one on the server side. Once KAFKA-2066 is merged, we will only be using the client side objects for direct serialization/deserialization in the request APIs, but we we still be using the server-side MessageSet objects everywhere else. Ideally, we can update this code to use the client objects everywhere so that future message format changes only need to be made in one place. This would eliminate the potential for implementation differences and gives us a uniform API for accessing the low-level log structure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)