npm - @clickzetta/cz-cli-darwin-arm64 - Versions diffs - 0.5.16 → 0.5.17 - Mend

@clickzetta/cz-cli-darwin-arm64 0.5.16 → 0.5.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (243) hide show

package/bin/skills/lakehouse-doc-en/references/data-quality.md CHANGED Viewed

@@ -6,7 +6,9 @@ In the era of big data, data quality management is a critical step to ensure dat
 The data quality overview page provides an intuitive data quality monitoring dashboard, making it easy to view the overall status of quality rules and validation runs. Below are detailed explanations of some indicators:
-![](.topwrite/assets/image_1760004305684.png)
+![](/.topwrite/assets/image_1780673989475.png =740)
+^
 The definitions of some indicators are as follows:
@@ -23,7 +25,7 @@ The definitions of some indicators are as follows:
 The quality rules page displays all your configured quality rules in a list format. Use the filter area at the top to quickly find the rules you need.
-![](.topwrite/assets/image_1760004360956.png)
+^
 Use the top filter area to perform detailed searches.
@@ -31,23 +33,22 @@ Use the top filter area to perform detailed searches.
 1. In the quality rules list, or in the rule list of a validation object, click the "Create Rule" button to enter the new quality rule page.
 2. Fill in the required configuration items, such as data source, workspace, validation object, owner, description, parameter configuration, value filtering, validation method, expected result, trigger method, execution cluster, and timeout duration.
- ![](.topwrite/assets/image_1760004384816.png)
-| **Configuration Item**       | **Configuration Description**                                                                                                                                                                                                                                |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Data Source           | The type of data source. Currently only Lakehouse data sources are supported.                                                                                                                                                                                                                |
-| Workspace          | The workspace to which the validation object belongs.                                                                                                                                                                                                                             |
-| Validation Object          | When the validation object is a Lakehouse table, select its Schema and name (table name, view name, etc.).                                                                                                                                                                                              |
-| Owner           | The person responsible for the quality rule, affecting who receives alerts.                                                                                                                                                                                                                        |
-| Description            | A description defined for the quality rule.                                                                                                                                                                                                                              |
-| Parameter Configuration          | In the quality rule, when using value filtering and custom SQL to compute metric values, you can reference predefined dynamic parameter values. For example, define a parameter: partition = $[yyyyMMdd].                                                                                                                                                           |
-| Value Filtering          | Used to filter the range of objects to validate, such as filtering by partition. Supports parameter references: dt = ${partition}.                                                                                                                                                                                       |
-| Validation Method - Built-in Metrics   | System built-in validation metrics. Select as needed.                                                                                                                                                                                                                        |
-| Validation Method - Custom SQL | If the built-in metrics do not meet your needs, you can compute metric values using custom SQL. Important: The result of custom SQL must be a single numeric value to enable comparison.                                                                                                                                                               |
-| Expected Result          | Define the expected result for the metric value.                                                                                                                                                                                                                              |
-| Trigger Method          | Configures how the quality rule is triggered to run. 1. Scheduled trigger: The system triggers a single validation run at the specified time. 2. Periodic task trigger: Triggered by an associated periodic task instance after the instance runs successfully. For periodic scheduling triggers, there are two scheduling blocking options: A. Strong blocking: If validation fails, the associated task instance is marked as failed, blocking downstream instances. B. Non-blocking: The quality rule runs as a bypass and does not affect the task instance's run status. 3. Manual trigger: Manually triggered as needed. |
-| Execution Cluster          | Specifies the compute cluster within the workspace for running the quality rule.                                                                                                                                                                                                                     |
-| Timeout Duration          | If the quality rule validation does not complete within the set timeout, it will be automatically canceled by the system.                                                                                                                                                                                                       |
+| **Configuration Item**               | **Configuration Description**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Data Source                          | The type of data source. Currently only Lakehouse data sources are supported.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Workspace                            | The workspace to which the validation object belongs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Validation Object                    | When the validation object is a Lakehouse table, select its Schema and name (table name, view name, etc.).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Owner                                | The person responsible for the quality rule, affecting who receives alerts.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Description                          | A description defined for the quality rule.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Parameter Configuration              | In the quality rule, when using value filtering and custom SQL to compute metric values, you can reference predefined dynamic parameter values. For example, define a parameter: partition = $\[yyyyMMdd].                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Value Filtering                      | Used to filter the range of objects to validate, such as filtering by partition. Supports parameter references: dt = ${partition}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Validation Method - Built-in Metrics | System built-in validation metrics. Select as needed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Validation Method - Custom SQL       | If the built-in metrics do not meet your needs, you can compute metric values using custom SQL. Important: The result of custom SQL must be a single numeric value to enable comparison.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| Expected Result                      | Define the expected result for the metric value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Trigger Method                       | Configures how the quality rule is triggered to run. 1. Scheduled trigger: The system triggers a single validation run at the specified time. 2. Periodic task trigger: Triggered by an associated periodic task instance after the instance runs successfully. For periodic scheduling triggers, there are two scheduling blocking options: A. Strong blocking: If validation fails, the associated task instance is marked as failed, blocking downstream instances. B. Non-blocking: The quality rule runs as a bypass and does not affect the task instance's run status. 3. Manual trigger: Manually triggered as needed. |
+| Execution Cluster                    | Specifies the compute cluster within the workspace for running the quality rule.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Timeout Duration                     | If the quality rule validation does not complete within the set timeout, it will be automatically canceled by the system.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 After filling in the required configuration items, click the "Confirm" button to create the rule.
@@ -57,28 +58,27 @@ After filling in the required configuration items, click the "Confirm" button to
 After creating a quality rule, it is recommended to use the "Test Run" feature to verify the correctness of the configuration. After a successful test run, you can view the results to adjust the rule.
-![](.topwrite/assets/image_1760004576132.png)
+^
 ### View Test Run Results
 After clicking "Test Run", follow the prompts to click "View Results" to see the test run validation results.
-![](.topwrite/assets/image_1699875850066.png)
+^
 ### Configure Monitoring Alerts
 To ensure data quality issues are addressed promptly, you can configure monitoring alerts for quality rules. There are two ways:
 1. **Enable global quality monitoring alerts**: In the monitoring and alerting module, search for "Data Quality Check Failed" and enable the system's built-in global quality validation monitoring rule.
-   ![](.topwrite/assets/image_1699875920709.png)
 2. **Configure custom quality monitoring alerts**: Create custom monitoring rules, select "Quality Rule Validation Failed" as the monitoring message, and set filter conditions such as workspace or specific validation object.
-   ![](.topwrite/assets/image_1699875932007.png)
 ## Validation Objects
 On the validation objects page, you can manage all quality rules by the validation object (table) dimension. Use the search filter area to quickly locate specific rules.
-![](.topwrite/assets/image_1699875683208.png)
+![](/.topwrite/assets/image_1780674038464.png)
 ## Validation Results
@@ -86,7 +86,7 @@ On the validation objects page, you can manage all quality rules by the validati
 On the validation results list page, you can view the run status of all quality rules. Use the search and filter area to precisely find the required validation results.
-![](.topwrite/assets/image_1699875971234.png)
+^
 ### Operations on Validation Results

package/bin/skills/lakehouse-doc-en/references/data-sharing.md CHANGED Viewed

@@ -53,40 +53,32 @@ You can use `all tables in schema <schema_name>` and `all views in schema <schem
 **1. Create a share object**
-To ensure data security, share objects must be created by users with the "Instance Administrator" (instance_admin) role. Click "Data Management" - "Data Sharing" in the left menu to enter the data sharing list page.
+To ensure data security, share objects must be created by users with the "Instance Administrator" (instance\_admin) role. Click "Data Management" - "Data Sharing" in the left menu to enter the data sharing list page.
 Click "+ New Share" to open the new data sharing window:
-:-: ![](.topwrite/assets/image_1734492957409.png =507)
+1. Fill in the "Share Name" for the data share.
-1) Fill in the "Share Name" for the data share.
+2. Select "Workspace," which refers to the workspace containing the tables or views to be shared. A single data share object can only contain data from one workspace.
-2) Select "Workspace," which refers to the workspace containing the tables or views to be shared. A single data share object can only contain data from one workspace.
+3. In the data object row, click "Add." Select the specific tables or views to include in the data share. Multiple selections are allowed. Note that tables and views originating from other shares cannot be selected, because data sharing authorization does not permit secondary sharing. Data shares created via the web interface only support including existing tables and views; specifying "future" tables or views under an entire schema is not yet supported.
-3) In the data object row, click "Add." Select the specific tables or views to include in the data share. Multiple selections are allowed. Note that tables and views originating from other shares cannot be selected, because data sharing authorization does not permit secondary sharing. Data shares created via the web interface only support including existing tables and views; specifying "future" tables or views under an entire schema is not yet supported.
-4) In the recipient instance row, click "Add." Enter the name of the service instance that needs to receive the data. Service instance names are globally unique within the Lakehouse service. Consumer users can find their service instance name on the right side of the homepage or in the service instance URL and provide it to the sharer for configuration.
-:-: ![](.topwrite/assets/share_img_instancename.png =786)
+4. In the recipient instance row, click "Add." Enter the name of the service instance that needs to receive the data. Service instance names are globally unique within the Lakehouse service. Consumer users can find their service instance name on the right side of the homepage or in the service instance URL and provide it to the sharer for configuration.
 ^
 *Note*:
-1. *To ensure data security with workspace-level isolation, only users with the Workspace Administrator role can add data objects from their managed workspace to a data share.*
-2. *In the create share dialog, "Create" and "Add Data" are two separate operations. Even if adding shared data fails partially or completely, it does not affect the creation of the share object. When any operation fails, an error message is returned. You can click on an already-created share in the data sharing list to continue adding data objects or recipient service instances.*
+1. *To ensure data security with workspace-level isolation, only users with the Workspace Administrator role can add data objects from their managed workspace to a data share*.
+2. *In the create share dialog, "Create" and "Add Data" are two separate operations. Even if adding shared data fails partially or completely, it does not affect the creation of the share object. When any operation fails, an error message is returned. You can click on an already-created share in the data sharing list to continue adding data objects or recipient service instances*.
 **2. Query created share objects**
-All share objects created within the current service instance are displayed on the "Data Sharing" list page. Users with the Instance Administrator role (instance_admin) or Workspace Administrator role (workspace_admin) can view the list of share objects.
-:-: ![](.topwrite/assets/image_1734493289109.png =737)
+All share objects created within the current service instance are displayed on the "Data Sharing" list page. Users with the Instance Administrator role (instance\_admin) or Workspace Administrator role (workspace\_admin) can view the list of share objects.
 **3. View share details**
-On the "Data Sharing" list page, click a specific share name to view detailed information about the share, including basic information, recipient service instances, and shared data objects. Users with the Instance Administrator role (instance_admin) or Workspace Administrator role (workspace_admin) can view share object details.
-:-: ![](.topwrite/assets/image_1734493331354.png =735)
+On the "Data Sharing" list page, click a specific share name to view detailed information about the share, including basic information, recipient service instances, and shared data objects. Users with the Instance Administrator role (instance\_admin) or Workspace Administrator role (workspace\_admin) can view share object details.
 **4. Add/Remove shared data objects**
@@ -96,19 +88,16 @@ On the data sharing list page, click the name of the share object to which you w
 Added data objects become immediately visible to share consumers and appear in their schema for extracting data.
-:-: ![](.topwrite/assets/image_1734493367553.png =721)
 **5. Configure share targets**
-You must configure the recipient service instance name (instance_name) for the share object to complete data sharing. The service instance name needs to be provided by the data consumer.
+You must configure the recipient service instance name (instance\_name) for the share object to complete data sharing. The service instance name needs to be provided by the data consumer.
-:-: ![](.topwrite/assets/image_1734493417202.png =771)
 ^
 **6. Delete a share object**
-Users with the Instance Administrator role (instance_admin) or the Workspace Administrator role (workspace_admin) for the workspace to which the share belongs can delete share objects.
+Users with the Instance Administrator role (instance\_admin) or the Workspace Administrator role (workspace\_admin) for the workspace to which the share belongs can delete share objects.
 On the data sharing list page or in the share details, click the "Delete" button under "Actions" to delete the share object. Once a share object is deleted, it cannot be recovered. Data consumers immediately lose access to the shared data.
@@ -116,7 +105,7 @@ On the data sharing list page or in the share details, click the "Delete" button
 **1. Create a share object**
-To ensure data security, share objects must be created by users with the "Instance Administrator" (instance_admin) role. When creating a share object, execute the following statement in the workspace where you plan to share data:
+To ensure data security, share objects must be created by users with the "Instance Administrator" (instance\_admin) role. When creating a share object, execute the following statement in the workspace where you plan to share data:
 ```SQL
 CREATE SHARE <share_name>;
@@ -145,7 +134,7 @@ Grant select, read metadata on ALL tables in SCHEMA share_demo_schema TO SHARE s
 Grant select, read metadata on ALL views in SCHEMA share_demo_schema TO SHARE share_demo;
 ```
-When adding data objects to a share, the user executing the operation must have SELECT (query) and READ METADATA (view metadata) privileges on the involved tables or views, and must be able to grant them onward (with grant option). The Workspace Administrator role (workspace_admin) inherently has the above privileges.
+When adding data objects to a share, the user executing the operation must have SELECT (query) and READ METADATA (view metadata) privileges on the involved tables or views, and must be able to grant them onward (with grant option). The Workspace Administrator role (workspace\_admin) inherently has the above privileges.
 To remove shared data objects from a share, use the REVOKE statement:
@@ -159,11 +148,10 @@ Note: When sharing a table or view, since the table or view always exists under
 **3. Configure share targets**
-You must configure the recipient service instance name (instance_name) for the share object to complete data sharing. The service instance name needs to be provided by the data consumer.
+You must configure the recipient service instance name (instance\_name) for the share object to complete data sharing. The service instance name needs to be provided by the data consumer.
 Service instance names are globally unique within the Lakehouse service. Consumer users can find their service instance name on the right side of the homepage or in the service instance URL and provide it to the sharer for configuration.
-:-: ![](.topwrite/assets/share_img_instancename.png =786)
 The syntax for the data provider to configure share targets is:
@@ -185,17 +173,13 @@ You can execute the SHOW command to query created share objects. The syntax is:
 SHOW SHARES;
 ```
-Example result:
-:-: ![](.topwrite/assets/share_img_showshares.png =803)
 Where:
 * provider is the tenant name of the share provider;
-* provider_instance is the service instance name of the share provider;
-* provider_workspace is the workspace to which the share belongs;
+* provider\_instance is the service instance name of the share provider;
+* provider\_workspace is the workspace to which the share belongs;
 * scope is the sharing scope of the share. Currently only PRIVATE is supported -- sharing to specified instances;
-* to_instance is the service instance name(s) to which the share is shared. Multiple instance names are separated by commas (,);
+* to\_instance is the service instance name(s) to which the share is shared. Multiple instance names are separated by commas (,);
 * kind is the share type. OUTBOUND indicates data shared from the current service instance; INBOUND indicates data shared from other service instances to the current service instance.
 ^
@@ -208,9 +192,6 @@ Execute the following statement to query the data objects granted in a share:
 DESC SHARE <share_name>;
 ```
-Example result:
-:-: ![](.topwrite/assets/share_img_descshare.png =798)
 ^
@@ -230,11 +211,10 @@ Once a share object is deleted, it cannot be recovered. Data consumers immediate
 **1. View shared data**
-Users with the Instance Administrator (instance_admin) role or Workspace Administrator (workspace_admin) role can view all share objects shared to the current service instance in the "Shared With Me" tab under the "Data Sharing" menu.
+Users with the Instance Administrator (instance\_admin) role or Workspace Administrator (workspace\_admin) role can view all share objects shared to the current service instance in the "Shared With Me" tab under the "Data Sharing" menu.
 Click a share object name to view details including the source, reception time, and the data (tables or views) currently contained in the share.
-:-: ![](.topwrite/assets/image_1734493496334.png =777)
 ^
@@ -242,11 +222,9 @@ Click a share object name to view details including the source, reception time,
 On the "Shared With Me" list page or the share details page, click the "Extract" button to extract data from the share.
-:-: ![](.topwrite/assets/image_1734493713534.png =793)
 When extracting data, extraction can only be done at the schema level. Individual table or view extraction is not yet supported.
-:-: ![](.topwrite/assets/image_1734493642759.png =541)
 First, select "Source Schema," which is the schema from which to extract data. If the share contains multiple schemas, you need to perform multiple extractions.
@@ -260,7 +238,6 @@ After completing data extraction, you can see all tables and views shared under
 Shared data is marked with a special icon in the "Data" panel for easy identification.
-:-: ![](.topwrite/assets/image_1734493884869.png =279)
 ### Using SQL
@@ -284,7 +261,7 @@ Where `<provider_instance>` and `<share_name>` can be obtained from the `SHOW SH
 The schema name in `CREATE SCHEMA <schema_name>` can be customized and does not need to match the schema name in the share.
-When executing the above command, the operator must have permission to create schemas in the target workspace. The Workspace Administrator role (workspace_admin) inherently has this permission.
+When executing the above command, the operator must have permission to create schemas in the target workspace. The Workspace Administrator role (workspace\_admin) inherently has this permission.
 ^
@@ -296,15 +273,15 @@ After executing `CREATE SCHEMA FROM SHARE`, you can see all tables and views sha
 **1. Provider permissions**
-Only users with the Instance Administrator (instance_admin) role can create share objects. The permission points for share operations are as follows. Granting share object permissions to other roles or users via the GRANT statement is not currently supported.
+Only users with the Instance Administrator (instance\_admin) role can create share objects. The permission points for share operations are as follows. Granting share object permissions to other roles or users via the GRANT statement is not currently supported.
-| **Permission**                                                    | **Description**                                                                        |
-| --------------------------------------------------------------- | ----------------------------------------------------------------------------- |
-| Create share                                                    | Permission to create share objects.                                                                |
-| Alter share                                                     | Permission to modify share objects, add or remove shared instance IDs.                                                    |
-| Drop share                                                      | Permission to delete share instances.                                                                   |
-| Read metadata                                                   | Permission for SHOW SHARES and DESC SHARE. DESC SHARE returns the objects and granted object privileges within the share. |
-| Grant objectprivilege to share / Revoke objectprivilege from share | Add or remove data objects from a share: GRANT objectPrivilege TO; REVOKE objectPrivilege FROM.         |
+| **Permission**                                                     | **Description**                                                                                                           |
+| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
+| Create share                                                       | Permission to create share objects.                                                                                       |
+| Alter share                                                        | Permission to modify share objects, add or remove shared instance IDs.                                                    |
+| Drop share                                                         | Permission to delete share instances.                                                                                     |
+| Read metadata                                                      | Permission for SHOW SHARES and DESC SHARE. DESC SHARE returns the objects and granted object privileges within the share. |
+| Grant objectprivilege to share / Revoke objectprivilege from share | Add or remove data objects from a share: GRANT objectPrivilege TO; REVOKE objectPrivilege FROM.                           |
 ^
@@ -312,9 +289,9 @@ Only users with the Instance Administrator (instance_admin) role can create shar
 All members in a workspace have USE and READ METADATA permissions on share objects. However, the CREATE SCHEMA permission in the workspace is required to create a schema from the data in a share.
-| **Permission**    | **Description**                                        |
-| ------------- | --------------------------------------------- |
-| Use           | Permission to use the share.                                  |
-| Read metadata | Permission to query share metadata. After obtaining this, SHOW SHARES and DESC SHARE can be executed. |
+| **Permission** | **Description**                                                                                       |
+| -------------- | ----------------------------------------------------------------------------------------------------- |
+| Use            | Permission to use the share.                                                                          |
+| Read metadata  | Permission to query share metadata. After obtaining this, SHOW SHARES and DESC SHARE can be executed. |
 ^

package/bin/skills/lakehouse-doc-en/references/data-sources.md CHANGED Viewed

@@ -10,53 +10,53 @@ The data source types and versions currently supported by each task type are as
 ### Offline Sync
-| Data Source | Release Level | Offline Single-Table Read | Offline Single-Table Write | Supported Versions |
-| --------------------- | ------- | ---- | ---- | --------------------- |
-| Singdata Lakehouse | GA | Y | Y | - |
-| ADB MySQL              | GA (Beta) | Y     | Y     | 3.x                    |
-| ADB PostgreSQL         | GA (Beta) | Y     | Y     | 6.x                    |
-| AMQP                   | GA (Beta) | Y     | N     | -                      |
-| AutoMQ                 | GA       | Y     | Y     | -                      |
-| ClickHouse | GA | Y | Y | 19.x and above |
-| COS                    | GA       | Y     | Y     | -                      |
-| Databricks             | GA       | Y     | Y     | -                      |
-| DB2                    | GA (Beta) | Y     | Y     | 11.x                   |
-| DM                     | GA (Beta) | Y     | Y     | 8.x                    |
-| Doris                  | GA (Beta) | Y     | Y     | 1.x                    |
-| DynamoDB               | GA       | Y     | Y     | -                      |
-| Elasticsearch          | GA       | Y     | Y     | 7.x                    |
-| Greenplum | GA (Beta) | Y | Y | 5.x and above |
-| HBase | GA | N | Y | 1.4+ |
-| Hive                   | GA       | Y     | Y     | 2.x                    |
-| Hologres               | GA (Beta) | Y     | Y     | -                      |
-| Kafka | GA | Y | Y | 0.8.x, 0.9.x, 0.10.x, 2.x |
-| MaxCompute             | GA       | Y     | N     | -                      |
-| MariaDB                | GA (Beta) | Y     | Y     | -                      |
-| MongoDB | GA | Y | N | 3.4 and above |
-| MySQL                  | GA       | Y     | Y     | 5.x, 8.x                |
-| Oracle                 | GA (Beta) | Y     | Y     | -                      |
-| OSS                    | GA       | Y     | Y     | -                      |
-| PolarDB for MySQL      | GA       | Y     | Y     | -                      |
-| PolarDB for PostgreSQL | GA       | Y     | Y     | -                      |
-| PostgreSQL | GA | Y | Y | 9.4 and above |
-| Redis                  | GA       | N     | Y     | -                      |
-| Redshift               | GA (Beta) | Y     | Y     | -                      |
-| RestApi                | GA       | Y     | N     | -                      |
-| SLS (LogHub)            | GA       | Y     | N     | -                      |
-| SQL Server | GA | Y | Y | 2012 and above |
-| StarRocks              | GA (Beta) | Y     | Y     | 2.5                    |
-| TiDB                   | GA (Beta) | Y     | Y     | -                      |
+| Data Source            | Release Level | Offline Single-Table Read | Offline Single-Table Write | Supported Versions        |
+| ---------------------- | ------------- | ------------------------- | -------------------------- | ------------------------- |
+| Singdata Lakehouse     | GA            | Y                         | Y                          | -                         |
+| ADB MySQL              | GA (Beta)     | Y                         | Y                          | 3.x                       |
+| ADB PostgreSQL         | GA (Beta)     | Y                         | Y                          | 6.x                       |
+| AMQP                   | GA (Beta)     | Y                         | N                          | -                         |
+| AutoMQ                 | GA            | Y                         | Y                          | -                         |
+| ClickHouse             | GA            | Y                         | Y                          | 19.x and above            |
+| COS                    | GA            | Y                         | Y                          | -                         |
+| Databricks             | GA            | Y                         | Y                          | -                         |
+| DB2                    | GA (Beta)     | Y                         | Y                          | 11.x                      |
+| DM                     | GA (Beta)     | Y                         | Y                          | 8.x                       |
+| Doris                  | GA (Beta)     | Y                         | Y                          | 1.x                       |
+| DynamoDB               | GA            | Y                         | Y                          | -                         |
+| Elasticsearch          | GA            | Y                         | Y                          | 7.x                       |
+| Greenplum              | GA (Beta)     | Y                         | Y                          | 5.x and above             |
+| HBase                  | GA            | N                         | Y                          | 1.4+                      |
+| Hive                   | GA            | Y                         | Y                          | 2.x                       |
+| Hologres               | GA (Beta)     | Y                         | Y                          | -                         |
+| Kafka                  | GA            | Y                         | Y                          | 0.8.x, 0.9.x, 0.10.x, 2.x |
+| MaxCompute             | GA            | Y                         | N                          | -                         |
+| MariaDB                | GA (Beta)     | Y                         | Y                          | -                         |
+| MongoDB                | GA            | Y                         | N                          | 3.4 and above             |
+| MySQL                  | GA            | Y                         | Y                          | 5.x, 8.x                  |
+| Oracle                 | GA (Beta)     | Y                         | Y                          | -                         |
+| OSS                    | GA            | Y                         | Y                          | -                         |
+| PolarDB for MySQL      | GA            | Y                         | Y                          | -                         |
+| PolarDB for PostgreSQL | GA            | Y                         | Y                          | -                         |
+| PostgreSQL             | GA            | Y                         | Y                          | 9.4 and above             |
+| Redis                  | GA            | N                         | Y                          | -                         |
+| Redshift               | GA (Beta)     | Y                         | Y                          | -                         |
+| RestApi                | GA            | Y                         | N                          | -                         |
+| SLS (LogHub)           | GA            | Y                         | N                          | -                         |
+| SQL Server             | GA            | Y                         | Y                          | 2012 and above            |
+| StarRocks              | GA (Beta)     | Y                         | Y                          | 2.5                       |
+| TiDB                   | GA (Beta)     | Y                         | Y                          | -                         |
 ### Real-Time Sync
-| Data Source | Release Level | Real-Time Single-Table Read | Real-Time Multi-Table Read | Real-Time Write | Supported Versions |
-| --------------- | --- | ---- | ---- | ---- | ---- |
-| Singdata Lakehouse | GA | N | N | Y | - |
-| AutoMQ                 | GA   | Y     | N     | N   | -             |
-| Kafka | GA | Y | N | Y | 0.8.x, 0.9.x, 0.10.x, 2.x |
-| MySQL | GA | Y | Y | N | 5.x, 8.x |
-| PolarDB for MySQL      | GA   | Y     | Y     | N   | -         |
-| PolarDB for PostgreSQL | GA   | Y     | Y     | N   | -       |
-| SQL Server | GA | Y | Y | N | SQL Server 2016 Service Pack 1 (SP1) and above |
+| Data Source            | Release Level | Real-Time Single-Table Read | Real-Time Multi-Table Read | Real-Time Write | Supported Versions                             |
+| ---------------------- | ------------- | --------------------------- | -------------------------- | --------------- | ---------------------------------------------- |
+| Singdata Lakehouse     | GA            | N                           | N                          | Y               | -                                              |
+| AutoMQ                 | GA            | Y                           | N                          | N               | -                                              |
+| Kafka                  | GA            | Y                           | N                          | Y               | 0.8.x, 0.9.x, 0.10.x, 2.x                      |
+| MySQL                  | GA            | Y                           | Y                          | N               | 5.x, 8.x                                       |
+| PolarDB for MySQL      | GA            | Y                           | Y                          | N               | -                                              |
+| PolarDB for PostgreSQL | GA            | Y                           | Y                          | N               | -                                              |
+| SQL Server             | GA            | Y                           | Y                          | N               | SQL Server 2016 Service Pack 1 (SP1) and above |
 ^

package/bin/skills/lakehouse-doc-en/references/data_catalog.md CHANGED Viewed

@@ -4,7 +4,7 @@
 Data Catalog, also known as the data asset map, provides powerful data search and display capabilities, designed to help users more easily find, understand, and use data. It supports two modes: Data Search mode and Data Management mode. Data Search mode allows users to search data directly, while Data Management mode allows users to browse and manage data tables through a directory structure. With Data Catalog, you can manage and utilize data resources more efficiently.
-![](.topwrite/assets/image_1735621816126.png)
+![](/.topwrite/assets/image_1780673609913.png)
 * Asset Details: Displays the total data assets of the current tenant.
 * Search Box: Click to enter the data search results page.
@@ -16,11 +16,11 @@ Data Catalog, also known as the data asset map, provides powerful data search an
 Enter keywords in the search box on the Data Catalog homepage to enter the search results page. The search function supports searching by the name and description of object types (Table, View, Materialized View). The search results page provides various filtering options, including object type, workspace/Schema, creation time, owner, etc., as well as sorting options by name, creation time, update time, etc.
-![](.topwrite/assets/image_1735638515501.png)
+![](/.topwrite/assets/image_1780673622966.png)
 On the search results filtering: supports filtering by object type, workspace/schema, creation time, and owner; also supports filtering by name, creation time, and update time.
-![](.topwrite/assets/image_1735638559254.png)
+![](/.topwrite/assets/image_1780673651359.png)
 Click the table name on the search results page to navigate to the corresponding table details page.
@@ -28,55 +28,53 @@ Click the table name on the search results page to navigate to the corresponding
 The Data Management page displays all data assets that the current user has permission to manage under the service instance in a directory format. Click **Data Management** from the homepage to enter the Data Management page, which displays the list of workspaces that the current user has permissions to under the service.
-![](.topwrite/assets/536c830f76/6d452f0b5d750f3a42ac150d3d2f2a46a1b06216.png)
+![](/.topwrite/assets/image_1780673677696.png)
+^
 ### Workspace Level
 At the workspace level, you can see the list of all Schemas under that workspace. Click the directory tree on the left to expand and view the hierarchy. The top area displays basic workspace information, such as source, creation time/modification time, owner, etc. The information area presents specific Schema information, including name, creation time, update time, owner, etc.
-Each workspace has a default information_schema.
-Schemas under a workspace include two categories: internally created and externally created.
+Each workspace has a default information\_schema.
-![](.topwrite/assets/536c830f76/13c0c5b0de5cdb544d9dfb30208ecd7897706983.png)
+Schemas under a workspace include two categories: internally created and externally created.![](/.topwrite/assets/image_1780673705918.png)
 Users can create schema information under a workspace through a visual interface. Click the question mark next to the title to view help documentation for creating objects.
-![](.topwrite/assets/536c830f76/ca874a7a019814f4b59811207177035046a8f740.png =297)
+![](/.topwrite/assets/image_1780673717394.png =372)
 ### Schema Level
-After clicking a specific Schema, you can drill down to the Schema's details page. At the Schema level, you can view all object information managed under the Schema, with specific objects organized by object type. The system currently supports three object types: Table, View, and Materialized View.
-![Schema Level](.topwrite/assets/536c830f76/1c37e9e34e320d58f7d975ad833c5686162e1159.png)
+After clicking a specific Schema, you can drill down to the Schema's details page. At the Schema level, you can view all object information managed under the Schema, with specific objects organized by object type. The system currently supports three object types: Table, View, and Materialized View.![](/.topwrite/assets/image_1780673754518.png =728)
 Objects can be created directly under a Schema, supporting both script-based creation and visual creation. The system has built-in templates for different objects to help users better understand Lakehouse syntax.
-![Create Object Template](.topwrite/assets/536c830f76/79ef0ae4339fac60c009a9508b495ac8f3cbd090.png =529)
+![](/.topwrite/assets/image_1780673779657.png =646)
 ## Table Details Page
-The table details page displays all detailed information for tables in the Singdata Lakehouse library, including field information, data preview, data lineage, job history, uploads, etc. The details page is divided into two parts: the top area displays the table name, owner, and some quick table operations; the information area contains six major sections: Details, Fields, Preview, Lineage, Jobs, and Uploads.
-![](.topwrite/assets/536c830f76/441e6d94ae7efacb852c089f4a4aa0871cc04c3f.png)
+The table details page displays all detailed information for tables in the Singdata Lakehouse library, including field information, data preview, data lineage, job history, uploads, etc. The details page is divided into two parts: the top area displays the table name, owner, and some quick table operations; the information area contains six major sections: Details, Fields, Preview, Lineage, Jobs, and Uploads.![](/.topwrite/assets/image_1780673802254.png)
 ### Top Functional Area
 The top area displays the full structure of the current table (i.e., the corresponding workspace/schema/table name information), row count/storage size, creation time/update time, owner, and other basic information. The top area also provides an **Upload** function, supporting the uploading of local files to the Singdata Lakehouse platform.
-![Top Functional Area](.topwrite/assets/536c830f76/67ea57ab34dd3b76f3ab553faf2a258f582864bc.png)
+^
+![](/.topwrite/assets/image_1780673850037.png =695)
-### Details
+DDL preview：
 The Details tab displays the DDL statement of the current table, supporting one-click copy. It also supports one-click navigation to the permission management page for permission authorization.
-![](.topwrite/assets/536c830f76/f081a3d6f3b91bec4de88b3ee67a10bd42003355.png)
+^
 ### Fields
 The **Fields** tab displays the field names, types, descriptions, and other information for the current table. If there is primary key information, it can also display the primary key and standardized labels for the fields.
-![](.topwrite/assets/536c830f76/47b33b650c6c77e2de4ff2df037836580e4be390.png)
+![](/.topwrite/assets/image_1780673897761.png =652)
 ### Preview
@@ -84,26 +82,26 @@ In the Data Preview tab, you can preview the first 100 rows of data in the curre
 Data preview requires the user to manually select a compute cluster participating in the query to display the preview data.
-![](.topwrite/assets/536c830f76/c5efa313984239360d57373d1912d37f030c7345.png)
+^
 ### Lineage
 In the Data Lineage tab, you can view the upstream and downstream dependencies of the current table. The lineage relationships here are generated based on code parsing of the corresponding task that produces this table, and belong to relationships from the "definition perspective."
-![](.topwrite/assets/536c830f76/3e8ffc557a0d11d362aef2a576257b5b023f4e78.png)
+^
 Click on a specific upstream or downstream table node to view more detailed information:
-![](.topwrite/assets/536c830f76/0820ab62e0868ea1f873defc635eb4577142a084.png)
+^
 ### Jobs
 Under the Jobs tab, you can view the SQL jobs of the tasks that produce the table. By clicking on the job ID, you can further view the job details.
-![](.topwrite/assets/536c830f76/b18ee57b085317472a1abfadb1777bda2fab3c36.png)
+^
 ### Uploads
 Under the Uploads tab, all historical records uploaded to the current table via the **Upload** function are displayed.
-![](.topwrite/assets/536c830f76/89ad928925aedfc753ac5eca1b07411286234857.png)
+^

package/bin/skills/lakehouse-doc-en/references/data_privacy.md CHANGED Viewed

@@ -13,11 +13,14 @@ When the system processes your data queries, the following data will be sent to
 **Data**:
-* Column value data with indexing enabled (You can prevent specific column data from being sent to the large language model by disabling column value indexing)  ![](.topwrite/assets/20250219-130449.jpeg)
+* Column value data with indexing enabled (You can prevent specific column data from being sent to the large language model by disabling column value indexing)
+![](.topwrite/assets/20250115-094842.jpeg)
 **Document Segmentation**:
-The system segments the document into vectorized chunks through semantic parsing. These vectorized segments are then processed by the Large Language Model (LLM) to enable intelligent question-answering capabilities.
+* The system segments document content into chunks
+* These document segments are sent to the Large Language Model to enable intelligent question-answering
 ## Data Protection Measures