This is an automated email from the ASF dual-hosted git repository. clolov pushed a commit to branch 4.2 in repository https://gitbox.apache.org/repos/asf/kafka.git
commit 32d93b466feeb253c28ef4aaeb90213205f93e23 Author: Matthias J. Sax <[email protected]> AuthorDate: Mon Feb 9 11:42:50 2026 -0800 MINOR: update KIP-1071 docs for KafkaClientSupplier (#21366) KafkaClientSupplier is not fully supported with "streams" group. This PR adds a note to "not supported" features to the docs about it. Reviewers: Lucas Brutschy <[email protected]> --- docs/streams/developer-guide/streams-rebalance-protocol.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/streams-rebalance-protocol.md b/docs/streams/developer-guide/streams-rebalance-protocol.md index 4ef05252ab7..0b56d411342 100644 --- a/docs/streams/developer-guide/streams-rebalance-protocol.md +++ b/docs/streams/developer-guide/streams-rebalance-protocol.md @@ -57,12 +57,14 @@ 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. * **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:
