Page History

...

Unfortunately, we also introduced a backward incompatibility bug in the newly added KStream.processValues implementation (cf

Jira
server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-1968819668

). To address this backward incompatibility, we propose to also deprecate KStreams.processValues methods, and replace with a backward compatible alternative. 

...

The only backward incompatibility we cannot address, is a potential issue for Kafka Streams 4.0.0 and 4.1.0 users (and potentially 4.0.1, 4.1.1, and 4.2.0 users, if they have an affected Topology, do not apply the fix of of

Jira
server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-1968819668

). if these uses need to migrate off the deprecated methods KStreams#processValues(). We will update the docs with all necessary information, including the documentation for 4.0, 4.1, and 4.2 release, to guide users to not use KStream#processValues() (or use it in the right way) to avoid any future issue. – Given that the bug of of

Jira
server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-1968819668

only  only applies to very specific scenarios, we expect only a very small number of users to be affected by any backward incompatibility issues, and these users still have time to address these issues manually before the next major release. Given that KStream#processValue() won't be removed any time soon, we provide plenty of time and users can upgrade to newer version of Kafka Streams just staying on the deprecated methods for the time being.

...