ableegoldman commented on a change in pull request #10573:
URL: https://github.com/apache/kafka/pull/10573#discussion_r619557012
##########
File path: docs/streams/upgrade-guide.html
##########
@@ -93,6 +95,12 @@ <h1>Upgrade Guide and API Changes</h1>
</p>
<h3><a id="streams_api_changes_300"
href="#streams_api_changes_300">Streams API changes in 3.0.0</a></h3>
+ <p>
+ The <code>StreamsConfig.EXACTLY_ONCE</code> and
<code>StreamsConfig.EXACTLY_ONCE_BETA</code> configs have been deprecated, and
a new <code>StreamsConfig.EXACTLY_ONCE_V2</code> config has been
+ introduced. This is the same feature as eos-beta, but renamed to
highlight its production-readiness. Users of exactly-once semantics should plan
to migrate to the eos-v2 config and prepare for the removal of the deprecated
configs in 4.0 or after at least a year
+ from the release of 3.0, whichever comes last. Note that eos-v2 requires
broker version 2.5 or higher, like eos-beta, so users should begin to upgrade
their kafka cluster if necessary. See
Review comment:
We specifically voted on this in the KIP. Personally I was a bit
hesitant when someone suggested it, but I think the motivation there was to
give users some slight sense of urgency so they don't put off upgrading their
code or brokers, and then complain if/when we remove it because they haven't
done so yet. Not sure if you saw the WW3 thread that John started when he
synced over the commit that removed all the deprecated methods in 3.0...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
