[
https://issues.apache.org/jira/browse/KAFKA-20536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-20536.
------------------------------------
Fix Version/s: 4.3.0
4.2.1
Resolution: Fixed
> Empty "Upgrading Servers to 4.1.0" section in upgrade docs across
> trunk/4.2/4.3
> -------------------------------------------------------------------------------
>
> Key: KAFKA-20536
> URL: https://issues.apache.org/jira/browse/KAFKA-20536
> Project: Kafka
> Issue Type: Task
> Affects Versions: 4.2.0, 4.3.0, 4.4.0
> Reporter: Muralidhar Basani
> Assignee: Muralidhar Basani
> Priority: Minor
> Labels: docs
> Fix For: 4.3.0, 4.2.1
>
> Attachments: EmptyHeaders.png
>
>
> In trunk, 4.2 and 4.3, the section "Upgrading Servers to 4.1.0" in upgrade
> docs across trunk/4.2/4.3 is empty.
> This is already fixed in [https://github.com/apache/kafka/pull/22149]
>
> Also update the below
> {code:java}
> ## Upgrading to 4.1.2
> ### Notable changes in 4.1.2
> * Includes a fix for the rare Kafka producer bug
> ([KAFKA-19012](https://issues.apache.org/jira/browse/KAFKA-19012)), in which
> a record could end up on the incorrect topic.
> ## Upgrading to 4.1.1
> ### Notable changes in 4.1.1
> * Includes a fix for the critical Kafka Streams bug
> ([KAFKA-19748](https://issues.apache.org/jira/browse/KAFKA-19748)), solving
> the memory leak issues that affected users of range scans and certain DSL
> operators (session windows, sliding windows, stream-stream joins, foreign-key
> joins).
> * Includes a fix for the critical Kafka Streams bug
> ([KAFKA-19479](https://issues.apache.org/jira/browse/KAFKA-19479)), related
> to potential data loss.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
