You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by lu...@apache.org on 2025/11/04 09:10:40 UTC

(kafka) branch trunk updated: MINOR: Make feature upgrade instructions more precise (#20816)

This is an automated email from the ASF dual-hosted git repository.

lucasbru pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 750523f3fa6 MINOR: Make feature upgrade instructions more precise (#20816)
750523f3fa6 is described below

commit 750523f3fa6a3d292823eb0bfe274a359e98a4de
Author: Lucas Brutschy <lb...@confluent.io>
AuthorDate: Tue Nov 4 10:10:34 2025 +0100

    MINOR: Make feature upgrade instructions more precise (#20816)
    
    In some frameworks such as Strimzi, the metadata version seems to be
    hardcoded.   In this case, or if we have a pre-existing cluster,  users
    need to enable the feature explicitly.
    
    Reviewers: Matthias J. Sax <ma...@confluent.io>
    
    ---------
    
    Co-authored-by: Copilot <17...@users.noreply.github.com>
---
 docs/streams/upgrade-guide.html | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html
index b875fcddc89..3c2c8e66df3 100644
--- a/docs/streams/upgrade-guide.html
+++ b/docs/streams/upgrade-guide.html
@@ -184,9 +184,19 @@
         Set <code>unstable.feature.versions.enable=true</code> for controllers and brokers, and
         set <code>unstable.api.versions.enable=true</code> on the brokers as well. In your Kafka Streams application
         configuration, set <code>group.protocol=streams</code>.
-        After the new feature is configured, check
-	<code>kafka-features.sh --bootstrap-server localhost:9092 describe</code>
-	and `streams.version` should now have FinalizedVersionLevel 1.
+    </p>
+
+    <p>
+        When <code>unstable.api.versions.enable=true</code> is set when the kafka storage is first created,
+        and no explicit metadata version is set, the feature will be enabled by default. In other configurations
+        (e.g. if the cluster already existed, or a metadata version was hardcoded), you may have to enable it explicitly.
+        First, check the current feature level by running
+        <code>kafka-features.sh --bootstrap-server localhost:9092 describe</code>.
+        If <code>streams.version</code> shows <code>FinalizedVersionLevel</code> is 1, no action is needed.
+        Otherwise, upgrade by running
+        <code>kafka-features.sh --bootstrap-server localhost:9092 upgrade --feature streams.version=1</code>.
+        After the upgrade, verify the change by running
+        <code>kafka-features.sh --bootstrap-server localhost:9092 describe</code>.
     </p>
 
     <p>