mjsax commented on code in PR #23803:
URL: https://github.com/apache/kafka/pull/23803#discussion_r4561096437


##########
docs/getting-started/upgrade.md:
##########
@@ -26,6 +26,14 @@ type: docs
 -->
 
 
+## Upgrading to 4.5.0
+
+### Upgrading Servers to 4.5.0 from any version 3.3.x through 4.4.0
+
+### Notable changes in 4.5.0
+
+  * A custom assignor configured in `group.streams.assignors` may now reuse 
the name of a built-in assignor, and then replaces that built-in; such a 
configuration used to fail broker startup with a `ConfigException`. This 
matters because `balanced` is now a built-in streams task assignor that is 
registered by default (the default of `group.streams.assignors` is now 
`sticky,balanced`), so a broker that registers a custom assignor named 
`balanced` keeps starting after the upgrade and keeps using that custom 
assignor. Configuring a custom assignor together with the built-in whose name 
it reuses still fails broker startup, because assignor names must be unique. 
For further details, please refer to 
[KAFKA-21194](https://issues.apache.org/jira/browse/KAFKA-21194).

Review Comment:
   > may now reuse the name of a built-in assignor
   
   [But the](https://issues.apache.org/jira/browse/KAFKA-20843) was shipped 
with AK 4.4.0 release, which also add custom assignor support. No nothing 
changes in 4.5 release and it was always this way.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to