From ef0f1ff2dee2f26ca3a2773fad8dc89d48add7a6 Mon Sep 17 00:00:00 2001 From: "Matthias J. Sax" Date: Wed, 28 Jan 2026 12:05:56 -0800 Subject: [PATCH 1/2] MINOR: update KIP-1071 docs for KafkaClientSupplier KafkaClientSupplier is not fully supported with "streams" group. This PR adds a note to "not supported" features to the docs about it. --- docs/streams/developer-guide/streams-rebalance-protocol.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/streams/developer-guide/streams-rebalance-protocol.md b/docs/streams/developer-guide/streams-rebalance-protocol.md index 4ef05252ab76a..5bc90aa946d0d 100644 --- a/docs/streams/developer-guide/streams-rebalance-protocol.md +++ b/docs/streams/developer-guide/streams-rebalance-protocol.md @@ -63,6 +63,8 @@ The following features are not yet available and should be avoided when using th * **Online Migration**: Group migration while the application is running is not available between the classic and new streams protocol. +* **Custom Client Supplier**: Using a custom `KafkaClientSupplier` will only allow so provide restore/global consumer, producer, and admin client. It's not possible to provide the "main" consumer when "streams" groups are enabled. + # Why Use the Streams Rebalance Protocol? The Streams Rebalance Protocol offers several key advantages over the classic client-driven protocol: From 568e9459bf4614bbc27c09db1bfd70df920330dd Mon Sep 17 00:00:00 2001 From: "Matthias J. Sax" Date: Mon, 2 Feb 2026 18:45:48 -0800 Subject: [PATCH 2/2] improvement --- docs/streams/developer-guide/streams-rebalance-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/streams-rebalance-protocol.md b/docs/streams/developer-guide/streams-rebalance-protocol.md index 5bc90aa946d0d..0b56d4113429b 100644 --- a/docs/streams/developer-guide/streams-rebalance-protocol.md +++ b/docs/streams/developer-guide/streams-rebalance-protocol.md @@ -57,7 +57,7 @@ The following features are not yet available and should be avoided when using th * **Topology Updates**: If a topology is changed significantly (e.g., by adding new source topics or changing the number of subtopologies), a new streams group must be created. -* **High Availability Assignor**: Only the sticky assignor is supported. This implies that "warmup tasks" are not supported yet. +* **High Availability Assignor**: Only the sticky assignor is supported. This implies that "warmup tasks" and rack aware assignment are not supported yet. * **Regular Expressions**: Pattern-based topic subscription is not supported.