This is an automated email from the ASF dual-hosted git repository.
RocMarshal pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new 1a45ad8ba3c [hotfix][docs] Remove inconsistent parameter descriptions.
(#28767)
1a45ad8ba3c is described below
commit 1a45ad8ba3c40f8b390e98e9ced5b433cba2a7c4
Author: Yuepeng Pan <[email protected]>
AuthorDate: Wed Jul 22 20:19:42 2026 +0800
[hotfix][docs] Remove inconsistent parameter descriptions. (#28767)
---
docs/content.zh/release-notes/flink-2.3.md | 8 +-------
docs/content/release-notes/flink-2.3.md | 8 +-------
2 files changed, 2 insertions(+), 14 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..06635d5f6f9 100644
--- a/docs/content.zh/release-notes/flink-2.3.md
+++ b/docs/content.zh/release-notes/flink-2.3.md
@@ -90,17 +90,11 @@ CREATE FUNCTION my_func AS 'com.example.MyUdf'
Flink 2.3 reworks how `SinkUpsertMaterializer` handles the case where a
query's upsert key
differs from the sink's primary key. Previously this required maintaining the
full history of
-records and could blow up state. Two changes address this:
+records and could blow up state. An enhancement allows you to manage this
situation:
- 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..06635d5f6f9 100644
--- a/docs/content/release-notes/flink-2.3.md
+++ b/docs/content/release-notes/flink-2.3.md
@@ -90,17 +90,11 @@ CREATE FUNCTION my_func AS 'com.example.MyUdf'
Flink 2.3 reworks how `SinkUpsertMaterializer` handles the case where a
query's upsert key
differs from the sink's primary key. Previously this required maintaining the
full history of
-records and could blow up state. Two changes address this:
+records and could blow up state. An enhancement allows you to manage this
situation:
- 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
