kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damian Guy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2
Date Thu, 01 Feb 2018 11:44:00 GMT

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

Damian Guy updated KAFKA-5026:
------------------------------
    Fix Version/s:     (was: 1.1.0)
                   1.2.0

> 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
>            Priority: Major
>              Labels: exactly-once, tooling
>             Fix For: 1.2.0
>
>
> [~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
(v7.6.3#76005)

Mime
View raw message