chia7712 commented on code in PR #20334:
URL: https://github.com/apache/kafka/pull/20334#discussion_r2514729130
##########
docs/upgrade.html:
##########
@@ -113,6 +113,35 @@ <h5><a id="upgrade_420_notable"
href="#upgrade_420_notable">Notable changes in 4
<li>
The <code>num.replica.fetchers</code> config has a new lower bound of
1.
</li>
+ <li>
+ Improvements have been made to the validation rules and default values
of LIST-type configurations
+ (<a href="https://cwiki.apache.org/confluence/x/HArXF";>KIP-1161</a>).
+ <ul>
+ <li>
+ LIST-type configurations now enforce stricter validation:
+ <ul>
+ <li>Null values are no longer accepted for most LIST-type
configurations, except those that explicitly
+ allow a null default value or where a null value has a
well-defined semantic meaning.</li>
+ <li>Duplicate entries within the same list are no longer
permitted.</li>
Review Comment:
> If v4.last had a tool to generate a compatibility report,
I assume the tool will be implemented in 4.3 and will be enhanced with more
checks over time. Users will be able to ask it whether their configuration file
and exising cluster are compatible with its version
> that would help users migrate to 5.0 without us having to violate the
consistency checks for the newly incompatible configs.
Users will still violate the incompatible configs if they fail to adjust
their existing cluster (or configuration file) before upgrading
The tool could also address KAFKA-19851. The compatibility report should
remind users that `message.format.version` is no longer supported in the new
version, prompting them to use the Admin Client to remove the configuration
before upgrading to 4.x
--
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]
