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

Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/06/02 07:14:04 UTC

[jira] [Updated] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

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

Ismael Juma updated KAFKA-5026:
-------------------------------
    Fix Version/s:     (was: 0.11.0.0)
                   0.11.0.1

> DebuggingConsumerId and DebuggingMessageFormatter and message format v2
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-5026
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5026
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Ismael Juma
>              Labels: exactly-once, tooling
>             Fix For: 0.11.0.1
>
>
> [~junrao] suggested the following:
> Currently, the broker supports a DebuggingConsumerId mode for the fetch request. Should we extend that so that the consumer can read the control message as well? Should we also have some kind of DebuggingMessageFormatter so that ConsoleConsumer can show all the newly introduced fields in the new message format (e.g., pid, epoch, etc) for debugging purpose?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)