@clickzetta/cz-cli-darwin-x64 0.3.94 → 0.3.96

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

@@ -0,0 +1,36 @@
+# ClickHouse Data Source Configuration Guide
+
+## Overview
+
+ClickHouse is an open-source columnar database management system that supports efficient data analysis using SQL and can quickly generate reports. By configuring the ClickHouse data source, you can achieve fast data import, export, and analysis.
+
+## Parameter Configuration
+
+When configuring the ClickHouse 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 ClickHouse data source, such as `ClickHouseSource01`.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the ClickHouse database, in the format `jdbc:clickhouse://host:port/`. For example, `jdbc:clickhouse://host01:8123/`.
+* **Username**: Enter the username used to connect to the ClickHouse database, such as `user01`.
+* **Password**: Provide the database password corresponding to the username, such as `password`.
+* **Schema**: Specify the default database to connect to, such as `default`.
+* **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 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 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 ClickHouse service is accessible.
+* Protect your database 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.
+
+After completing the configuration, you can select this ClickHouse 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_DB2.md

@@ -0,0 +1,36 @@
+# DB2 Data Source Configuration Guide
+
+## Overview
+
+DB2 is a relational database management system developed by IBM, known for its high performance, high reliability, and powerful data processing capabilities. By configuring a DB2 data source, you can achieve data synchronization and integration with other systems, supporting complex data analysis and transaction processing.
+
+## Parameter Configuration
+
+When configuring a DB2 data source, you need to provide the following information to ensure a successful connection to the DB2 database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your DB2 data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the DB2 database, usually in the format `jdbc:db2://host:port/database`. For example, `jdbc:db2://db2-host:50000/mydatabase`.
+* **Username**: Enter the username used to connect to the DB2 database.
+* **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.
+* **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 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 DB2 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 DB2 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 DB2 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_DM.md

@@ -0,0 +1,35 @@
+# DM Data Source Configuration Guide
+
+## Overview
+
+DM Database (DM) is a domestically produced relational database management system that offers high security, high reliability, and high performance data processing capabilities. By configuring the DM database data source, you can achieve data synchronization and integration with other systems, supporting enterprise-level data management and analysis needs.
+
+## Parameter Configuration
+
+When configuring the DM database data source, you need to provide the following information to ensure a successful connection to the DM database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your DM database data source.
+* **JDBC Connection Address**: Provide the JDBC connection address of the DM database, usually in the format `jdbc:dm://host:port/sid`. For example, `jdbc:dm://dm-host:5236/dm`.
+* **Username**: Enter the username used to connect to the DM 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 on 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 the DM 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 to, 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 DM database service is accessible.
+* Protect your database credentials and SSH credentials to prevent 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 DM database 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. The direct connection method provides a more straightforward data transmission path.

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

@@ -0,0 +1,38 @@
+# Databricks Data Source Configuration Guide
+
+## Overview
+
+Databricks is a popular cloud data platform that offers various data services, including Delta Lake. Configuring a Databricks data source can help you integrate Databricks with your data system, enabling efficient data management and analysis.
+
+## Parameter Configuration
+
+When configuring a Databricks data source, you need to provide the following information to ensure a successful connection:
+
+1. Workspace URL: This is the unique URL of the Databricks workspace, usually in the format `https://<workspace-id>.cloud.databricks.com`. You can determine the workspace URL by logging into the Databricks workspace and checking the URL in the browser's address bar.
+
+2. Workspace ID: The workspace ID is the unique identifier of the Databricks workspace, usually reflected in the workspace URL as a string of numbers. For example, if the URL is `https://<databricks-instance>/?o=6280049833385130`, then the workspace ID is `6280049833385130`.
+
+3. Authentication Method: Databricks supports various authentication methods, including token-based authentication. You need to configure the authentication parameters according to the actual situation, such as using a Personal Access Token (PAT) for authentication. Choose the appropriate authentication method and configure the corresponding authentication information.
+
+4. Sql Warehouse: Please configure the Databricks Sql Warehouse required to run Databricks SQL workloads.
+
+5. Advanced Configuration: Provide advanced parameters for the data source in a Key-Value manner. This parameter is reserved and usually can be ignored. If needed, please contact our technical support for details on how to use it.
+
+## Connection Configuration
+
+When configuring the connection, you need to pay attention to the following:
+
+* Ensure that the workspace URL and workspace ID are correct and that the Databricks service is accessible.
+* Configure the corresponding authentication information according to Databricks documentation to ensure a secure connection.
+
+## Notes
+
+* Protect your Databricks credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in the workspace structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+## Completing the Configuration
+
+After completing the configuration, you can select this Databricks data source in data synchronization tasks to perform data import or export operations. Ensure to follow Databricks best practices and security policies to protect your data.
+
+Please refer to the official Databricks documentation and support resources for the most accurate guidance when configuring the Databricks data source.

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

@@ -0,0 +1,34 @@
+# Doris Data Source Configuration Guide
+
+## Overview
+
+Doris is a high-performance distributed data warehouse designed for fast analytics. By configuring the Doris data source, you can achieve efficient data import, export, and real-time analysis to meet the business needs of the big data era.
+
+## Parameter Configuration
+
+When configuring the Doris data source, you need to provide the following information to ensure a successful connection to the Doris cluster:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your Doris data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the Oracle database, usually 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.
+* **ExternalCatalog**: (Optional) Provide external catalog configuration, including type (such as MySQL, PostgreSQL, etc.) and corresponding connection information, for example, `mysql://user:password@host:port/database`.
+* **Address Type**: Select the node type, providing two options: "FE Node Address" and "BE Node Address".
+  * **FE Node Address**: Provide the address of the Doris Frontend (FE) node for connecting and managing the Doris cluster. For example, `fe-node:8030`.
+  * **BE Node Address**: Provide the address of the Doris Backend (BE) node for data storage and query processing. For example, `be-node:9050`.
+* **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:
+
+* Depending on the selected address type, ensure that the entered FE or BE node address is accessible on the public network. If the source end 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.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the Doris service is accessible.
+* If your Doris cluster has enabled authentication, protect your credential information to avoid leakage to unauthorized personnel.
+* Regularly check and update your data source configuration to adapt to changes in cluster structure or new security requirements.
+* Monitor the running status of data synchronization tasks to promptly identify and resolve any potential issues.
+
+After the configuration is complete, you can select this Doris data source in data synchronization tasks to perform data import or export operations. Choosing the appropriate node type and ensuring the correctness of the address can provide efficient data transmission and improve data processing efficiency. During the configuration process, ensure to follow best practices and security policies to protect your data security.

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

@@ -0,0 +1,37 @@
+# Amazon DynamoDB Data Source Configuration Guide
+
+## Overview
+
+Amazon DynamoDB is a fully managed NoSQL database service that delivers fast and predictable performance with seamless scalability. DynamoDB supports document and key-value data models and includes built-in security, data encryption, backup and restore, and in-memory caching for internet-scale applications. By configuring a DynamoDB data source, you can achieve efficient NoSQL data synchronization and processing, supporting the flexible data access patterns required by modern applications.
+
+## Parameter Configuration
+
+When configuring an Amazon DynamoDB data source, provide the following information to ensure a successful connection to the DynamoDB service:
+
+* **Data source name**: Assign a unique, easily identifiable name to your DynamoDB data source.
+* **Region**: Specify the AWS region where the DynamoDB service is located. Examples: `us-east-1` (US East), `us-west-2` (US West), `ap-southeast-1` (Asia Pacific — Singapore), `eu-west-1` (Europe — Ireland).
+* **Endpoint**: Provide the endpoint address for the DynamoDB service. The format is typically `https://dynamodb.{region}.amazonaws.com`, for example `https://dynamodb.us-east-1.amazonaws.com`.
+* **Authentication method**: Select "Access Key ID & Access Key Secret".
+* **Access Key ID**: Enter your AWS access key ID. This is typically a 20-character string beginning with `AKIA`.
+* **Access Key Secret**: Provide the corresponding AWS secret access key. This is a 40-character security credential string.
+* **Data source description**: (Optional) Add a description to help you or other administrators understand the purpose or characteristics of this data source.
+
+## Connection Configuration
+
+DynamoDB is an AWS cloud service that uses HTTPS-based secure connections:
+
+* **HTTPS connection**: Make sure the region and endpoint information you enter are correct. DynamoDB provides secure connections over HTTPS by default, and all data in transit is TLS-encrypted.
+* **Region consistency**: Ensure the Region parameter matches the region specified in the Endpoint to avoid connection errors.
+* **Network access**: If your network environment has firewall restrictions, make sure access to the DynamoDB endpoint for the relevant region is allowed. Refer to the IP address ranges published by AWS for configuration guidance.
+
+## Notes
+
+* **Verify connection details**: Confirm that all provided connection details are accurate — including the region, endpoint, and access credentials — and that the DynamoDB service is accessible in the specified region.
+* **Protect access credentials**: Keep your AWS access key information secure and do not expose it to unauthorized parties. Rotate access keys regularly and follow AWS security best practices.
+* **Permission configuration**: Ensure the IAM user used for the connection has the permissions required to perform data synchronization tasks, including but not limited to read and write access to the target DynamoDB tables. Follow the principle of least privilege.
+* **Cost management**: Understand DynamoDB's billing model (provisioned capacity or on-demand) and configure read/write capacity appropriately to control costs. Monitor resource consumption from data synchronization tasks.
+* **Data consistency**: Be aware of DynamoDB's eventual consistency model. If you require strongly consistent reads, configure this at the application level.
+* **Monitoring and maintenance**: Regularly review and update your data source configuration to accommodate changes in AWS services or new security requirements. Monitor the status of data synchronization tasks to detect and resolve issues promptly.
+* **Region selection**: Choose the AWS region closest to your data consumers for the best network latency and performance.
+
+Once configuration is complete, you can select this DynamoDB data source in your data synchronization tasks to import or export NoSQL data. DynamoDB's serverless architecture and auto-scaling capabilities make it an ideal choice for modern cloud-native applications. Proper permission configuration and monitoring measures will ensure your DynamoDB data source is both efficient and secure.

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

@@ -0,0 +1,30 @@
+# ElasticSearch Data Source Configuration Guide
+
+## Overview
+
+ElasticSearch is a distributed, RESTful search and data analysis engine that enables real-time full-text search and complex data analysis. Configuring an ElasticSearch data source can help you achieve efficient data operations in data synchronization and analysis tasks.
+
+## Parameter Configuration
+
+When configuring an ElasticSearch data source, you need to provide the following information to ensure a successful connection to the ElasticSearch cluster:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your ElasticSearch data source, such as `ElasticSearchLogAnalytics`.
+* **es address**: Provide the connection address of the ElasticSearch cluster in the format `http://host:port`. For example, `http://192.168.0.16:9200`.
+* **es username** (optional): If the ElasticSearch cluster is configured with security authentication, provide the connection username for the ElasticSearch cluster.
+* **es password** (optional): Provide the connection password for the corresponding username of the ElasticSearch cluster.
+* **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, 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.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the ElasticSearch 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 cluster 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 ElasticSearch data source in data synchronization tasks to perform data import or export operations. Through direct connection, you can achieve fast data transmission and improve data processing efficiency.

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

@@ -0,0 +1,36 @@
+# Greenplum Data Source Configuration Guide
+
+## Overview
+
+Greenplum is a high-performance, scalable open-source data warehouse platform developed based on PostgreSQL. By configuring the Greenplum data source, you can achieve efficient querying and analysis of large-scale datasets to meet complex data processing needs.
+
+## Parameter Configuration
+
+When configuring the Greenplum data source, you need to provide the following information to ensure a successful connection to the Greenplum database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your Greenplum data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the Greenplum database, usually in the format `jdbc:postgresql://host:port/database`. For example, `jdbc:postgresql://gp-server:5432/mydatabase`.
+* **Username**: Enter the username used to connect to the Greenplum database.
+* **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.
+* **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 Greenplum 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 listens to, 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 Greenplum service is accessible.
+* Protect your database credentials and SSH credentials to avoid leaking them 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 Greenplum 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. Selecting 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_HANA.md

@@ -0,0 +1,53 @@
+# HANA Data Source Configuration Guide
+
+## Overview
+
+SAP HANA is a high-performance in-memory relational database management system developed by SAP. It supports both OLTP (Online Transaction Processing) and OLAP (Online Analytical Processing), with real-time data processing capabilities and advanced analytics features. By configuring an SAP HANA data source, you can achieve efficient data synchronization and processing to support complex data analysis and business intelligence applications.
+
+## Parameter Configuration
+
+When configuring an SAP HANA data source, provide the following information to ensure a successful connection to the HANA database:
+
+* **Data source name**: Assign a unique, easily identifiable name to your HANA data source. A meaningful naming convention is recommended, such as "Behavioral Data Source".
+* **JDBC connection URL**: Provide the JDBC connection URL for the SAP HANA database. The format is typically `jdbc:sap://host:port`, for example `jdbc:sap://hana-server:30015`. For HANA Cloud, the connection URL may look like `jdbc:sap://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.hana.trial-us10.hanacloud.ondemand.com:443/?encrypt=true&validateCertificate=true`.
+* **Username**: Enter the username for connecting to the HANA database. This is typically a database user with the appropriate permissions, such as `admin`.
+* **Password**: Provide the database password for the corresponding username. Ensure the password is secure and accurate.
+* **Allow this configuration to connect to all databases/schemas** (optional): Check this option to allow the configuration to be used for connecting to all databases and schemas in the HANA instance. If unchecked, the connection is limited to the specified schema. Use this option with caution in production environments.
+* **Database timezone**: Select the timezone of the HANA database to ensure time data accuracy.
+* **Data source description**: (Optional) Add a description to help you or other administrators understand the purpose or characteristics of this data source.
+
+## Connection Configuration
+
+For the connection configuration, you can choose one of the following connection methods:
+
+### Direct Connection
+
+Ensure that the connection information you enter is accessible over the network. If the HANA server has an IP allowlist enabled, make sure the outbound IP address of the data integration service has been added to the allowlist. Contact technical support for the specific IP addresses.
+
+### Via SSH Tunnel
+
+For enhanced security, you can connect to SAP HANA through an SSH tunnel. Enable this option and provide the following SSH tunnel configuration:
+
+* **SSH server address**: Provide the IP address or hostname of the SSH server.
+* **SSH port**: Specify the port the SSH server listens on, typically `22`.
+* **Username**: Provide the login username for the SSH server.
+* **Password**: Provide the password for the SSH server login username.
+
+## Notes
+
+* **Validate connection details**: Ensure all provided connection details are accurate and that the SAP HANA service is accessible. Before saving the configuration, use the "Test Connection" feature to verify connectivity.
+* **Security management**: Keep your database credentials and SSH credentials secure and do not expose them to unauthorized parties. Rotate database passwords regularly.
+* **Permission configuration**: Ensure the database user used for the connection has the permissions required to perform data synchronization tasks, including but not limited to SELECT, INSERT, UPDATE, and DELETE.
+* **Network configuration**: If the HANA database is deployed behind a firewall, ensure the necessary ports (e.g., 30015, 30013) are open.
+* **Performance optimization**: As an in-memory database, SAP HANA benefits from properly configured connection pool parameters for optimal performance.
+* **Monitoring and maintenance**: Regularly review and update your data source configuration to accommodate changes in database structure or new security requirements. Monitor the status of data synchronization tasks to detect and resolve issues promptly.
+* **Version compatibility**: Confirm that your HANA database version is compatible with the data integration platform. HANA Cloud, HANA 2.0 SP04, or later versions are recommended.
+
+## Best Practices
+
+* **Connection pool configuration**: Set an appropriate connection pool size to avoid performance issues caused by too many or too few connections.
+* **Schema permissions**: Grant only the necessary schema access permissions, following the principle of least privilege.
+* **Data type mapping**: Understand the mapping between HANA data types and the target system to ensure data synchronization accuracy.
+* **Backup strategy**: Back up target data before performing important data synchronization operations.
+
+Once configuration is complete, you can select this HANA data source in your data synchronization tasks to import or export data. Connecting via an SSH tunnel enhances the security of data transmission, especially when handling sensitive data. Proper permission configuration and security measures will ensure your HANA data source is both efficient and secure.

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

@@ -0,0 +1,29 @@
+# HBase Data Source Configuration Guide
+
+## Overview
+
+HBase is a distributed, column-oriented open-source NoSQL database that provides random, real-time read/write access to large-scale datasets. Configuring an HBase data source allows you to efficiently utilize HBase for storing and retrieving data in data integration tasks.
+
+## Parameter Configuration
+
+When configuring an HBase data source, you need to provide the following information to ensure a successful connection to the HBase cluster:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your HBase data source, such as `HBaseSource01`.
+* **ZK Connection Address**: Provide the Zookeeper connection address in the format `host1:port,host2:port,host3:port`. For example, `192.168.0.177:2181,192.168.0.179:2181,192.168.0.178:2181`.
+* **ZK Parent**: Specify the parent path of Zookeeper, usually `/hbase`.
+* **RootDir**: Specify the root directory of HBase, such as `/hbase-data`.
+* **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 enter 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 personnel.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the HBase service is accessible.
+* Regularly check and update your data source configuration to adapt to changes in the cluster 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 HBase data source in data synchronization tasks to perform data import or export operations. Using an SSH tunnel connection can enhance the security of data transmission, especially when handling sensitive data.

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

@@ -0,0 +1,50 @@
+# Hive Data Source Configuration Guide
+
+## Overview
+
+Hive is a data warehouse software based on the Hadoop ecosystem. It provides an SQL interface (HiveQL) to query and manage large-scale datasets. By configuring the Hive data source, you can achieve data synchronization with other systems and perform complex data analysis tasks.
+
+## Parameter Configuration
+
+When configuring the Hive data source, you need to provide the following information to ensure a successful connection to the Hive service:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your Hive data source.
+* **HiveServer Connection Information**: Provide the JDBC connection URL for HiveServer, usually in the format `jdbc:hive2://host:port/database`. For example, `jdbc:hive2://hive-server:10000/default`.
+* **Authentication Mode**: Choose whether to use anonymous authentication. If anonymous is selected, no username and password are required; if not, you must provide a username and password.
+* **Username**: If not using anonymous authentication, provide the username required to connect to the database.
+* **Password**: The database password corresponding to the username.
+* **defaultFS**: Provide the default parameter for HDFS, corresponding to the `fs.defaultFS` parameter in the core-site.xml file.
+* **hiveVersion** (optional): Provide the version information of Hive.
+* **hiveMetaStoreUri** (optional): Provide the Hive metastore connection URI.
+* **Extended Parameters** (optional): If needed, provide other Hadoop-related parameters, such as the NameNode address.
+```JSON
+{
+    "hadoop.user.name": "datadev",
+    "dfs.ha.namenodes.zetta-cluster": "nn1,nn2",
+    "dfs.namenode.rpc-address.zetta-cluster.nn1": "test-01:8020",
+    "dfs.nameservices": "zetta-cluster",
+    "dfs.namenode.rpc-address.zetta-cluster.nn2": "test-02:8020"
+}
+```
+* **Authentication Method**: Choose the authentication method, providing two options: "None" and "Kerberos Authentication".
+  * If "None" is selected, no additional authentication information is required.
+  * If "Kerberos Authentication" is selected, Kerberos-related authentication information needs to be provided, including:
+    * Username: Provide the username for Kerberos authentication.
+    * Password: Provide the password corresponding to the username.
+    * Kerberos keytab file (optional): If using a Kerberos keytab for authentication, provide the path to the keytab file.
+
+## 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 Hive 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 Hive server via SSH.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the Hive service is accessible.
+* Protect your database credential information to prevent 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 Hive data source in the data synchronization task 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_Hologres.md

@@ -0,0 +1,36 @@
+# Hologres Data Source Configuration Guide
+
+## Overview
+
+Hologres is a high-performance, highly available distributed data warehouse service that provides powerful data storage and analysis capabilities. By configuring the Hologres data source, you can achieve efficient data synchronization and complex analysis, supporting various data operations and reporting needs.
+
+## Parameter Configuration
+
+When configuring the Hologres data source, you need to provide the following information to ensure a successful connection to the Hologres service:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your Hologres data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the Hologres database, typically in the format  `jdbc:postgresql://host:port/database`, such as `jdbc:postgresql://xxxxxxxxxx-cn-hangzhou.hologres.aliyuncs.com:80/test`。
+* **Username**: Enter the username used to connect to the Hologres database.
+* **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.
+* **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 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 Hologres 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, such as `ssh.example.com`.
+  * **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 Hologres service is accessible.
+* Protect your database credentials and SSH credentials to prevent unauthorized access.
+* 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 Hologres 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_Kafka.md

@@ -0,0 +1,32 @@
+# Apache Kafka Data Source Configuration Guide
+
+## Overview
+
+Apache Kafka is a high-throughput, scalable distributed event streaming platform, ideal for building real-time data pipelines and stream processing applications. By configuring a Kafka data source, you can achieve efficient data streaming with other systems.
+
+## Parameter Configuration
+
+When configuring a Kafka data source, you need to provide the following information to ensure a successful connection to the Kafka cluster:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your Kafka data source, such as `OrderStreamKafka`.
+* **Kafka Connection Configuration**: Fill in the service addresses of the Kafka cluster in the format `host1:port,host2:port,host3:port`. For example, `order-kafka-broker-01:9092,order-kafka-broker-02:9092`.
+* **Kafka Security Authentication Protocol**: Choose the appropriate security authentication protocol, such as No Authentication, SASL_PLAINTEXT, SASL_SSL/SCRAM.
+* **JAAS Configuration**: If using SASL_SSL authentication, provide the Java Authentication and Authorization Service (JAAS) configuration string, for example, `org.apache.kafka.common.security.plain.PlainLoginModule required username="orderuser" password="orderpass";`.
+* **Truststore (CA Certificate) File**: If using SASL_SSL authentication, specify the path to the truststore file, for example, `kafka.client.truststore.jks`.
+* **Truststore Password**: Provide the access password for the truststore.
+* **Keystore (Private Key) File**: If client authentication is required, specify the path to the keystore file, for example, `kafka.client.keystore.jks`.
+* **Keystore Password**: Provide the access password for the keystore.
+
+## Connection Configuration
+
+Regarding connection configuration, you need to pay attention to the following:
+
+* **Direct Connection**: Ensure that the connection information you enter is accessible on the public network. If the source end has enabled an IP access whitelist, 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.
+
+## Notes
+
+* Ensure the security and stability of the Kafka cluster, and configure authentication and authorization mechanisms appropriately.
+* In a production environment, it is recommended to use encrypted connections (such as SASL_SSL) to protect data transmission security.
+* Monitor the running status of the Kafka cluster to promptly identify and resolve potential issues.
+
+After completing the configuration, you can select this Kafka data source in data synchronization tasks to perform data import or export operations.

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

@@ -0,0 +1,36 @@
+# MariaDB Data Source Configuration Guide
+
+## Overview
+
+MariaDB is a popular open-source relational database management system, which is a fork of MySQL, offering high performance, reliability, and compatibility. By configuring the MariaDB data source, you can achieve efficient data synchronization and processing, supporting various data operations and analysis tasks.
+
+## Parameter Configuration
+
+When configuring the MariaDB data source, you need to provide the following information to ensure a successful connection to the MariaDB database:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your MariaDB data source.
+* **JDBC Connection URL**: Provide the JDBC connection URL for the MariaDB database, usually in the format `jdbc:mysql://host:port/database`. For example, `jdbc:mysql://mariadb-host:3306/mydatabase`.
+* **Username**: Enter the username used to connect to the MariaDB database.
+* **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 MariaDB instance. 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 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 MariaDB 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 MariaDB service is accessible.
+* Protect your database credentials and SSH credentials to prevent unauthorized access.
+* 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 MariaDB 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 cautiously to avoid security risks.

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

@@ -0,0 +1,32 @@
+# MaxCompute Data Source Configuration Guide
+
+## Overview
+
+MaxCompute is a fully managed big data computing service provided by Alibaba Cloud. It supports the storage, processing, and analysis of massive amounts of data. By configuring the MaxCompute data source, you can achieve data synchronization with other systems and big data analysis.
+
+## Parameter Configuration
+
+When configuring the MaxCompute data source, you need to provide the following information to ensure a successful connection to the service:
+
+* **Data Source Name**: Specify a unique and easily recognizable name for your MaxCompute data source.
+* **MaxCompute Service Address**: Provide the Endpoint connection address of the MaxCompute service, which is the main entry point for accessing the MaxCompute service, for example: `<http://service.ap-southeast-1.maxcompute.aliyun.com/api>`.
+* **MaxCompute Tunnel Service Address** (optional): If you use the Tunnel service to enhance data transmission security, you need to provide the Tunnel service address. For example: `http://dt.<region-name>.maxcompute.aliyun.com/api`, where `<region-name>` is the region name of your MaxCompute service.
+* **Project Space Name**: Fill in the project space name associated with your MaxCompute account, which is the context environment for operating and managing data.
+* **Access Key ID**: Provide the Access Key ID of your Alibaba Cloud account for authentication.
+* **Secret Access Key**: Provide the secret access key corresponding to the Access Key ID.
+
+## 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 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 personnel.
+* **Via SSH Tunnel**: To enhance security, you can choose to connect to MaxCompute via an SSH tunnel. Enable this option and provide the IP address and port of the SSH service. Ensure that your SSH client is correctly configured and that you have permission to connect to the MaxCompute server via SSH.
+
+## Notes
+
+* Ensure that all provided connection information is accurate and that the MaxCompute 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 project space 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 MaxCompute data source in data synchronization tasks to perform data import or export operations. Connecting via SSH tunnel or MaxCompute Tunnel service can enhance data transmission security, especially when handling sensitive data.