MINOR: Add KIP-584 to upgrade.html file (#9511)

Reviewers: Kowshik Prakasam <kprakasam@confluent.io>, Manikumar Reddy <manikumar.reddy@gmail.com>, Boyang Chen <boyang@confluent.io>
This commit is contained in:
Bill Bejeck 2020-10-27 14:35:02 -04:00 committed by GitHub
parent aa287acb2e
commit 81465a1951
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 0 deletions

View File

@ -44,6 +44,15 @@
topics deletions to prevent a cluster from being harmed via
<a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-599%3A+Throttle+Create+Topic%2C+Create+Partition+and+Delete+Topic+Operations">KIP-599</a>
</li>
<li>
When new features become available in Kafka there are two main issues:
<ol>
<li>How do Kafka clients become aware of broker capabilities?</li>
<li>How does the broker decide which features to enable?</li>
</ol>
<a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features">KIP-584</a>
provides a flexible and operationally easy solution for client discovery, feature gating and rolling upgrades using a single restart.
</li>
<li>
The addition of <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-554%3A+Add+Broker-side+SCRAM+Config+API">KIP-554</a>
continues progress towards the goal of Zookeeper removal from Kafka. The addition of KIP-554