You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2018/06/18 19:18:00 UTC

[jira] [Resolved] (KAFKA-5237) SimpleConsumerShell logs terminating message to stdout instead of stderr

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

Manikumar resolved KAFKA-5237.
------------------------------
    Resolution: Auto Closed

Old consumer related tools are deprecated and  will be removed in KAFKA-2983.

> SimpleConsumerShell logs terminating message to stdout instead of stderr
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-5237
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5237
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients
>    Affects Versions: 0.10.2.1
>            Reporter: Daniel Einspanjer
>            Priority: Trivial
>
> The SimpleConsumerShell has one big advantage over the standard kafka-console-consumer client, it supports the --no-wait-at-logend parameter which lets you script its use without having to rely on a timeout or dealing with the exception and stacktrace thrown by said timeout.
> Unfortunately, when you use this option, it will write a termination message to stdout when it is finished.  This means if you are using it to dump the contents of a topic to a file, you get an extra line.
> This pull request just changes that one line to call System.err.println instead of println.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)