Skip to content

[hotfix][docs] Remove inconsistent parameter descriptions. #28767

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RocMarshal merged 3 commits into from
Jul 22, 2026
+2 −14
Merged

[hotfix][docs] Remove inconsistent parameter descriptions. #28767

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f5b46c3
[hotfix][docs] Remove inconsistent parameter descriptions.
RocMarshal Jul 17, 2026
bd69d0c
Update docs/content/release-notes/flink-2.3.md
RocMarshal Jul 22, 2026
eee43dc
Update docs/content.zh/release-notes/flink-2.3.md
RocMarshal Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions docs/content.zh/release-notes/flink-2.3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. A change partially addressed this issue:
Comment thread
RocMarshal marked this conversation as resolved.
Outdated

- 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

Expand Down
8 changes: 1 addition & 7 deletions docs/content/release-notes/flink-2.3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. A change partially addressed this issue:
Comment thread
RocMarshal marked this conversation as resolved.
Outdated
Comment thread
RocMarshal marked this conversation as resolved.
Outdated

- 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

Expand Down