Skip to content

KAFKA-21128: Generalize version in upgrade guide - #23524

Open
Parkerhiphop wants to merge 2 commits into
apache:trunkfrom
Parkerhiphop:kafka-21128-generalize-upgrade-guide
Open

Parkerhiphop wants to merge 2 commits into
apache:trunkfrom
Parkerhiphop:kafka-21128-generalize-upgrade-guide

Conversation

@Parkerhiphop

@Parkerhiphop Parkerhiphop commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

The upgrade guide currently refers specifically to 4.3.0 when describing the upgrade path.

This updates the wording to use a more general version so the instructions also apply to later releases.

Reviewers: Chia-Ping Tsai chia7712@gmail.com

@github-actions github-actions Bot added triage PRs from the community docs small Small PRs labels Sep 20, 2026
# Upgrade Guide and API Changes

Upgrading from any older version to 4.3.0 is possible: if upgrading from 3.4 or below, you will need to do two rolling bounces, where during the first rolling bounce phase you set the config `upgrade.from="older version"` (possible values are `"2.4" - "3.4"`) and during the second you remove it. This is required to safely handle 2 changes. The first is a change in foreign-key join serialization format. The second is a change in the serialization format for an internal repartition topic. For more details, please refer to [KIP-904](https://cwiki.apache.org/confluence/x/P5VbDg):
Upgrading from any older version to the current release is possible: if upgrading from 3.4 or below, you will need to do two rolling bounces, where during the first rolling bounce phase you set the config `upgrade.from="older version"` (possible values are `"2.4" - "3.4"`) and during the second you remove it. This is required to safely handle 2 changes. The first is a change in foreign-key join serialization format. The second is a change in the serialization format for an internal repartition topic. For more details, please refer to [KIP-904](https://cwiki.apache.org/confluence/x/P5VbDg):

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Would you mind updating the links hardcoded with /43/ to use /{version}/ as well?

@Parkerhiphop Parkerhiphop Sep 20, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes. I have updated all links.

@github-actions github-actions Bot removed the triage PRs from the community label Sep 21, 2026
## Streams API changes in 3.6.0

Rack aware task assignment was introduced in [KIP-925](https://cwiki.apache.org/confluence/x/CQ40Dw). Rack aware task assignment can be enabled for `StickyTaskAssignor` or `HighAvailabilityTaskAssignor` to compute task assignments which can minimize cross rack traffic under certain conditions. For more information, including how it can be enabled and further configured, see the [**Kafka Streams Developer Guide**](/43/documentation/streams/developer-guide/config-streams.html#rack-aware-assignment-strategy).
Rack aware task assignment was introduced in [KIP-925](https://cwiki.apache.org/confluence/x/CQ40Dw). Rack aware task assignment can be enabled for `StickyTaskAssignor` or `HighAvailabilityTaskAssignor` to compute task assignments which can minimize cross rack traffic under certain conditions. For more information, including how it can be enabled and further configured, see the [**Kafka Streams Developer Guide**](/{version}/documentation/streams/developer-guide/config-streams.html#rack-aware-assignment-strategy).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/{version}/documentation/streams/developer-guide/config-streams.html#rack-aware-assignment-strategy).

Those links are broken. Would you mind fixing them in this PR as well?

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.

2 participants