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

2019-02-17 Thread Matthias J. Sax (JIRA)


[ 
https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770572#comment-16770572
 ] 

Matthias J. Sax commented on KAFKA-5026:


Moving all major/minor/trivial tickets that are not merged yet out of 2.2 
release.

> 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: 2.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)


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

2018-10-02 Thread Dong Lin (JIRA)


[ 
https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635603#comment-16635603
 ] 

Dong Lin commented on KAFKA-5026:
-

Moving this to 2.2.0 since PR is not ready yet.

> 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: 2.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)