This is an automated email from the ASF dual-hosted git repository.
JNSimba pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new f38a37b0839 [docs](flink) Clarify binlog offset table purpose and
manual recovery (#4198)
f38a37b0839 is described below
commit f38a37b0839b263a35b293f1fe231fb56afefe00
Author: wudi <[email protected]>
AuthorDate: Fri Oct 9 12:04:00 2026 +0800
[docs](flink) Clarify binlog offset table purpose and manual recovery
(#4198)
The Binlog offset table can be mistaken for a recovery source. Clarify
in both English and Chinese that it only publishes consumption progress
covered by completed Checkpoints and is not read automatically when a
job starts or restarts.
Document how to manually resume from a recorded `offset_timestamp` with
`source.scan.mode = 'from-timestamp'` and `source.scan.timestamp` when
Checkpoint or Savepoint recovery is unavailable.
Validation: reviewed the English and Chinese changes and ran `git diff
--check`. Tests and site builds were not run as requested. Page paths,
anchors, links, and navigation remain unchanged.
---
.../flink-doris-connector/incremental-read.md | 15 ++++++++++++---
.../flink-doris-connector/incremental-read.md | 15 ++++++++++++---
2 files changed, 24 insertions(+), 6 deletions(-)
diff --git
a/docs/connection-integration/data-integration/flink-doris-connector/incremental-read.md
b/docs/connection-integration/data-integration/flink-doris-connector/incremental-read.md
index eafa6a5d4fd..9ea08eb8d40 100644
---
a/docs/connection-integration/data-integration/flink-doris-connector/incremental-read.md
+++
b/docs/connection-integration/data-integration/flink-doris-connector/incremental-read.md
@@ -95,7 +95,9 @@ When this option is enabled, the source table must declare a
primary key, as in
## Publishing Consumption Progress to Doris (Optional) {#offset-table}
-Consumption progress is stored in Flink Checkpoints by default. To also query
the progress in Doris, create the following offset table:
+Consumption progress is stored in Flink Checkpoint state. The optional offset
table is only for observing progress covered by completed Checkpoints. The
Connector does not read this table to automatically resume consumption when a
job starts or restarts.
+
+To query consumption progress in Doris, create the following offset table:
```sql
CREATE DATABASE IF NOT EXISTS ops;
@@ -118,7 +120,14 @@ PROPERTIES (
'source.binlog.consumer-id' = 'student-sync'
```
-`source.binlog.consumer-id` identifies the consumer job and should remain
unchanged when the same job restarts.
+`source.binlog.consumer-id` identifies the consumer job in the offset table.
Keep it unchanged when the same job restarts to track its progress.
+
+If you cannot restore from a Flink Checkpoint or Savepoint, copy the
`offset_timestamp` from the offset table into `source.scan.timestamp` and set
`source.scan.mode` to `from-timestamp` to manually resume from that offset. For
example:
+
+```sql
+'source.scan.mode' = 'from-timestamp',
+'source.scan.timestamp' = '2026-10-09 10:00:00'
+```
## Options {#options}
@@ -131,5 +140,5 @@ The following options control incremental reading. The
other Source options are
| source.binlog.increment-type | detail | N | Binlog change type:
`detail`, `min_delta`, or `append_only`.
|
| source.binlog.poll-interval | 10s | N | Interval for
polling new Binlog data. The minimum value is 1 second.
|
| source.binlog.visible-wait-timeout | 5m | N | Maximum time
for the Connector to retry the same read window after Doris returns a
transaction visibility wait timeout error. Set to `0s` to disable retries;
negative values are invalid. |
-| source.binlog.offset-table | -- | N | Doris table in
`database.table` format used to publish offsets covered by completed
Checkpoints. Configure with `source.binlog.consumer-id` and `jdbc-url`. |
+| source.binlog.offset-table | -- | N | Doris table in
`database.table` format used to publish offsets covered by completed
Checkpoints for observation only, not for automatic recovery. Configure with
`source.binlog.consumer-id` and `jdbc-url`. |
| source.binlog.consumer-id | -- | N | Stable consumer
identifier written to `source.binlog.offset-table`.
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/connection-integration/data-integration/flink-doris-connector/incremental-read.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/connection-integration/data-integration/flink-doris-connector/incremental-read.md
index d01eb43436e..90e88bd993e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/connection-integration/data-integration/flink-doris-connector/incremental-read.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/connection-integration/data-integration/flink-doris-connector/incremental-read.md
@@ -95,7 +95,9 @@ SET 'table.exec.source.cdc-events-duplicate' = 'true';
## 将消费进度写入 Doris（可选） {#offset-table}
-消费进度默认保存在 Flink Checkpoint 中。如果还需要在 Doris 中查询消费进度，可以创建以下 Offset 表：
+消费进度保存在 Flink Checkpoint 状态中。可选的 Offset 表仅用于观测已完成 Checkpoint
所覆盖的消费进度。Connector 不会在任务启动或重启时读取该表来自动恢复消费位点。
+
+如果需要在 Doris 中查询消费进度，可以创建以下 Offset 表：
```sql
CREATE DATABASE IF NOT EXISTS ops;
@@ -118,7 +120,14 @@ PROPERTIES (
'source.binlog.consumer-id' = 'student-sync'
```
-`source.binlog.consumer-id` 用于标识当前消费任务，同一任务重启时应保持不变。
+`source.binlog.consumer-id` 用于在 Offset 表中标识当前消费任务，同一任务重启时应保持不变，便于观测消费进度。
+
+如果无法从 Flink Checkpoint 或 Savepoint 恢复，可以取出 Offset 表中的 `offset_timestamp`，填入
`source.scan.timestamp`，并将 `source.scan.mode` 设置为
`from-timestamp`，手动从该位点恢复消费。例如：
+
+```sql
+'source.scan.mode' = 'from-timestamp',
+'source.scan.timestamp' = '2026-10-09 10:00:00'
+```
## 配置项 {#options}
@@ -131,5 +140,5 @@ PROPERTIES (
| source.binlog.increment-type | detail | N | Binlog 变更类型，支持
`detail`、`min_delta` 和 `append_only`
|
| source.binlog.poll-interval | 10s | N | 轮询新 Binlog
数据的时间间隔，最小值为 1 秒
|
| source.binlog.visible-wait-timeout | 5m | N | Doris
返回事务可见性等待超时错误后，Connector 重试同一读取区间的最长时间。设置为 `0s` 可关闭重试；不能为负值。 |
-| source.binlog.offset-table | -- | N | 用于发布成功 Checkpoint
所覆盖 offset 的 Doris 表，格式为 `database.table`。需要同时配置 `source.binlog.consumer-id` 和
`jdbc-url` |
+| source.binlog.offset-table | -- | N | 用于发布已完成 Checkpoint
所覆盖 offset 的 Doris 表，仅供观测，不用于自动恢复。格式为 `database.table`，需要同时配置
`source.binlog.consumer-id` 和 `jdbc-url`。 |
| source.binlog.consumer-id | -- | N | 写入
`source.binlog.offset-table` 的稳定消费者标识
|
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
