You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Vahid Hashemian (JIRA)" <ji...@apache.org> on 2017/06/17 00:09:00 UTC

[jira] [Updated] (KAFKA-4108) Improve DumpLogSegments offsets-decoder output format

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

Vahid Hashemian updated KAFKA-4108:
-----------------------------------
    Fix Version/s: 0.11.1.0

> Improve DumpLogSegments offsets-decoder output format
> -----------------------------------------------------
>
>                 Key: KAFKA-4108
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4108
>             Project: Kafka
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Jason Gustafson
>            Assignee: Vahid Hashemian
>             Fix For: 0.11.1.0
>
>
> When using the DumpLogSegments with the "--offsets-decoder" option (for consuming __consumer_offsets), the encoding of group metadata makes it a little difficult to identify individual fields. In particular, we use the following formatted string for group metadata: 
> {code}
> ${protocolType}:${groupMetadata.protocol}:${groupMetadata.generationId}:${assignment}
> {code}
> Keys have a similar formatting. Most users are probably not going to know which field is which based only on the output, so it would be helpful to include field names. Maybe we could just output a JSON object?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)