[
https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609393#comment-15609393
]
ASF GitHub Bot commented on KAFKA-2066:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/2069
KAFKA-2066: Use client-side FetchRequest/FetchResponse on server
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-2066
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2069.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2069
----
commit 3a8a99d6b1177dc703a07c358a628091a0bb7654
Author: Jason Gustafson <ja...@confluent.io>
Date: 2016-10-24T23:17:43Z
KAFKA-2066: Use client-side FetchRequest/FetchResponse on server
----
> Replace FetchRequest / FetchResponse with their
> org.apache.kafka.common.requests equivalents
> --------------------------------------------------------------------------------------------
>
> Key: KAFKA-2066
> URL: https://issues.apache.org/jira/browse/KAFKA-2066
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Gwen Shapira
> Assignee: Jason Gustafson
>
> Replace FetchRequest / FetchResponse with their
> org.apache.kafka.common.requests equivalents.
> Note that they can't be completely removed until we deprecate the
> SimpleConsumer API (and it will require very careful patchwork for the places
> where core modules actually use the SimpleConsumer API).
> This also requires a solution on how to stream from memory-mapped files
> (similar to what existing code does with FileMessageSet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
