Skip to content

MINOR: update KIP-1071 docs for KafkaClientSupplier #21366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mjsax wants to merge 2 commits into
base: trunk
Choose a base branch
from
+3 −1
Open

MINOR: update KIP-1071 docs for KafkaClientSupplier #21366

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef0f1ff
MINOR: update KIP-1071 docs for KafkaClientSupplier
mjsax Jan 28, 2026
568e945
improvement
mjsax Feb 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/streams/developer-guide/streams-rebalance-protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down