[
https://issues.apache.org/jira/browse/KAFKA-18410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910250#comment-17910250
]
Chia-Ping Tsai commented on KAFKA-18410:
----------------------------------------
Parsing metadata as comprehensively as possible is highly desirable. However,
we must carefully consider how to extend the formatter functionality.
1. Extending GroupMetadataMessageFormatter: While this approach offers
flexibility, it might obscure specific metadata details for users. To address
this, we could introduce a configuration mechanism to allow users to specify
which metadata fields they wish to view.
2. Creating dedicated formatters: This approach, exemplified by existing
formatters like TransactionLogMessageFormatter and OffsetsMessageFormatter,
provides granular control over metadata presentation. However, it may lead to
an increase in the number of formatters, which could potentially become
cumbersome to manage.
> Should GroupMetadataMessageFormatter print new records too?
> -----------------------------------------------------------
>
> Key: KAFKA-18410
> URL: https://issues.apache.org/jira/browse/KAFKA-18410
> Project: Kafka
> Issue Type: Improvement
> Reporter: David Jacot
> Assignee: Peter Lee
> Priority: Major
>
> At the moment, GroupMetadataMessageFormatter only prints out the metadata
> record of the classic groups. It seems that we should extend it to also print
> out the metadata of other groups (e.g. consumer, share, stream, etc.).
> Thoughts?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
