From 979ec2deb2d34963fb31b301007a0340d0241180 Mon Sep 17 00:00:00 2001 From: Kathryn May Date: Mon, 10 Feb 2025 10:58:34 -0500 Subject: [PATCH] Update --- src/current/v25.1/changefeed-messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/v25.1/changefeed-messages.md b/src/current/v25.1/changefeed-messages.md index eb26c923924..d4e7cd72e0a 100644 --- a/src/current/v25.1/changefeed-messages.md +++ b/src/current/v25.1/changefeed-messages.md @@ -369,7 +369,7 @@ There are three different ways to configure resolved timestamp messages: The changefeed job's coordinating node will emit resolved timestamp messages once the changefeed has reached a checkpoint. The frequency of the checkpoints determine how often the resolved timestamp messages emit to the sink. To configure how often the changefeed checkpoints, you can set the [`min_checkpoint_frequency`]({% link {{ page.version.version }}/create-changefeed.md %}#min-checkpoint-frequency) option and [flush frequency]({% link {{ page.version.version }}/changefeed-sinks.md %}) (if flushing is configurable for your sink). -The `min_checkpoint_frequency` option controls how often nodes flush their progress to the coordinating node. If you need resolved timestamp messages to emit from the changefeed more frequently than the `30s` default, then you must set `min_checkpoint_frequency` to at least the desired resolved timestamp frequency. For example: +The `min_checkpoint_frequency` option controls how often nodes flush their progress to the coordinating node. If you need resolved timestamp messages to emit from the changefeed more frequently than the `30s` default, then you must set `min_checkpoint_frequency` to at least the desired resolved timestamp frequency. For example: {% include_cached copy-clipboard.html %} ~~~ sql