[ https://issues.apache.org/jira/browse/KAFKA-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725070#comment-14725070 ]
ASF GitHub Bot commented on KAFKA-2493: --------------------------------------- GitHub user sslavic opened a pull request: https://github.com/apache/kafka/pull/184 KAFKA-2493 Upgraded zkclient dependency from 0.5 to 0.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/sslavic/kafka feature/KAFKA-2492 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/184.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 #184 ---- commit 9f7d7e304c966349c5c39bbe852d3f4220ffe467 Author: Stevo Slavic <ssla...@gmail.com> Date: 2015-09-01T09:34:43Z KAFKA-2493 Upgraded zkclient dependency from 0.5 to 0.6 ---- > Add ability to fetch only keys in consumer > ------------------------------------------ > > Key: KAFKA-2493 > URL: https://issues.apache.org/jira/browse/KAFKA-2493 > Project: Kafka > Issue Type: Wish > Components: consumer > Reporter: Ivan Balashov > Assignee: Neha Narkhede > Priority: Minor > > Often clients need to find out which offsets contain necessary data. One of > the possible solutions would be to iterate with small fetch size. However, > this still leads to unnecessary data being transmitted in case keys already > reference searched data. The ability to fetch keys only would simplify search > for the necessary offset. > Of course, there can be other scenarios where consumer needs keys only, > without message part. -- This message was sent by Atlassian JIRA (v6.3.4#6332)