@clickzetta/cz-cli-darwin-arm64 0.3.95 → 0.3.100

package/bin/skills/lakehouse-doc-en/references/DataSource_MongoDB.md

@@ -0,0 +1,36 @@
+# MongoDB Data Source Configuration Guide
+
+## Overview
+
+MongoDB is a high-performance, highly available NoSQL database that offers rich data models and flexible query languages. By configuring a MongoDB data source, you can achieve data synchronization and integration with other systems.
+
+## Parameter Configuration
+
+When configuring a MongoDB data source, you need to provide the following information to ensure a successful connection to the database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your MongoDB data source.
+* **MongoDB Instance Type**: Choose your MongoDB instance type, which can be a single node, replica set, or sharded cluster.
+* **Service Address**: Provide the address of the MongoDB database node in the format `host:port`.
+* **Database Name**: Specify the name of the database to be synchronized.
+* **Replica Set Name** (if applicable): If it is a replica set instance, provide the name of the replica set.
+* **Read Preference** (if applicable): In a replica set instance, choose the read preference, such as `primary` or `secondary`.
+* **Username**: If authentication is required, provide the username used to connect to MongoDB.
+* **Password**: Provide the database password corresponding to the username.
+* **Authentication Database Name**: (optional) The name of the database used when creating the user, usually `admin`.
+* **Data Source Description**: (optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure that the connection information you enter is accessible on the public network. If the source has an IP access whitelist enabled, make sure the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to MongoDB via an SSH tunnel. Enable this option and provide the IP address and port of the SSH service. Ensure that your SSH client is properly configured and that you have permission to connect to the MongoDB server via SSH.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the MongoDB service is accessible.
+* Protect your database credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+After completing the configuration, you can select this MongoDB data source in data synchronization tasks to perform data import or export operations. Connecting via an SSH tunnel can enhance the security of data transmission, especially when handling sensitive data.

package/bin/skills/lakehouse-doc-en/references/DataSource_MySQL.md

@@ -0,0 +1,35 @@
+# MySQL Data Source Configuration Guide
+
+## Overview
+
+MySQL is a widely used open-source relational database management system. By configuring a MySQL data source, you can achieve efficient data synchronization and integration, supporting various data operations and analysis tasks.
+
+## Parameter Configuration
+
+When configuring a MySQL data source, you need to provide the following information to ensure a successful connection to the database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your data source, such as `MySQLSource01`.
+* **JDBC Connection URL**: Fill in the JDBC connection URL of the MySQL database, usually in the format `jdbc:mysql://host:port/dbname`. For example, if your database is on the `host` server, the port is `3306`, and the database name is `db01`, the URL would be `jdbc:mysql://host:3306/db01`.
+* **Username**: Enter the username used to connect to the MySQL database, such as `user01`.
+* **Password**: Provide the database password corresponding to the username, such as `password`.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+For connection configuration, you can choose one of the following two methods:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible over the public network. If the source has an IP access whitelist enabled, make sure the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to datasource via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number on which the SSH server is listening, usually `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the MySQL service is accessible.
+* Protect your database credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+After completing the configuration, you can select this MySQL data source in data synchronization tasks to perform data import or export operations.

package/bin/skills/lakehouse-doc-en/references/DataSource_OSS.md

@@ -0,0 +1,31 @@
+# OSS Data Source Configuration Guide
+
+## Overview
+
+OSS (Object Storage Service) is an object storage service provided by Alibaba Cloud, suitable for large-scale, high-reliability data storage needs. By configuring the OSS data source, you can achieve efficient data upload, download, and synchronization, supporting various data usage scenarios.
+
+## Parameter Configuration
+
+When configuring the OSS data source, you need to provide the following information to ensure a successful connection to the OSS service:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your OSS data source, such as `OSSDataSync`.
+* **Alibaba Cloud OSS Address**: Provide the Endpoint connection address for the OSS service. For example, `oss-cn-shanghai-internal.aliyuncs.com`.
+* **Alibaba Cloud accessKeyId**: The accessKeyId of your Alibaba Cloud account, used for authentication.
+* **Alibaba Cloud accessKeySecret**: The private access key corresponding to the accessKeyId.
+* **Alibaba Cloud OSS Bucket**: Specify the name of the OSS bucket to connect to, such as `my-oss-bucket`.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you need to pay attention to the following:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible on the public network. If the source end has enabled an IP access whitelist, make sure that the egress IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support. It also supports accessing via OSS intranet and public network Endpoints, and you can choose the access method based on the "Alibaba Cloud OSS Address" domain name address.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the OSS service is accessible.
+* Protect your credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the bucket structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any issues that may arise.
+
+After completing the configuration, you can select this OSS data source in data synchronization tasks to perform data import or export operations. Through the direct connection method, you can achieve fast data transmission and improve data processing efficiency.

package/bin/skills/lakehouse-doc-en/references/DataSource_Oracle.md

@@ -0,0 +1,35 @@
+# Oracle Data Source Configuration Guide
+
+## Overview
+
+Oracle Database is a widely used relational database management system (RDBMS) that offers powerful data management features and high-performance data processing capabilities. By configuring an Oracle data source, you can achieve data synchronization and integration with other systems, supporting complex data analysis and transaction processing.
+
+## Parameter Configuration
+
+When configuring an Oracle data source, you need to provide the following information to ensure a successful connection to the Oracle database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your Oracle data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the Oracle database, typically in the format `jdbc:oracle:thin:@host:port/SID` or `jdbc:oracle:thin:@host:port:service_name`. For example, `jdbc:oracle:thin:@oracle-host:1521/ORCL`.
+* **Username**: Enter the username used to connect to the Oracle database.
+* **Password**: Provide the database password corresponding to the username.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible over the public network. If the source has an IP access whitelist enabled, make sure the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to the Oracle database via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number that the SSH server listens on, usually `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the Oracle service is accessible.
+* Protect your database credentials and SSH credentials to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+Once the configuration is complete, you can select this Oracle data source in data synchronization tasks to perform data import or export operations. Connecting via an SSH tunnel can enhance the security of data transmission, especially when handling sensitive data. The direct connection method provides a more straightforward data transmission path.

package/bin/skills/lakehouse-doc-en/references/DataSource_PolarDB.md

@@ -0,0 +1,37 @@
+# PolarDB Data Source Configuration Guide
+
+## Overview
+
+PolarDB is a high-performance, scalable cloud-native relational database service provided by Alibaba Cloud. It is compatible with multiple database engines such as MySQL, PostgreSQL, and Oracle, offering high availability and elastic scaling capabilities. By configuring a PolarDB data source, you can achieve efficient data synchronization and analysis to meet enterprise-level data management requirements.
+
+## Parameter Configuration
+
+When configuring a PolarDB data source, the following information must be provided to ensure a successful connection to the PolarDB service:
+
+* **Data Source Name**: Specify a unique and easily identifiable name for your PolarDB data source.
+* **JDBC Connection Address**: Provide the JDBC connection address for the PolarDB instance, typically in the format `jdbc:engine_type://host:port/database`, for example `jdbc:mysql://polar-db-host:3306/mydatabase`.
+* **Username**: Enter the username for connecting to the PolarDB instance.
+* **Password**: Provide the database password corresponding to the username.
+* **Schema**: Specify the default Schema to connect to, such as `public` or another Schema you need to use.
+* **Allow Using Configuration Info to Connect to All Databases/Schemas**: Enable this option so that the configuration information can be used to connect to all databases and schemas in the PolarDB instance. If not enabled, the connection will be limited to the specified Schema.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of this data source.
+
+## Connection Configuration
+
+For connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure the connection information you enter is publicly accessible. If the source has IP access whitelisting enabled, make sure the data integration service's egress IP address has been added to the whitelist. Contact technical support for the specific IP address.
+* **Via SSH Tunnel**: To improve security, you can choose to connect to PolarDB through an SSH tunnel. Enable this option and provide the following SSH tunnel configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number the SSH server is listening on, typically `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure all provided connection information is accurate and the PolarDB service is accessible.
+* Protect your database credentials and SSH credentials to prevent disclosure to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly detect and resolve potential issues.
+
+After configuration is complete, you can select this PolarDB data source in data synchronization tasks for data import or export operations. Connecting via an SSH tunnel enhances the security of data transmission, especially when handling sensitive data. Checking the "Allow Using Configuration Info to Connect to All Databases/Schemas" option provides greater flexibility, but use it with caution to avoid security risks.

package/bin/skills/lakehouse-doc-en/references/DataSource_PorarDB.md

@@ -0,0 +1,37 @@
+# PolarDB Data Source Configuration Guide
+
+## Overview
+
+PolarDB is a high-performance, scalable cloud-native relational database service provided by Alibaba Cloud. It is compatible with multiple database engines such as MySQL, PostgreSQL, and Oracle, offering high availability and elastic scalability. By configuring the PolarDB data source, you can achieve efficient data synchronization and analysis, meeting enterprise-level data management needs.
+
+## Parameter Configuration
+
+When configuring the PolarDB data source, you need to provide the following information to ensure a successful connection to the PolarDB service:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your PolarDB data source.
+* **JDBC Connection Address**: Provide the JDBC connection address of the PolarDB instance, usually in the format `jdbc:engine_type://host:port/database`. For example, `jdbc:mysql://polar-db-host:3306/mydatabase`.
+* **Username**: Enter the username used to connect to the PolarDB instance.
+* **Password**: Provide the database password corresponding to the username.
+* **Schema**: Specify the default schema to connect to, such as `public` or any other schema you need to use.
+* **Allow using configuration information to connect to all databases/Schemas**: Enable this option to allow the configuration information to be used to connect to all databases and schemas in the PolarDB instance. If not enabled, the connection will be limited to the specified schema.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible over the public network. If the source has enabled an IP access whitelist, make sure the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to PolarDB via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number the SSH server is listening on, usually `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the PolarDB service is accessible.
+* Protect your database credentials and SSH credentials to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+Once the configuration is complete, you can select this PolarDB data source in data synchronization tasks to perform data import or export operations. Connecting via SSH tunnel can enhance the security of data transmission, especially when handling sensitive data. Enabling the "Allow using configuration information to connect to all databases/Schemas" option can provide greater flexibility, but use it with caution to avoid security risks.

package/bin/skills/lakehouse-doc-en/references/DataSource_PostgreSQL.md

@@ -0,0 +1,36 @@
+# PostgreSQL Data Source Configuration Guide
+
+## Overview
+
+PostgreSQL is a powerful open-source object-relational database system that provides advanced features such as complex queries, foreign keys, triggers, and views. By configuring a PostgreSQL data source, you can achieve data synchronization and integration with other systems, supporting various data analysis and reporting needs.
+
+## Parameter Configuration
+
+When configuring a PostgreSQL data source, you need to provide the following information to ensure a successful connection to the database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your PostgreSQL data source, such as `PGDataSourceExample`.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the PostgreSQL database, usually in the format `jdbc:postgresql://host:port/database`. For example, `jdbc:postgresql://postgres-server:5432/mydatabase`.
+* **Username**: Enter the username used to connect to the PostgreSQL database, such as `dbuser`.
+* **Password**: Provide the database password corresponding to the username, such as `dbpassword`.
+* **Schema**: Specify the default schema to connect to, such as `public`.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+Regarding connection configuration, you need to pay attention to the following:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible over the public network. If the source has an IP access whitelist enabled, make sure the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to datasource via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number on which the SSH server is listening, usually `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the PostgreSQL service is accessible.
+* Protect your database credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+Once the configuration is complete, you can select this PostgreSQL data source in data synchronization tasks to perform data import or export operations. Connecting via an SSH tunnel can enhance the security of data transmission, especially when handling sensitive data.

package/bin/skills/lakehouse-doc-en/references/DataSource_Redis.md

@@ -0,0 +1,55 @@
+# Redis Data Source Configuration Guide
+
+## Overview
+
+Redis is an open-source, in-memory key-value data storage system that supports multiple data structures such as strings, hashes, lists, sets, and sorted sets. It is widely used in caching, message queuing, and real-time analytics scenarios due to its high performance, low latency, and rich feature set. Configuring a Redis data source enables you to achieve efficient data reading and writing operations in data synchronization tasks.
+
+## Parameter Configuration
+
+When configuring a Redis data source, you need to provide the following information to ensure successful connection to the Redis service:
+
+* **Data Source Name**: Specify a unique and easily identifiable name for your Redis data source, for example, `BehavioralDataSource`.
+
+* **Authentication User**: Provide the username for connecting to the Redis service. If the Redis service has not enabled ACL (Access Control List) authentication or uses the default user, you can leave this field blank.
+
+* **Access Password**: Provide the connection password for the Redis service. If the Redis service is configured with password authentication (requirepass), please fill in the corresponding password. If no password is set, you can leave this field blank.
+
+* **Node Mode**: Select the deployment architecture mode for Redis. Currently supported:
+
+  * **Standalone**: Single-instance mode, suitable for single Redis instance scenarios
+  * **Cluster**: Cluster mode, suitable for Redis Cluster distributed clusters
+
+* **Node Information**: Provide the connection address information for the Redis service, including:
+
+  * **IP**: The IP address of the Redis server, for example, `10.10.10.1`
+  * **Port**: The port number of the Redis service, default is `6379`, the example uses `3306`
+  * Multiple node addresses can be configured via the "Add Node" button, suitable for cluster or master-slave architecture scenarios
+
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of this data source, such as "Production environment user behavior cache" or "Real-time session data storage".
+
+* **Authorize for Workspace Use**: Select the usage permission scope for this data source:
+
+  * **Specified Workspace**: Only authorized for use by specific workspaces
+  * **All Workspaces**: Authorized for use by all workspaces
+
+## Connection Configuration
+
+Regarding connection configuration, you need to pay attention to the following matters:
+
+* **Direct Connection**: Ensure that the connection information you enter is network-accessible. If the Redis service has IP access whitelist or firewall rules enabled, please ensure that the egress IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support personnel.
+* **Test Connectivity**: After completing the configuration, it is recommended to click the "Test Connectivity" button to verify the correctness of the connection configuration and ensure that the system can successfully connect to the Redis service.
+* **Network Connectivity Testing**: Before formal configuration, it is recommended to test network connectivity using `redis-cli` or telnet tool to confirm whether the port is open and the password is correct.
+
+## Notes
+
+* **Ensure all provided connection information is accurate**, and that the Redis service is accessible. Pay special attention to the correctness of IP addresses and port numbers.
+* **Data Type Support**: Redis supports multiple data structures (String, Hash, List, Set, Sorted Set, etc.). During data synchronization, it is necessary to clarify the data type mapping relationship between the source and target.
+* **Performance Considerations**: Redis is an in-memory data storage system. Large-scale data reading may affect Redis service performance. It is recommended to execute data synchronization tasks during off-peak business hours or use slave nodes for data reading.
+* **Protect your credential information** to avoid leakage to unauthorized personnel. It is recommended to regularly change passwords and follow strong password policies.
+* **Version Compatibility**: Confirm the compatibility between the Redis service version and the data integration platform. Redis 3.0 and above is recommended for better stability and feature support.
+* **Multi-node Configuration**: When configuring multiple nodes, the system will automatically handle connection logic according to the node mode. Please ensure all node information is accurate to avoid data synchronization anomalies.
+* **Regularly check and update your data source configuration** to adapt to architectural changes or new security requirements.
+* **Monitor the running status of data synchronization tasks** to promptly discover and resolve potential issues.
+* **Key Naming Convention**: It is recommended to clarify the naming pattern of Redis keys (such as prefix, separator, etc.) in data synchronization tasks to accurately identify and synchronize target data.
+
+After completing the configuration, you can select this Redis data source in data synchronization tasks to perform data import or export operations. Through direct connection and proper configuration, you can fully leverage Redis's high-performance characteristics to achieve fast data transmission and processing.

package/bin/skills/lakehouse-doc-en/references/DataSource_Redshift.md

@@ -0,0 +1,49 @@
+# Amazon Redshift Data Source Configuration Guide
+
+## Overview
+
+Amazon Redshift is a fully managed, petabyte-scale cloud data warehouse service that supports fast complex analysis on large datasets. By configuring the Amazon Redshift data source, you can achieve data synchronization and integration with other systems, leveraging Redshift's powerful capabilities for data warehousing and analytical needs.
+
+## Parameter Configuration
+
+To ensure a successful connection to Amazon Redshift, provide the following information when configuring the data source:
+
+1. **Data Source Name**: Specify a unique and easily recognizable name for your Redshift data source.
+2. **JDBC Address**: Provide the identifier of your Redshift cluster. Provide the JDBC connection address for Redshift, typically in the format `jdbc:redshift://endpoint:port/database`. For example, `jdbc:redshift://amazon-redshift-endpoint:5439/mydatabase`.
+3. **Username**: Provide the username with access to the Redshift database.
+4. **Password**: Provide the password for the specified database user.
+5. **Database Time Zone**: Fill in the server time zone setting of the database. By default, the server uses UTC (Coordinated Universal Time) as the time zone. If the server is in a different time zone, select the corresponding time zone here.
+6. **Data Source Description** (optional): Add descriptive information to help you or other administrators understand the purpose or characteristics of this data source.
+
+## Connection Configuration
+
+For connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure that the connection information you enter is accessible over the public network. If the source has enabled an IP access whitelist, ensure that the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to Aurora MySQL via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number on which the SSH server is listening, typically `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+When setting up the connection, consider the following:
+
+* **Security Group Configuration**: Ensure that the security group associated with your Redshift cluster allows inbound connections from the IP address of the system initiating the connection.
+
+## Notes
+
+* Ensure the security and stability of the AWS Redshift service by appropriately configuring IAM roles and policies.
+* Protect your database credentials to prevent unauthorized access.
+* Regularly review and rotate database credentials to maintain security.
+* When configuring, refer to the relevant AWS Redshift documentation and support resources to ensure accuracy.
+
+## Configuration Completion
+
+After configuration is complete, you can select this Amazon Redshift data source in data synchronization tasks to perform data import and export operations.
+
+* Use the "Test Connectivity" feature to verify whether the data source is accessible and whether the configuration information is correct.
+* After successful verification, you can continue to read or write data from the Redshift database according to the requirements of the data workflow.
+
+Please ensure that you have read and followed the above guidelines to successfully configure the AWS Redshift data source. If you need further assistance, refer to the relevant Amazon Redshift documentation or contact technical support.

package/bin/skills/lakehouse-doc-en/references/DataSource_RestApi.md

@@ -0,0 +1,30 @@
+# RestAPI Data Source Configuration Guide
+
+## Overview
+
+RestAPI is a widely used network architecture style that allows clients to interact with servers via the HTTP protocol. Configuring a RestAPI data source allows users to import or export data from Restful services, achieving data synchronization and integration.
+
+## Parameter Configuration
+
+1. **Data Source Name**: Specify a clear and unique name for the RestAPI data source for identification and management.
+2. **URL Address**: Enter the base URL of the Restful service, which is the root address of the API service and will be used for all data synchronization operations.
+3. **Request Method**: Select the HTTP request method used in the data synchronization task, which can be `GET` or `POST`.
+4. **Default Request Headers** (optional): Add any necessary HTTP request header information, organized in Key-Value format, such as `Content-Type`, with a default value of `application/json`.
+5. **Authentication Method**: Choose the authentication method required by the Restful service to ensure the security of data transmission.
+   * **No Authentication**: Select this option if the API service does not require authentication.
+   * **Basic Authentication** (BasicAuth): Select this option if the API service supports username and password authentication, and configure the corresponding username and password.
+   * **Bearer Token Authentication**: Select this option if the API service accepts Bearer Token authentication, and provide a valid Token name and value.
+6. **Data Source Description** (optional): Provide descriptive information about the data source to help understand its purpose and characteristics.
+
+## Connection Test
+
+* **Test Connectivity**: Before saving the configuration, you can click the "Test Connectivity" button to verify the correctness and accessibility of the API service address. This step only checks the reachability of the URL address and does not perform authentication verification.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the Restful service is accessible.
+* Configure request headers and authentication methods according to the requirements of the Restful service to ensure the security and effectiveness of data transmission.
+* Protect your authentication information to avoid leakage to unauthorized personnel.
+* Comply with the API usage terms of the Restful service, use the request frequency reasonably, and avoid abuse.
+
+After completing the above configuration, you can select this RestAPI data source for data synchronization task development. When configuring the RestAPI data source, refer to the relevant Restful service's API documentation and support resources for the most accurate guidance. Correctly configuring the authentication method is crucial for protecting data security and ensuring the smooth progress of data synchronization.

package/bin/skills/lakehouse-doc-en/references/DataSource_S3.md

@@ -0,0 +1,25 @@
+# S3 Data Source Configuration Guide
+
+## Overview
+
+Amazon S3 (Simple Storage Service) is a scalable object storage service provided by Amazon. Configuring an S3 data source allows you to efficiently integrate and synchronize data with other systems, supporting various data management and analysis tasks.
+
+## Parameter Configuration
+
+When configuring an S3 data source, you need to provide the following information to ensure a successful connection to the S3 bucket:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your S3 data source.
+* **Region**: Specify the AWS region where the S3 bucket is located.
+* **Bucket**: Enter the name of the S3 bucket you want to connect to.
+* **Access Key ID**: Provide the AWS access key ID used for authentication.
+* **Access Key Secret**: Provide the secret access key corresponding to the access key ID.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the S3 service is accessible.
+* Protect your AWS credentials to prevent unauthorized access to your S3 resources.
+* Regularly review and update your data source configuration to accommodate changes in data structure or new security requirements.
+* Monitor the status of data synchronization tasks to promptly address any issues that may arise.
+
+Once the configuration is complete, you can use this S3 data source for data import or export operations in data synchronization tasks.

package/bin/skills/lakehouse-doc-en/references/DataSource_SLS.md

@@ -0,0 +1,31 @@
+# SLS(LogHub) Data Source Configuration Guide
+
+## Overview
+
+SLS (Log Service), also known as LogHub, is a real-time log service provided by Alibaba Cloud for the collection, storage, query, and analysis of log data. Configuring an SLS data source can make your data synchronization and analysis work more efficient, especially suitable for handling large-scale log data.
+
+## Parameter Configuration
+
+When configuring an SLS data source, you need to provide the following information to ensure a successful connection to the SLS service:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your SLS data source, such as `MySLSDataSource`.
+* **Project**: Provide the SLS project name, which is the project identifier you set in the SLS console.
+* **Alibaba Cloud SLS Service Address**: Fill in the Endpoint connection address of the SLS service, usually the SLS service address in your region.
+* **Alibaba Cloud accessKeyId**: Provide the Access Key ID of your Alibaba Cloud account for authentication.
+* **Alibaba Cloud accessKeySecret**: Provide the Access Key Secret corresponding to the Access Key ID for authentication.
+* **Data Source Description (Optional)**: Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you need to pay attention to the following matters:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible on the public network. If the source end has enabled an IP access whitelist, make sure that the outbound IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support personnel.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the SLS service is accessible.
+* Protect your credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in project structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly discover and resolve any potential issues.
+
+After the configuration is complete, you can select this SLS data source in data synchronization tasks to perform log data import or export operations. Through the direct connection method, you can achieve fast log data transmission and improve log processing efficiency.

package/bin/skills/lakehouse-doc-en/references/DataSource_StarRocks.md

@@ -0,0 +1,35 @@
+# StarRocks Data Source Configuration Guide
+
+## Overview
+
+StarRocks is a high-performance, real-time analytical distributed relational database that provides low-latency data queries and high-concurrency data ingestion capabilities. By configuring the StarRocks data source, you can achieve rapid analysis and real-time processing of large data sets, meeting complex business analysis needs.
+
+## Parameter Configuration
+
+When configuring the StarRocks data source, you need to provide the following information to ensure a successful connection to the StarRocks cluster:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your StarRocks data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL of the StarRocks cluster, usually in the format `jdbc:starrocks://host:port/database`. For example, `jdbc:starrocks://sr-host:8030/mydatabase`.
+* **Username**: Enter the username used to connect to the StarRocks cluster.
+* **Password**: Provide the database password corresponding to the username.
+* **Data Source Description**: (Optional) Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure that the connection information you enter is accessible over the public network. If the source end has enabled an IP access whitelist, make sure the egress IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to StarRocks via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number on which the SSH server is listening, usually `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the StarRocks service is accessible.
+* Protect your database credentials and SSH credentials to prevent them from being disclosed to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+Once the configuration is complete, you can select this StarRocks data source in data synchronization tasks to perform data import or export operations. Connecting via an SSH tunnel can enhance the security of data transmission, especially when handling sensitive data.

package/bin/skills/lakehouse-doc-en/references/DataSource_TiDB.md

@@ -0,0 +1,36 @@
+# TiDB Data Source Configuration Guide
+
+## Overview
+
+TiDB is an open-source distributed relational database that supports horizontal scaling and strong consistency, suitable for building Hybrid Transactional and Analytical Processing (HTAP) applications. By configuring the TiDB data source, you can achieve efficient data synchronization and real-time analysis to meet the needs of various business scenarios.
+
+## Parameter Configuration
+
+When configuring the TiDB data source, you need to provide the following information to ensure a successful connection to the TiDB cluster:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your TiDB data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL of the TiDB cluster, usually in the format `jdbc:tidb://host:port/database`. For example, `jdbc:tidb://tidb-server:4000/mypd`.
+* **Username**: Enter the username used to connect to the TiDB cluster.
+* **Password**: Provide the database password corresponding to the username.
+* **Allow using configuration information to connect to all databases/Schemas** (optional): Check this option to allow the configuration information to be used to connect to all databases and schemas in the TiDB cluster. If unchecked, the connection will be limited to the specified schema.
+* **Data Source Description** (optional): Add descriptive information for the data source to help you or other administrators understand the purpose or characteristics of the data source.
+
+## Connection Configuration
+
+In terms of connection configuration, you can choose one of the following connection methods:
+
+* **Direct Connection**: Ensure that the connection information you entered is accessible over the public network. If the source has an IP access whitelist enabled, make sure the egress IP address of the data integration service has been added to the whitelist. For specific IP addresses, please contact technical support.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to TiDB via an SSH tunnel. Enable this option and provide the following SSH tunnel-related configuration information:
+  * **SSH Server Address**: Provide the IP address or domain name of the SSH server.
+  * **SSH Port**: Specify the port number on which the SSH server is listening, usually `22`.
+  * **Username**: Provide the login username for the SSH server.
+  * **Password**: Provide the password corresponding to the SSH server login username.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the TiDB service is accessible.
+* Protect your database credentials and SSH credentials to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the database structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+Once the configuration is complete, you can select this TiDB data source in data synchronization tasks to perform data import or export operations. Connecting via an SSH tunnel can enhance the security of data transmission, especially when handling sensitive data. Checking the "Allow using configuration information to connect to all databases/Schemas" option can provide greater flexibility, but use it with caution to avoid security risks.

package/bin/skills/lakehouse-doc-en/references/DataSupplementationTask.md

@@ -0,0 +1,51 @@
+# Data Supplementation Task
+
+Data supplementation can be achieved by filling in historical or future data for a certain period, writing the data into the corresponding time partition. If there are scheduling parameters configured in the code, they will be automatically replaced with specific values based on the business time selected for data supplementation, and the corresponding time data will be written into the specified partition according to the business code logic.
+
+## Usage Scenarios
+
+When a new task is created and historical data needs to be processed, the data supplementation function can be used to select a certain period of history to execute the task.
+
+When there is a problem with the data or the task is abnormal during a certain period, data supplementation can be used to regenerate instances for the abnormal historical data or tasks and execute them again, achieving the purpose of repairing historical data.
+
+## Product Operation
+
+###  Step One: Create a Data Supplementation Task
+
+Click on the left navigation to Operations Monitoring -> Task Operations, select the Periodic Task tab. Then, choose any periodic task in management and click on the operation - Data Supplementation to enter the data supplementation operation interface.
+
+Configure the corresponding operations for the data supplementation task.
+
+Task Name: The system provides a default name, which is not currently supported for user input.
+
+Select the task nodes included in the data supplementation task.
+
+Include Current Node: Users can choose whether to check the current task to participate in data supplementation according to actual needs.
+
+Include Downstream Nodes: Users can check the downstream tasks that need data supplementation according to actual needs, supporting three options: not choosing, choosing all, and customizing the range of selection.
+
+Task Timing Time Range: When creating a data supplementation task, you can add multiple planned execution time ranges to address scenarios where you want to supplement data for multiple discontinuous periods. Currently, up to 4 planned execution time ranges are supported. Users are not allowed to select overlapping times.
+
+Concurrency Settings: Indicates that when supplementing data for multiple periods in a row, if the concurrency is met, multiple instances of the period can run simultaneously, which can improve the efficiency of data supplementation, but will also consume more resources.
+
+After enabling concurrent execution, the system will default to attach self-dependencies to task instances assigned to the same concurrency group.
+
+###  Step Two: View Data Supplementation Tasks
+
+Click on the left navigation to Operations Monitoring -> Task Operations, and select the Data Supplementation Task tab.
+
+Basic Information: Includes concurrency grouping, target task ID, task name, workspace, whether to include downstream, status, execution order, task timing time range, submission time, submitter, etc.
+
+Statistics Graph:
+
+Global Statistical Information: You can see the total number of all times included in the current data supplementation task, and the execution status is given based on a daily granularity.
+
+Granularity Effect Diagram: Provides statistical data in three granularities of year/month/day, and clicking on the statistical graph will link to the instance list below.
+
+Year View: Hovering the mouse over the date will show the execution status of that day;
+
+Month View: You can see the total number of instances to be executed on that day in the month view, and hovering over the calendar will show a summary of the execution status;
+
+Day View: Supports switching between two granularities of day/1 hour, and you can see the average duration of instances under different aggregation granularities.
+
+Instance Statistics List: By default, it displays information about all executed instances under the current data supplementation task according to the planned time. Clicking on it will jump to the instance execution details page to view dependency and other details.

package/bin/skills/lakehouse-doc-en/references/Data_Catalog_Management.md

@@ -0,0 +1 @@
+^