> The ZooKeeper project fixed this bug in ZooKeeper > 3.9.3 but it is unlikely that we will upgrade the ZooKeeper version > for Kafka 3.9.x.
Our decision on upgrading dependencies likely hinges on how we approach Kafka version 3.9.x. For branches in maintenance mode, it's generally advisable to avoid frequent dependency upgrades. This aligns with the previous discussion around JDK 23 (https://lists.apache.org/thread/vl43q9wqq4xs67xx61f0t0850y2b037o). Perhaps it would be beneficial to discuss situation of 3.9.x again. While we can always discuss individual changes, reaching a consensus on the handling of 3.9.x as a "special" case would be ideal. Best, Chia-Ping On 2025/01/28 18:47:36 José Armando García Sancio wrote: > Hi all, > > I am not sure if this was discussed before but what is our plan for > jira (bugs) that are specific to the implementation of Kafka that is > specific to the ZooKeeper implementation? > > It would be nice to easily identify all such jiras. Should we tag all > such jiras with the zookeeper label? > > Should we resolve all such issues with the resolution "won't do" and > state that Kafka doesn't depend on ZooKeeper after 4.0.0? I am > specifically thinking of this issue > https://issues.apache.org/jira/browse/KAFKA-15844. It is blocked on a > ZooKeeper issue. The ZooKeeper project fixed this bug in ZooKeeper > 3.9.3 but it is unlikely that we will upgrade the ZooKeeper version > for Kafka 3.9.x. > > Thanks, > -- > -José >
