Add release docs 2.3.7

i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.7/about.md

@@ -32,7 +32,7 @@ SeaTunnel专注于数据集成和数据同步，主要旨在解决数据集成
 
 ## SeaTunnel 工作流图
 
-![SeaTunnel Work Flowchart](/image_zh/architecture_diagram.png)
+![SeaTunnel Work Flowchart](images/architecture_diagram.png)
 
 SeaTunnel的运行流程如上图所示。
 
@@ -60,7 +60,7 @@ SeaTunnel 拥有大量用户。 您可以在[用户](https://seatunnel.apache.or
 
 <p align="center">
 <br/><br/>
-<img src="https://landscape.cncf.io//image_zh/left-logo.svg" width="150" alt=""/>&nbsp;&nbsp;<img src="https://landscape.cncf.io//image_zh/right-logo.svg" width="200" alt=""/>
+<img src="https://landscape.cncf.io/images/left-logo.svg" width="150" alt=""/>&nbsp;&nbsp;<img src="https://landscape.cncf.io/images/right-logo.svg" width="200" alt=""/>
 <br/><br/>
 SeaTunnel 丰富了<a href="https://landscape.cncf.io/card-mode?category=streaming-messaging&license=apache-license-2-0&grouping=category&selected=sea-tunnal">CNCF 云原生景观</a >。
 </p >

i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.7/faq.md

@@ -65,9 +65,9 @@ your string 1
 
 当然！ 请参阅下面的屏幕截图：
 
-![工作流程.png](/image_zh/workflow.png)
+![工作流程.png](images/workflow.png)
 
-![azkaban.png](/image_zh/azkaban.png)
+![azkaban.png](images/azkaban.png)
 
 ## SeaTunnel是否有配置多个源的情况，例如同时在源中配置elasticsearch和hdfs？
 
@@ -185,7 +185,7 @@ sink {
 
 3、一般来说，M和N都确定了，从2可以得出结论：`spark.streaming.kafka.maxRatePerPartition`的大小与`spark.executor.cores` * `spark的大小正相关 .executor.instances`，可以在增加资源`maxRatePerPartition`的同时增加，以加快消耗。
 
-![Kafka](/image_zh/kafka.png)
+![Kafka](images/kafka.png)
 
 ## 如何解决错误 `Exception in thread "main" java.lang.NoSuchFieldError: INSTANCE`？
 

i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.7/seatunnel-engine/resource-isolation.md

@@ -79,5 +79,5 @@ sink {
 - 当在任务的配置中, 没有添加`tag_filter`时, 会从所有节点中随机选择节点来运行任务.
 - 当`tag_filter`中存在多个过滤条件时, 会根据key存在以及value相等的全部匹配的节点, 当没有找到匹配的节点时, 会抛出 `NoEnoughResourceException`异常.
 
-![img.png](/image_zh/resource-isolation.png)
+![img.png](images/resource-isolation.png)
 

tools/build-docs.ts

@@ -13,6 +13,7 @@ import {
   PROJECT_IMG_DIR,
   PROJECT_SITE_ZH_IMG_DIR,
   PROJECT_DOC_DIR,
+  PROJECT_SITE_DOC_IMG_DIR,
   PROJECT_ZH_DOC_DIR,
   PROJECT_SITE_ZH_DOC_DIR,
   replaceImagesPath,
@@ -76,10 +77,10 @@ function prepareDocs() {
   console.log(`===>>>: Rsync sidebars.js to ${DOCUSAURUS_DOC_SIDEBARS_FILE}`);
   fs.copyFileSync(PROJECT_SIDEBAR_PATH, DOCUSAURUS_DOC_SIDEBARS_FILE);
 
-  console.log(`===>>>: Rsync images to ${PROJECT_SITE_IMG_DIR}`);
+  console.log(`===>>>: Rsync en images to ${PROJECT_SITE_IMG_DIR}`);
   copySync(PROJECT_IMG_DIR, PROJECT_SITE_IMG_DIR, {});
 
-  console.log(`===>>>: Rsync images to ${PROJECT_SITE_ZH_IMG_DIR}`);
+  console.log(`===>>>: Rsync zh images to ${PROJECT_SITE_ZH_IMG_DIR}`);
   copySync(PROJECT_IMG_DIR, PROJECT_SITE_ZH_IMG_DIR, {});
 
   console.log(
@@ -89,7 +90,10 @@ function prepareDocs() {
     filter: (src) => !src.endsWith("images"),
   });
 
-  console.log(`===>>>: Rsync zh documents to ${PROJECT_ZH_DOC_DIR}`);
+  console.log(`===>>>: Rsync images to ${PROJECT_SITE_DOC_IMG_DIR}`);
+  copySync(PROJECT_IMG_DIR, PROJECT_SITE_DOC_IMG_DIR, {});
+
+  console.log(`===>>>: Rsync zh documents to ${PROJECT_SITE_ZH_DOC_DIR}`);
   copySync(PROJECT_ZH_DOC_DIR, PROJECT_SITE_ZH_DOC_DIR, {
     filter: (src) => !src.endsWith("images"),
   });

tools/common.ts

@@ -25,6 +25,7 @@ export const PROJECT_SITE_ZH_IMG_DIR = path.resolve(
   "image_zh"
 );
 export const PROJECT_SITE_DOC_DIR = path.resolve(SOURCE_PATH, "docs");
+export const PROJECT_SITE_DOC_IMG_DIR = path.resolve(SOURCE_PATH, "docs", "images");
 export const PROJECT_SITE_ZH_DOC_DIR = path.resolve(
   SOURCE_PATH,
   "i18n",

tools/version.ts

@@ -49,7 +49,6 @@ async function main() {
   });
   stepTwo.stderr.on("data", (data) => {
     console.error(color.red(`syncerr: ${data}`));
-    process.exit(1);
   });
   await stepTwo;
 
@@ -62,7 +61,6 @@ async function main() {
   });
   stepThree.stderr.on("data", (data) => {
     console.error(color.red(`syncerr: ${data}`));
-    process.exit(1);
   });
   await stepThree;
 

versioned_docs/version-2.3.7/about.md

@@ -34,7 +34,7 @@ SeaTunnel focuses on data integration and data synchronization, and is mainly de
 
 ## SeaTunnel Work Flowchart
 
-![SeaTunnel Work Flowchart](/image_en/architecture_diagram.png)
+![SeaTunnel Work Flowchart](images/architecture_diagram.png)
 
 The runtime process of SeaTunnel is shown in the figure above.
 
@@ -62,7 +62,7 @@ SeaTunnel has lots of users. You can find more information about them in [Users]
 
 <p align="center">
 <br/><br/>
-<img src="https://landscape.cncf.io//image_en/left-logo.svg" width="150" alt=""/>&nbsp;&nbsp;<img src="https://landscape.cncf.io//image_en/right-logo.svg" width="200" alt=""/>
+<img src="https://landscape.cncf.io/images/left-logo.svg" width="150" alt=""/>&nbsp;&nbsp;<img src="https://landscape.cncf.io/images/right-logo.svg" width="200" alt=""/>
 <br/><br/>
 SeaTunnel enriches the <a href="https://landscape.cncf.io/card-mode?category=streaming-messaging&license=apache-license-2-0&grouping=category&selected=sea-tunnal">CNCF CLOUD NATIVE Landscape</a >.
 </p >

versioned_docs/version-2.3.7/faq.md

@@ -65,9 +65,9 @@ Refer to: [lightbend/config#456](https://github.com/lightbend/config/issues/456)
 
 Of course! See the screenshot below:
 
-![workflow.png](/image_en/workflow.png)
+![workflow.png](images/workflow.png)
 
-![azkaban.png](/image_en/azkaban.png)
+![azkaban.png](images/azkaban.png)
 
 ## Does SeaTunnel have a case for configuring multiple sources, such as configuring elasticsearch and hdfs in source at the same time?
 
@@ -184,7 +184,7 @@ The following conclusions can be drawn:
 
 3. In general, both M and N are determined, and the conclusion can be drawn from 2: The size of `spark.streaming.kafka.maxRatePerPartition` is positively correlated with the size of `spark.executor.cores` * `spark.executor.instances`, and it can be increased while increasing the resource `maxRatePerPartition` to speed up consumption.
 
-![Kafka](/image_en/kafka.png)
+![Kafka](images/kafka.png)
 
 ## How can I solve the Error `Exception in thread "main" java.lang.NoSuchFieldError: INSTANCE`?
 

versioned_docs/version-2.3.7/seatunnel-engine/engine-jar-storage-mode.md

@@ -15,7 +15,7 @@ We are committed to ongoing efforts to enhance and stabilize this functionality,
 We can enable the optimization job submission process, which is configured in the `seatunel.yaml`. After enabling the optimization of the Seatunnel job submission process configuration item,
 users can use the Seatunnel engine(Zeta) as the execution engine without placing the connector jar packages required for task execution or the third-party jar packages that the connector relies on in each engine `connector` directory.
 Users only need to place all the jar packages for task execution on the client that submits the job, and the client will automatically upload the jars required for task execution to the Zeta engine. It is necessary to enable this configuration item when submitting jobs in Docker or k8s mode,
-which can fundamentally solve the problem of large container /image_en caused by the heavy weight of the Seatunnel Zeta engine. In the image, only the core framework package of the Zeta engine needs to be provided,
+which can fundamentally solve the problem of large container images caused by the heavy weight of the Seatunnel Zeta engine. In the image, only the core framework package of the Zeta engine needs to be provided,
 and then the jar package of the connector and the third-party jar package that the connector relies on can be separately uploaded to the pod for distribution.
 
 After enabling the optimization job submission process configuration item, you do not need to place the following two types of jar packages in the Zeta engine:

versioned_docs/version-2.3.7/seatunnel-engine/resource-isolation.md

@@ -79,5 +79,5 @@ sink {
 - If not set `tag_filter` in job config, it will random choose the node in all active nodes.
 - When you add multiple tag in `tag_filter`, it need all key exist and value match. if all node not match, you will get `NoEnoughResourceException` exception.
 
-![img.png](/image_en/resource-isolation.png)
+![img.png](images/resource-isolation.png)