This is an automated email from the ASF dual-hosted git repository.

wanghailin pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/seatunnel.git


The following commit(s) were added to refs/heads/dev by this push:
     new b7b92bc793 [Doc][Improve] Remove unnecessary commas to make sentences 
smoother (#6783)
b7b92bc793 is described below

commit b7b92bc79333f524c4b2afd6de682ab3fcc93473
Author: ponxu <[email protected]>
AuthorDate: Mon May 6 23:14:23 2024 +0800

    [Doc][Improve] Remove unnecessary commas to make sentences smoother (#6783)
---
 docs/en/seatunnel-engine/deployment.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/seatunnel-engine/deployment.md 
b/docs/en/seatunnel-engine/deployment.md
index 412add286a..88df18b14c 100644
--- a/docs/en/seatunnel-engine/deployment.md
+++ b/docs/en/seatunnel-engine/deployment.md
@@ -95,7 +95,7 @@ About the checkpoint storage, you can see [checkpoint 
storage](checkpoint-storag
 
 ### 4.4 Historical Job expiration Config
 
-The information about each completed Job, such as status, counters, and error 
logs, is stored in the IMap object. As the number of running jobs increases, 
the memory increases and eventually the memory will overflow. Therefore, you 
can adjust the history-job-expire-minutes parameter to solve this problem. The 
time unit of this parameter is minute. The default value is 1440 minutes, that 
is, one day.
+The information about each completed Job, such as status, counters, and error 
logs, is stored in the IMap object. As the number of running jobs increases, 
the memory increases and eventually the memory will overflow. Therefore, you 
can adjust the history-job-expire-minutes parameter to solve this problem. The 
time unit of this parameter is minute. The default value is 1440 minutes, that 
is one day.
 
 Example
 

Reply via email to