This is an automated email from the ASF dual-hosted git repository.
bbejeck pushed a commit to branch 2.7
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/2.7 by this push:
new 811ec36 MINOR: Add KIP-584 to upgrade.html file (#9511)
811ec36 is described below
commit 811ec36d3deb090b2f2e04cd7a4a55d508bdaf1d
Author: Bill Bejeck <[email protected]>
AuthorDate: Tue Oct 27 14:35:02 2020 -0400
MINOR: Add KIP-584 to upgrade.html file (#9511)
Reviewers: Kowshik Prakasam <[email protected]>, Manikumar Reddy
<[email protected]>, Boyang Chen <[email protected]>
---
docs/upgrade.html | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 9d192ae..dddb781 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -43,6 +43,15 @@
<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
means you don't have to connect directly to ZooKeeper anymore for
managing SCRAM credentials.
