This is an automated email from the ASF dual-hosted git repository. cegerton pushed a commit to branch C0urante-patch-1 in repository https://gitbox.apache.org/repos/asf/kafka.git
commit 79f4a86382130d739bf243d919313c356067e628 Author: Chris Egerton <[email protected]> AuthorDate: Thu Jun 29 09:20:15 2023 -0400 MINOR: Update anchor link for exactly-once source connectors --- docs/connect.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connect.html b/docs/connect.html index e48692e8842..313913708f9 100644 --- a/docs/connect.html +++ b/docs/connect.html @@ -398,7 +398,7 @@ errors.tolerance=all</pre> <p>If a sink connector supports exactly-once semantics, to enable exactly-once 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 polic [...] - <h5><a id="connect_exactlyoncesource" href="connect_exactlyoncesource">Source connectors</a></h5> + <h5><a id="connect_exactlyoncesource" href="#connect_exactlyoncesource">Source connectors</a></h5> <p>If a source connector supports exactly-once semantics, you must configure your Connect cluster to enable framework-level support for exactly-once source connectors. Additional ACLs may be necessary if running against a secured Kafka cluster. Note that exactly-once support for source connectors is currently only available in distributed mode; standalone Connect workers cannot provide exactly-once semantics.</p>
