tikimims commented on code in PR #12941:
URL: https://github.com/apache/kafka/pull/12941#discussion_r1042942666
##########
docs/connect.html:
##########
@@ -369,6 +369,114 @@ <h4><a id="connect_errorreporting"
href="#connect_errorreporting">Error Reportin
# Tolerate all errors.
errors.tolerance=all</pre>
+ <h4><a id="connect_exactlyonce" href="#connect_exactlyonce">Exactly-once
support</a></h4>
+
+ <p>Kafka Connect is capable of providing exactly-once delivery guarantees
for sink connectors (as of version 0.11.0) and source connectors (as of version
3.3.0). Please note that <b>support for exactly-once delivery is highly
dependent on the type of connector being run.</b> Even if all the correct
worker properties are set in the config for each node in a cluster, if a
connector is not designed to or simply cannot take advantage of the
capabilities of the Kafka Connect framework, exactly-once may not be
possible.</p>
+
+ <h5><a id="connect_exactlyoncesink" href="#connect_exactlyoncesink">Sink
connectors</a></h5>
+
+ <p>If a sink connector supports exactly-once delivery, all that is
necessary to enable exactly-once delivery at the Connect worker level is
ensuring that its consumer group is configured to ignore records in aborted
transactions. This can be done by setting the worker property
<code>consumer.isolation.level</code> to <code>read_committed</code> or, if
running a version of Kafka Connect that supports it, using a <a
href="#connectconfigs_connector.client.config.override.policy">connector client
config override policy</a> that allows the
<code>consumer.override.isolation.level</code> property to be set to
<code>read_committed</code> in individual connector configs. There are no
additional ACL requirements.</p>
Review Comment:
```suggestion
<p>If a sink connector supports exactly-once delivery and to enable
exactly-once delivery at the Connect worker level, you must ensure its consumer
group is configured to ignore records in aborted transactions. You can do this
by setting the worker property <code>consumer.isolation.level</code> to
<code>read_committed</code> or, if running a version of Kafka Connect that
supports it, using a <a
href="#connectconfigs_connector.client.config.override.policy">connector client
config override policy</a> that allows the
<code>consumer.override.isolation.level</code> property to be set to
<code>read_committed</code> in individual connector configs. There are no
additional ACL requirements.</p>
```
--
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.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
