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/incubator-paimon.git
The following commit(s) were added to refs/heads/master by this push:
new 0a9c434a0 [doc] Add a description explaining that DELETE needs to be
run in the batch mode (#1439)
0a9c434a0 is described below
commit 0a9c434a070f84a5173d651e3e50562bee1626db
Author: Congxian Qiu <[email protected]>
AuthorDate: Tue Jun 27 15:59:20 2023 +0800
[doc] Add a description explaining that DELETE needs to be run in the batch
mode (#1439)
---
docs/content/concepts/file-operations.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/content/concepts/file-operations.md
b/docs/content/concepts/file-operations.md
index 19af3187e..58696d836 100644
--- a/docs/content/concepts/file-operations.md
+++ b/docs/content/concepts/file-operations.md
@@ -204,6 +204,7 @@ The new file layout as of snapshot-2 looks like
Now let's delete records that meet the condition `dt>=20230503`.
In Flink SQL, execute the following statement:
+{{< label Batch >}}
```sql
DELETE FROM T WHERE dt >= '20230503';
```
@@ -239,11 +240,10 @@ As you may have noticed, the number of small files will
augment over successive
snapshots, which may lead to decreased read performance. Therefore, a
full-compaction
is needed in order to reduce the number of small files.
-Let's trigger the full-compaction now. Make sure you have set execution mode
to `batch`
-(add an entry `execution.runtime-mode: batch` in `flink-conf.yaml`) and run a
-dedicated compaction job through `flink run`:
+Let's trigger the full-compaction now, and run a dedicated compaction job
through `flink run`:
-```bash
+{{< label Batch >}}
+```bash
<FLINK_HOME>/bin/flink run \
/path/to/paimon-flink-action-{{< version >}}.jar \
compact \
@@ -378,4 +378,4 @@ about previous files and merged files so that `Committer
Operator` can construct
`Committer Operator` might produce two snapshot during Flink checkpoint, one
for data written (snapshot of kind `Append`) and the
other for compact (snapshot of kind `Compact`). If no data file is written
during checkpoint interval, only snapshot of kind `Compact`
will be created. `Committer Operator` will check against snapshot expiration
and perform
-physical deletion of marked data files.
\ No newline at end of file
+physical deletion of marked data files.
