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/paimon.git
The following commit(s) were added to refs/heads/master by this push:
new c783cded3 [doc] Document sequence.field supports fields of all data
types (#3682)
c783cded3 is described below
commit c783cded30d6a475dad7a887e9ede3aad825fe31
Author: Kerwin <[email protected]>
AuthorDate: Fri Jul 5 20:34:12 2024 +0800
[doc] Document sequence.field supports fields of all data types (#3682)
---
docs/content/primary-key-table/merge-engine.md | 4 ++--
docs/content/primary-key-table/sequence-rowkind.md | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/content/primary-key-table/merge-engine.md
b/docs/content/primary-key-table/merge-engine.md
index 32b897a00..2b52ac703 100644
--- a/docs/content/primary-key-table/merge-engine.md
+++ b/docs/content/primary-key-table/merge-engine.md
@@ -354,8 +354,8 @@ By specifying `'merge-engine' = 'first-row'`, users can
keep the first row of th
`deduplicate` merge engine that in the `first-row` merge engine, it will
generate insert only changelog.
{{< hint info >}}
-1. You can not specify `sequence.field`.
+1. You can not specify [sequence.field]({{< ref
"primary-key-table/sequence-rowkind#sequence-field" >}}).
2. Not accept `DELETE` and `UPDATE_BEFORE` message. You can config
`ignore-delete` to ignore these two kinds records.
- {{< /hint >}}
+{{< /hint >}}
This is of great help in replacing log deduplication in streaming computation.
diff --git a/docs/content/primary-key-table/sequence-rowkind.md
b/docs/content/primary-key-table/sequence-rowkind.md
index 61e2c01c8..236d44da9 100644
--- a/docs/content/primary-key-table/sequence-rowkind.md
+++ b/docs/content/primary-key-table/sequence-rowkind.md
@@ -50,7 +50,7 @@ CREATE TABLE my_table (
{{< /tabs >}}
The record with the largest `sequence.field` value will be the last to merge,
if the values are the same, the input
-order will be used to determine which one is the last one.
+order will be used to determine which one is the last one. `sequence.field`
supports fields of all data types.
You can define multiple fields for `sequence.field`, for example
`'update_time,flag'`, multiple fields will be compared in order.
