[
https://issues.apache.org/jira/browse/KAFKA-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-4108:
---------------------------------
*Reminder to the contributor / reviewer of the PR*: please note that the code
deadline for 1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate
your JIRA and see if it still makes sense to be merged into 1.0.0 or it could
be pushed out to 1.1.0, or be closed directly if the JIRA itself is not valid
any more, or re-assign yourself as contributor / committer if you are no longer
working on the JIRA.
> 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: 1.0.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)
