This is an automated email from the ASF dual-hosted git repository.

RocMarshal pushed a commit to branch hotfix_0717_01
in repository https://gitbox.apache.org/repos/asf/flink.git

commit 807bf84d99d670916ecd9c8918c36c048e6135ca
Author: Yuepeng Pan <[email protected]>
AuthorDate: Fri Jul 17 19:52:25 2026 +0800

    [hotfix][docs] Remove inconsistent parameter descriptions.
---
 docs/content.zh/release-notes/flink-2.3.md | 6 ------
 docs/content/release-notes/flink-2.3.md    | 6 ------
 2 files changed, 12 deletions(-)

diff --git a/docs/content.zh/release-notes/flink-2.3.md 
b/docs/content.zh/release-notes/flink-2.3.md
index 8ddc99dbd92..d07733002b0 100644
--- a/docs/content.zh/release-notes/flink-2.3.md
+++ b/docs/content.zh/release-notes/flink-2.3.md
@@ -95,12 +95,6 @@ records and could blow up state. Two changes address this:
 - A new `ON CONFLICT` clause with `DO NOTHING`, `DO ERROR` and `DO 
DEDUPLICATE` strategies makes
   the behavior on key conflict explicit. By default, planning now fails when 
the upsert and
   primary keys differ, requiring the user to choose a conflict strategy.
-- Watermark-based record compaction is introduced to fix internal changelog 
disorder. The
-  trigger and frequency of compaction are controlled by:
-  - `table.exec.sink.upserts.compaction-mode` (default: `WATERMARK`) — 
`WATERMARK` or
-    `CHECKPOINT`.
-  - `table.exec.sink.upserts.compaction-interval` — optional fallback interval 
for emitting
-    watermarks when none arrive naturally.
 
 #### Process Table Function enhancements
 
diff --git a/docs/content/release-notes/flink-2.3.md 
b/docs/content/release-notes/flink-2.3.md
index 8ddc99dbd92..d07733002b0 100644
--- a/docs/content/release-notes/flink-2.3.md
+++ b/docs/content/release-notes/flink-2.3.md
@@ -95,12 +95,6 @@ records and could blow up state. Two changes address this:
 - A new `ON CONFLICT` clause with `DO NOTHING`, `DO ERROR` and `DO 
DEDUPLICATE` strategies makes
   the behavior on key conflict explicit. By default, planning now fails when 
the upsert and
   primary keys differ, requiring the user to choose a conflict strategy.
-- Watermark-based record compaction is introduced to fix internal changelog 
disorder. The
-  trigger and frequency of compaction are controlled by:
-  - `table.exec.sink.upserts.compaction-mode` (default: `WATERMARK`) — 
`WATERMARK` or
-    `CHECKPOINT`.
-  - `table.exec.sink.upserts.compaction-interval` — optional fallback interval 
for emitting
-    watermarks when none arrive naturally.
 
 #### Process Table Function enhancements
 

Reply via email to