You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Seweryn Habdank-Wojewodzki (JIRA)" <ji...@apache.org> on 2017/11/10 19:26:00 UTC

[jira] [Created] (KAFKA-6202) Classes OffsetsMessageFormatter and GroupMetadataMessageFormatter shall be used by kafka tools, but in the last releases lost visibility

Seweryn Habdank-Wojewodzki created KAFKA-6202:
-------------------------------------------------

             Summary: Classes OffsetsMessageFormatter and GroupMetadataMessageFormatter shall be used by kafka tools, but in the last releases lost visibility
                 Key: KAFKA-6202
                 URL: https://issues.apache.org/jira/browse/KAFKA-6202
             Project: Kafka
          Issue Type: Bug
    Affects Versions: 1.0.0, 0.11.0.0, 0.11.0.2, 0.11.0.3
            Reporter: Seweryn Habdank-Wojewodzki


Classes OffsetsMessageFormatter and GroupMetadataMessageFormatter shall be visible.

Also they shall/might be used by external toolis like console-consumer.
What is documented in the code!

But in last releases those two classes lost its visibility.

Currently they have none access modifier, which for subclasses are interpreted as private.
The proposal is to follow comments and use cases driven by console-consumer and change visibility from none/default to public.

Issue was found during discussion in SO: https://stackoverflow.com/questions/47218277/what-may-cause-huge-load-in-kafka-consumer-offsets-topic




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