[
https://issues.apache.org/jira/browse/KAFKA-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020696#comment-14020696
]
Neha Narkhede commented on KAFKA-1438:
--------------------------------------
[~sriharsha] To rephrase Jun's finding, the way the system test relies on
determining # of unique messages is by turning on DEBUG in ProducerPerformance
and the parsing the log for the unique IDs that it outputs. Maybe there is a
minor change required to the default log4j.properties that got moved during the
patch?
> Migrate kafka client tools
> --------------------------
>
> Key: KAFKA-1438
> URL: https://issues.apache.org/jira/browse/KAFKA-1438
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Sriharsha Chintalapani
> Labels: newbie, tools, usability
> Fix For: 0.8.2
>
> Attachments: KAFKA-1438.patch, KAFKA-1438_2014-05-27_11:45:29.patch,
> KAFKA-1438_2014-05-27_12:16:00.patch, KAFKA-1438_2014-05-27_17:08:59.patch,
> KAFKA-1438_2014-05-28_08:32:46.patch, KAFKA-1438_2014-05-28_08:36:28.patch,
> KAFKA-1438_2014-05-28_08:40:22.patch, KAFKA-1438_2014-05-30_11:36:01.patch,
> KAFKA-1438_2014-05-30_11:38:46.patch, KAFKA-1438_2014-05-30_11:42:32.patch
>
>
> Currently the console/perf client tools scatter across different packages,
> we'd better to:
> 1. Move Consumer/ProducerPerformance and SimpleConsumerPerformance to tools
> and remove the perf sub-project.
> 2. Move ConsoleConsumer from kafka.consumer to kafka.tools.
> 3. Move other consumer related tools from kafka.consumer to kafka.tools.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
