[jira] [Commented] (KAFKA-7317) Use collections subscription for main consumer to reduce metadata

["Matthias J. Sax (Jira)" <ji...@apache.org>]

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

Matthias J. Sax commented on KAFKA-7317:
----------------------------------------

[~ableegoldman] It seems that this ticket introduced a regression bug in 2.5.0 (cf. [https://stackoverflow.com/questions/61342530/kafka-streams-2-5-0-requires-input-topic]). I think the good new is, that it would be fixed via KAFKA-9127 that you already picked up?

Thoughts?

> Use collections subscription for main consumer to reduce metadata
> -----------------------------------------------------------------
>
>                 Key: KAFKA-7317
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7317
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Matthias J. Sax
>            Assignee: Sophie Blee-Goldman
>            Priority: Major
>             Fix For: 2.5.0
>
>
> In KAFKA-4633 we switched from "collection subscription" to "pattern subscription" for `Consumer#subscribe()` to avoid triggering auto topic creating on the broker. In KAFKA-5291, the metadata request was extended to overwrite the broker config within the request itself. However, this feature is only used in `KafkaAdminClient`. KAFKA-7320 adds this feature for the consumer client, too.
> This ticket proposes to use the new feature within Kafka Streams to allow the usage of collection based subscription in consumer and admit clients to reduce the metadata response size than can be very large for large number of partitions in the cluster.
> Note, that Streams need to be able to distinguish if it connects to older brokers that do not support the new metadata request and still use pattern subscription for this case.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)