This is an automated email from the ASF dual-hosted git repository.
chia7712 pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 1b588afb961 MINOR: Fix the link for the heading Errant Record Reporter
in connect.html (#20313)
1b588afb961 is described below
commit 1b588afb9616a426db0ddfc4d8df1c81df6a601a
Author: Chih-Yuan Chien <[email protected]>
AuthorDate: Thu Aug 7 00:31:46 2025 +0800
MINOR: Fix the link for the heading Errant Record Reporter in connect.html
(#20313)
The link for the heading Errant Record Reporter is missing the # symbol,
which is causing it to redirect to a 404 Not Found page. Please refer
to the updated preview. <img width="665" height="396"
alt="kafka-site-preview"
src="https://github.com/user-attachments/assets/1c6f3ea9-de9b-4b2c-a4d6-919199a6ff6f";
/>
Reviewers: PoAn Yang <[email protected]>, Ken Huang
<[email protected]>, Chia-Ping Tsai <[email protected]>
---
docs/connect.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/connect.html b/docs/connect.html
index 457bc575eaa..aa3c2af3ea9 100644
--- a/docs/connect.html
+++ b/docs/connect.html
@@ -762,7 +762,7 @@ public List<SourceRecord> poll() throws
InterruptedException {
<p>The <code>flush()</code> method is used during the offset commit
process, which allows tasks to recover from failures and resume from a safe
point such that no events will be missed. The method should push any
outstanding data to the destination system and then block until the write has
been acknowledged. The <code>offsets</code> parameter can often be ignored, but
is useful in some cases where implementations want to store offset information
in the destination store to provide ex [...]
delivery. For example, an HDFS connector could do this and use atomic move
operations to make sure the <code>flush()</code> operation atomically commits
the data and offsets to a final location in HDFS.</p>
- <h5><a id="connect_errantrecordreporter"
href="connect_errantrecordreporter">Errant Record Reporter</a></h5>
+ <h5><a id="connect_errantrecordreporter"
href="#connect_errantrecordreporter">Errant Record Reporter</a></h5>
<p>When <a href="#connect_errorreporting">error reporting</a> is enabled
for a connector, the connector can use an <code>ErrantRecordReporter</code> to
report problems with individual records sent to a sink connector. The following
example shows how a connector's <code>SinkTask</code> subclass might obtain and
use the <code>ErrantRecordReporter</code>, safely handling a null reporter when
the DLQ is not enabled or when the connector is installed in an older Connect
runtime that doesn [...]
