This is an automated email from the ASF dual-hosted git repository.
lzljs3620320 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink-table-store.git
The following commit(s) were added to refs/heads/master by this push:
new 2d1da3d8 [FLINK-31291] Document table.exec.sink.upsert-materialize to
none to avoid strange behavior
2d1da3d8 is described below
commit 2d1da3d8780b46740a1962e118a2dbd780791480
Author: schnappi17 <[email protected]>
AuthorDate: Fri Mar 3 13:34:22 2023 +0800
[FLINK-31291] Document table.exec.sink.upsert-materialize to none to avoid
strange behavior
This closes #571
---
docs/content/docs/concepts/primary-key-table.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/docs/content/docs/concepts/primary-key-table.md
b/docs/content/docs/concepts/primary-key-table.md
index 5e6cd329..8005f303 100644
--- a/docs/content/docs/concepts/primary-key-table.md
+++ b/docs/content/docs/concepts/primary-key-table.md
@@ -179,3 +179,7 @@ CREATE TABLE MyTable (
{{< /tabs >}}
The record with the largest `sequence.field` value will be the last to merge,
regardless of the input order.
+
+{{< hint info >}}
+We recommend you set `sequence.field` to table to correct disorder. Set
`table.exec.sink.upsert-materialize` to `NONE` always to avoid any materialize
operator being added by Flink SQL, which may result in strange behavior.
+{{< /hint >}}
