ableegoldman commented on a change in pull request #10573:
URL: https://github.com/apache/kafka/pull/10573#discussion_r618912357



##########
File path: docs/streams/developer-guide/config-streams.html
##########
@@ -667,12 +668,14 @@ <h4><a class="toc-backref" 
href="#id30">probing.rebalance.interval.ms</a><a clas
           <span 
id="streams-developer-guide-processing-guarantee"></span><h4><a 
class="toc-backref" href="#id25">processing.guarantee</a><a class="headerlink" 
href="#processing-guarantee" title="Permalink to this headline"></a></h4>
           <blockquote>
             <div>The processing guarantee that should be used.
-              Possible values are <code class="docutils literal"><span 
class="pre">"at_least_once"</span></code> (default),
-              <code class="docutils literal"><span 
class="pre">"exactly_once"</span></code> (for EOS version 1),
-              and <code class="docutils literal"><span 
class="pre">"exactly_once_beta"</span></code> (for EOS version 2).
-              Using <code class="docutils literal"><span 
class="pre">"exactly_once"</span></code> requires broker
-              version 0.11.0 or newer, while using <code class="docutils 
literal"><span class="pre">"exactly_once_beta"</span></code>
-              requires broker version 2.5 or newer.
+              Possible values are <code class="docutils literal"><span 
class="pre">"at_least_once"</span></code> (default)
+              and <code class="docutils literal"><span 
class="pre">"exactly_once_v2"</span></code> (for EOS version 2).
+              Deprecated config options are <code class="docutils 
literal"><span class="pre">"exactly_once"</span></code> (for EOS alpha),

Review comment:
       I think given we have just rolled this out, and many users are likely 
still in the process of upgrading their brokers to a sufficient version, we 
should continue to mention EOS alpha. And then we may as well mention beta as 
well for consistency. Don't feel too strongly though




-- 
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


Reply via email to