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 4f696b2cd [doc] Optimize useless message in dedicated-compaction
4f696b2cd is described below
commit 4f696b2cd67f6c6f570e0cbf1444aa008d53b424
Author: Jingsong <[email protected]>
AuthorDate: Mon May 13 21:10:19 2024 +0800
[doc] Optimize useless message in dedicated-compaction
---
docs/content/maintenance/dedicated-compaction.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/docs/content/maintenance/dedicated-compaction.md
b/docs/content/maintenance/dedicated-compaction.md
index f000849bf..ae975f4c9 100644
--- a/docs/content/maintenance/dedicated-compaction.md
+++ b/docs/content/maintenance/dedicated-compaction.md
@@ -45,10 +45,12 @@ streaming jobs to write records to a `'partial-update'`
table. Please refer to t
## Dedicated Compaction Job
-By default, Paimon writers will perform compaction as needed during writing
records. This is sufficient for most use cases, but there are two downsides:
+By default, Paimon writers will perform compaction as needed during writing
records. This is sufficient for most use cases.
-* This may result in unstable write throughput because throughput might
temporarily drop when performing a compaction.
-* Compaction will mark some data files as "deleted" (not really deleted, see
[expiring snapshots]({{< ref "maintenance/manage-snapshots#expiring-snapshots"
>}}) for more info). If multiple writers mark the same file, a conflict will
occur when committing the changes. Paimon will automatically resolve the
conflict, but this may result in job restarts.
+Compaction will mark some data files as "deleted" (not really deleted, see
+[expiring snapshots]({{< ref "maintenance/manage-snapshots#expiring-snapshots"
>}}) for more info).
+If multiple writers mark the same file, a conflict will occur when committing
the changes. Paimon will automatically
+resolve the conflict, but this may result in job restarts.
To avoid these downsides, users can also choose to skip compactions in
writers, and run a dedicated job only for compaction. As compactions are
performed only by the dedicated job, writers can continuously write records
without pausing and no conflicts will ever occur.
