Skip to content

Conversation

Nikita-Shupletsov
Copy link
Contributor

@Nikita-Shupletsov Nikita-Shupletsov commented Sep 16, 2025

Removed versions 2.3 and below from UpgradeFromValues, including all the
usagesof them.

Reviewers: Matthias J. Sax [email protected]

@github-actions github-actions bot added triage PRs from the community streams labels Sep 16, 2025
@mjsax mjsax added ci-approved and removed triage PRs from the community labels Sep 16, 2025
@mjsax
Copy link
Member

mjsax commented Sep 18, 2025

It seems we should also update the docs here: https://github.com/apache/kafka/blob/trunk/docs/streams/developer-guide/config-streams.html#L1237-L1238 The last sentence does not apply any longer.

@mjsax
Copy link
Member

mjsax commented Sep 18, 2025

Also for the upgrade guide: https://github.com/apache/kafka/blob/trunk/docs/streams/upgrade-guide.html

You should set this config to the appropriate version before bouncing your instances and upgrading them to the newer version. Once everyone is on the
newer version, you should remove this config and do a second rolling bounce. It is only necessary to set this config and follow the two-bounce upgrade path
when upgrading from below version 2.0, or when upgrading to 2.4+ from any version lower than 2.4.
when upgrading to 3.4+ from any version lower than 3.4.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed to 3.4 to align with the upgrade guide. if it's incorrect, please let me know, I will fix it

<p> As an alternative, an offline upgrade is also possible. Upgrading from any versions as old as 0.10.0.x to {{fullDotVersion}} in offline mode require the following steps: </p>
<ul>
<li> stop all old (e.g., 0.10.0.x) application instances </li>
<li> update your code and swap old code and jar file with new code and new jar file </li>
Copy link
Member

@mjsax mjsax Sep 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cannot comment above, but it say:

As an alternative, an offline upgrade is also possible. Upgrading from any versions as old as 0.10.0.x to {{fullDotVersion}} in offline mode require the following steps:

And stop all old (e.g., 0.10.0.x) application instances.

That's not correct any longer. Let's bump 0.10.0.x to 0.11.0.

I am also wondering if we should whole paragraphs Streams API changes in XXX for at least all 0.10.0.x and 0.10.1.x releases. Maybe even more (ie, up-to-including 2.3.x, we we only support rolling-bounce upgrade from 2.4+ as oldest version to 4.0+ now), and add a sentence + link to eg 3.9 docs for these older versions?

\cc @lucasbru @bbejeck WDYT?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also wondering if we should whole paragraphs

Something is missing here. 'Remove'?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming the intent is to remove, I would say yes for at least the 0.10.x versions. I'm also good with expanding the cleanup for versions up to 2.3.x and adding a link for upgrading the older versions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes... "remove" :)

for more details.
</p>

<p>For a table that shows Streams API compatibility with Kafka broker versions, see <a href="#streams_api_broker_compat">Broker Compatibility</a>.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Further below, there is more stuff, that seems to be old and we can remove it?

To run a Kafka Streams application version 2.2.1, 2.3.0, or higher a broker version 0.11.0 or higher is required and the on-disk message format must be 0.11 or higher. [...]

Ie, the whole two paragraphs?

…ffline upgrade.

Removed all information about versions 2.3.x and below.
Copy link
Member

@mjsax mjsax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. Overall LGTM. Two more tiny things.

<li> Windows are not named anymore: TimeWindows.of("name", 1000) changes to TimeWindows.of(1000) (cf. DSL: new parameter to specify state store names) </li>
<li> JoinWindows has no default size anymore: JoinWindows.of("name").within(1000) changes to JoinWindows.of(1000) </li>
</ul>
<p>For Streams API changes in version older than 2.4.x, please check <a href="/39/documentation/streams/upgrade-guide">3.9 upgrade document</a>.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the section below, we still mention version 2.1, 2.2, and 2.3:

            <td>Kafka Streams API (rows)</td>
            <td>2.1.x and<br>2.2.x and<br>2.3.x and<br>2.4.x and<br>2.5.x and<br>2.6.x and<br>2.7.x and<br>2.8.x and<br>3.0.x and<br>3.1.x and<br>3.2.x and<br>3.3.x and<br>3.4.x and<br>3.5.x and<br>3.6.x and<br>3.7.x and<br>3.8.x and<br>3.9.x and<br>4.0.x</td>

Might be good to also remove them?

<p>
We removed the following deprecated APIs:
</p>
<ul>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not 100% sure if any of this needs to be deleted

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can keep this as-is, because it's the list of things we removed with 3.0.0 release.

@mjsax mjsax merged commit 7ddd0d7 into apache:trunk Oct 3, 2025
22 checks passed
@mjsax
Copy link
Member

mjsax commented Oct 3, 2025

Thanks for the PR. Merged to trunk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants