This is an automated email from the ASF dual-hosted git repository.
junhao 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 71c1122e64 [doc] not recommended to use asynchronous expiration in
batch mode (#5464)
71c1122e64 is described below
commit 71c1122e64ed47d19d1f9ff84119afdd15c580f5
Author: LsomeYeah <[email protected]>
AuthorDate: Mon Apr 14 17:42:23 2025 +0800
[doc] not recommended to use asynchronous expiration in batch mode (#5464)
---
docs/content/maintenance/manage-snapshots.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/docs/content/maintenance/manage-snapshots.md
b/docs/content/maintenance/manage-snapshots.md
index dc3d32602a..2d4299520e 100644
--- a/docs/content/maintenance/manage-snapshots.md
+++ b/docs/content/maintenance/manage-snapshots.md
@@ -224,7 +224,9 @@ Please note that too short retain time or too small retain
number may result in:
By default, paimon will delete expired snapshots synchronously. When there are
too
many files that need to be deleted, they may not be deleted quickly and
back-pressured
to the upstream operator. To avoid this situation, users can use asynchronous
expiration
-mode by setting `snapshot.expire.execution-mode` to `async`.
+mode by setting `snapshot.expire.execution-mode` to `async`. However, if your
job runs in
+batch mode, it is not recommended to use asynchronous expiration mode, as the
expire task
+may fail to complete successfully.
## Rollback to Snapshot
