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

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

@@ -9,30 +9,30 @@ You can create a new sync task from both the workspace and the development entry
 * Create from Workspace
   Through the "Workspace" entry in the console, select "New Batch Sync" or "Real-time Sync Task" under the "New" button on the right.
 
-  ![](.topwrite/assets/image_1740137267351.png =771)
+  :-: ![](.topwrite/assets/image_1740137267351.png =771)
 
 * Create from Development Entry
   You can enter the "Development" page and select to create a new sync task in the specified directory in the task area.
 
-  ![](.topwrite/assets/image_1740137285198.png =488)
+  :-: ![](.topwrite/assets/image_1740137285198.png =488)
 
 ## Batch Sync Task Development
 
 **Step 1: Create a New Batch Data** **Sync** **Task**
 Create an Batch sync task with a specified name in the specified task save location.
 
-![](.topwrite/assets/image_1740137311337.png =485)
+:-: ![](.topwrite/assets/image_1740137311337.png =485)
 
 The system will generate the sync task and open the data sync task editor in the right area for user editing:
 
-![](.topwrite/assets/image_1690125934293.png =640)
+:-: ![](.topwrite/assets/image_1690125934293.png =640)
 
 **Step 2: Define the Sync Task**
 
 * Select Source and Target Data Sources and Data Objects
   On the data source side, select an existing data source or create a new data source as the data source and specify the data object to be synchronized. On the data target side, select an existing data source or create a new data source as the target data. The write object of the target data supports specifying the data object or quickly creating it based on the source object.
 
-  ![](.topwrite/assets/image_1740137397919.png =640)
+  :-: ![](.topwrite/assets/image_1740137397919.png =640)
 
   After determining the source object and target object, the data sync task will generate a field mapping between the source object and the target object. By default, the same row mapping rule is used, and the mapping between fields can be adjusted by dragging. It supports adding constant fields as source table fields for mapping and writing.
 
@@ -40,7 +40,7 @@ The system will generate the sync task and open the data sync task editor in the
   * Task concurrency, can be set to a minimum of 1 and a maximum of 10
   * Task sync rate, can be set to a minimum of 1MB/S, with no maximum limit
 
-    ![](.topwrite/assets/image_1740137412611.png =514)
+    :-: ![](.topwrite/assets/image_1740137412611.png =514)
 
 * Advanced Configuration of the Task
   The advanced configuration area usually does not need to be configured and can be left blank. You can also expand to set advanced parameters for the task, such as adjusting the memory specifications used by the task. The supported parameters are as follows. For specific settings, please contact technical support.
@@ -50,13 +50,13 @@ The system will generate the sync task and open the data sync task editor in the
 **Step 3: Test the Sync Task**
 Click "Run" on the development task interface to test the sync task. Observe the task execution status and logs, query the data changes in the target table, and verify whether the sync task is executed correctly.
 
-![](.topwrite/assets/image_1740137443153.png =640)
+:-: ![](.topwrite/assets/image_1740137443153.png =640)
 
 **Step 4: Set Scheduling and Deploy to Production**
 After the scheduling configuration is successful, you can click the "Submit" button of the task to deploy it to the scheduling system for periodic execution.
 
-![](.topwrite/assets/image_1740137457830.png =640)
+:-: ![](.topwrite/assets/image_1740137457830.png =640)
 
 View and maintain the published sync tasks in the Operations Center
 
-![](.topwrite/assets/image_1740137476462.png =640)
+:-: ![](.topwrite/assets/image_1740137476462.png =640)

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

@@ -12,7 +12,7 @@ Answer: The cost of data sync tasks is generally composed of two categories: har
 
 ### Question: What data sources are currently supported for offline sync?
 
-Answer: On the task configuration page, when selecting the source and target, all supported data source types are listed in full. If no data source is available, click the **+** button to create a new one first, then use it. Offline sync data sources can be freely combined in pairs to build a rich variety of sync links. See: [Data Source Management](config-datasource.md)
+Answer: On the task configuration page, when selecting the source and target, all supported data source types are listed in full. If no data source is available, click the + button to create a new one first, then use it. Offline sync data sources can be freely combined in pairs to build a rich variety of sync links. See: [Data Source Management](config-datasource.md)
 
 ^
 
@@ -82,7 +82,7 @@ Solution: Typically, the following solutions are available:
 
 * Refer to the heap memory overflow solution and adjust the `taskmanager.memory.process.size` parameter.
 * Separately adjust the task off-heap memory size by adjusting the `taskmanager.memory.task.off-heap.size` parameter, e.g., 256m or 512m.
-* If the data source supports setting batch size, reduce the configured value appropriately. **However, note that this may lead to reduced sync efficiency.**
+* If the data source supports setting batch size, reduce the configured value appropriately. **However, note that this may lead to reduced sync efficiency**.
 
 ### Question: How to resolve the error `CZLH-67000:Out of Memory undefined: could not allocate block of size 262KB (1.0GB/1.0GB used)`?
 

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

@@ -12,7 +12,7 @@ This guide will help you import large amounts of data from public URL Parquet fi
 
 Script download address: <https://github.com/yunqiqiliang/nyc-taxi-data-clickzetta>
 
-## 1. Install [Singdata SQLLine](https://doc.singdata.com/zh-CN/connect-with-cli)
+## 1. Install [Singdata SQLLine](connect-with-cli.md)
 
 ## 2. Install [R](https://www.r-project.org/)
 

package/bin/skills/lakehouse-doc-en/references/bulkloadv1-python-sdk.md

@@ -20,7 +20,7 @@ pip uninstall clickzetta-connector clickzetta-connector-python clickzetta-sqlalc
 pip show clickzetta-connector clickzetta-sqlalchemy clickzetta-ingestion-python clickzetta-ingestion-python-v2 clickzetta-connector-python
 ```
 
-Install the latest version (requires Python >= 3.7):
+Install the latest version (requires Python >= 3.10):
 
 ```bash
 pip install clickzetta-connector -U -i https://pypi.org/simple/
@@ -68,7 +68,7 @@ conn = connect(
     instance='your_instance',
     workspace='your_workspace',
     schema='public',
-    vcluster='default'
+    vcluster='DEFAULT'
 )
 
 bulkload_stream = conn.create_bulkload_stream(schema='public', table='bulkload_test')
@@ -96,7 +96,7 @@ bulkload_stream.commit()
        instance='your_instance',
        workspace='your_workspace',
        schema='public',
-       vcluster='default'
+       vcluster='DEFAULT'
    )
    ```
 

package/bin/skills/lakehouse-doc-en/references/chart-auto-refresh-guide.md

@@ -1,5 +1,3 @@
-^
-
 # Chart Auto-Refresh Settings
 
 ## Feature Overview
@@ -16,10 +14,10 @@ Charts in dashboards support setting an auto-refresh interval. The system will a
 
 ## How to Use
 
-| Step       | Description                                       | Screenshot                                             |
-| ---------- | ------------------------------------------------- | ------------------------------------------------------ |
-| Select chart settings | Click "Dashboard" and select the chart you want to configure | ![](/.topwrite/assets/image_1779185744966.png =237) |
-| Set refresh interval | Default refresh every 24 hours; adjustable based on business needs | ![](/.topwrite/assets/image_1779185773256.png =247) |
+| Step                  | Description                                                        | Screenshot                                          |
+| --------------------- | ------------------------------------------------------------------ | --------------------------------------------------- |
+| Select chart settings | Click "Dashboard" and select the chart you want to configure       | ![](/.topwrite/assets/image_1780901921376.png =241) |
+| Set refresh interval  | Default refresh every 24 hours; adjustable based on business needs | ![](/.topwrite/assets/image_1780901941736.png =251) |
 
 ## **Notes**
 
@@ -28,3 +26,11 @@ Charts in dashboards support setting an auto-refresh interval. The system will a
 2\. During refresh, the system re-executes the query corresponding to that chart to retrieve the latest data
 
 3\. It is recommended to set refresh intervals reasonably based on data update frequency, avoiding excessively frequent refreshes that cause unnecessary resource consumption
+
+## Related Documentation
+
+* [Scheduled Tasks](scheduled_task.md) — Automatically execute analysis on a schedule and push results
+* [Dashboard Version Management](dashboard-version-management-guide.md) — Manage multi-version history of dashboards
+* [Conversational Data Analytics (Analytics Agent)](datagpt_introduction.md) — Return to feature overview
+
+^

package/bin/skills/lakehouse-doc-en/references/clickzetta-sample-data.md

@@ -213,7 +213,7 @@ ORDER BY trips DESC;
 | `date_processed` | timestamp_ltz | Vector processing timestamp |
 
 **Use cases**:
-- Experience vector similarity retrieval (the `<=>` cosine distance operator)
+- Experience vector similarity retrieval (the `cosine_distance` function)
 - Build a RAG (Retrieval-Augmented Generation) Q&A system based on product documentation
 - Learn how to use the `AI_EMBEDDING` function together with vector indexes
 
@@ -224,7 +224,7 @@ SELECT
     filename,
     type,
     text,
-    embeddings <=> AI_EMBEDDING('动态表是什么') AS distance
+    cosine_distance(embeddings, AI_EMBEDDING('ai_gateway_conn:text-embedding-v4', 'What is a dynamic table')) AS distance
 FROM clickzetta_sample_data.clickzetta_doc_kb.dashscope_clickzetta_elements
 ORDER BY distance ASC
 LIMIT 5;
@@ -236,4 +236,4 @@ LIMIT 5;
 - [TPC-H Performance Benchmark](tpch-benchmark.md)
 - [Table Stream](om-table-stream.md)
 - [Vector Index](om-inverted-index.md)
-- [AI_EMBEDDING Function](ai_embedding.md)
+- [AI_EMBEDDING Function](sql_functions/ai_embedding.md)

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

@@ -2,7 +2,7 @@ When configuring a workspace, you can enable the "Mandatory Code Review" feature
 
 ## Prerequisites
 
-Only users with the workspace administrator (workspace_admin) role can enable or disable the mandatory code review process.
+Only users with the workspace administrator (workspace\_admin) role can enable or disable the mandatory code review process.
 
 ## Steps
 
@@ -10,7 +10,6 @@ Only users with the workspace administrator (workspace_admin) role can enable or
 
 * Enable the code review process when creating a new workspace.
 * For existing workspaces -> Click to enter the details page -> Edit, and enable the code review feature.
-  ![](/.topwrite/assets/image_1775099278363.png)
 
 **2. Configure the Code Review Approval Flow**
 
@@ -19,16 +18,13 @@ Click Approval -> Approval Flow -> Select the code review flow for the target wo
 Under "Approval", configure the approval roles/users for the code review flow. These roles/users will be the personnel who need to participate in code review when code is submitted in the current workspace.
 
 > Only roles with development permissions can perform approvals
-  ![](/.topwrite/assets/image_1775099287191.png)
 
 **3. Submit Code for Review**
 
 After enabling mandatory code review, any submission action will trigger a "Code Review" approval ticket. Once the approver approves, the code will be published to the production environment. If the approver rejects it, you need to modify and resubmit.
-  ![](/.topwrite/assets/image_1775099296124.png)
 
 **4. Approval**
 
 After code submission, the approver needs to review it.
 
 Click Approval -> Under the Approval tab, find the target task and perform the relevant actions.
-  ![](/.topwrite/assets/image_1775099305006.png)

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

@@ -18,15 +18,9 @@ You can create a composite task through any of the following paths:
 
 * Task Development: Task tab → New Task → Select "Composite Task"
 
-  ![](.topwrite/assets/image_1752130018729.png =420)
-
 * Task Group Details page: Inside a task group → Add New Task → Select "Composite Task"
-  
-  ![](.topwrite/assets/image_1752130033606.png =680)
 
 * Workspace: Top navigation bar → New Task → Select "Composite Task"
-  
-  ![](.topwrite/assets/image_1752130048252.png =680)
 
 ### Basic Information
 
@@ -36,20 +30,19 @@ In the composite task creation dialog, fill in the required fields — same as f
 * Folder: The folder to place the task in. Required.
 * Task Group: Optionally assign the task to a task group by selecting a specific task group name.
 
-  ![](.topwrite/assets/image_1752130064673.png =680)
+  ^
 
 ## Core Feature Guide
 
 ### Subtask Management (Canvas Mode)
 
 Composite tasks use a **canvas** (DAG diagram) to display subtask nodes and support the following operations:
-![](.topwrite/assets/image_1752130101512.png =680)
 
 #### Adding Subtasks
 
 * **Entry point**: Canvas toolbar → "New Subtask" → Select a task type (only periodic tasks are supported: offline synchronization, SQL, etc.; **real-time tasks are not supported**). You can add a subtask by clicking the task type or dragging it onto the canvas.
 
-  ![](.topwrite/assets/image_1752130110716.png =360)
+  ^
 
 * **Default state**: Newly added subtasks have no dependencies by default. You need to configure dependencies manually — either by drawing connections on the canvas or through the subtask detail configuration.
 
@@ -75,18 +68,16 @@ Composite tasks use a **canvas** (DAG diagram) to display subtask nodes and supp
 
 The scheduling strategy for a composite task is managed through a combination of **global configuration** (at the composite task level) and **local configuration** (at the subtask level). Subtasks inherit the composite task's global configuration by default, but can also be configured individually. When a local configuration exists, it takes precedence. Key configuration items:
 
-| Configuration Item | Global Configuration (Composite Task)                                    | Local Configuration (Subtask)                                                                        |
-| ------------------ | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
-| Scheduling Time    | Required; supports Cron expressions. Subtasks cannot set this independently. | None. Subtasks follow the composite task's global scheduling time and run at the same frequency.  |
-| Instance Rerun     | Global setting (rerun count, interval). Subtasks inherit by default.     | Optional override of global settings (only supported for specific task types such as SQL).           |
-| Task Priority      | Global setting (default value).                                          | Optional individual setting (overrides global; only supported for SQL nodes).                        |
-| Self-dependency    | Global setting (controls composite task cycle dependency).               | None. Subtask self-dependency is indirectly achieved through the composite task's global self-dependency. |
+| Configuration Item | Global Configuration (Composite Task)                                        | Local Configuration (Subtask)                                                                             |
+| ------------------ | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| Scheduling Time    | Required; supports Cron expressions. Subtasks cannot set this independently. | None. Subtasks follow the composite task's global scheduling time and run at the same frequency.          |
+| Instance Rerun     | Global setting (rerun count, interval). Subtasks inherit by default.         | Optional override of global settings (only supported for specific task types such as SQL).                |
+| Task Priority      | Global setting (default value).                                              | Optional individual setting (overrides global; only supported for SQL nodes).                             |
+| Self-dependency    | Global setting (controls composite task cycle dependency).                   | None. Subtask self-dependency is indirectly achieved through the composite task's global self-dependency. |
 
 **Example**: If the composite task global setting is "3 reruns with a 5-minute interval," and a subtask is individually configured with "5 reruns," that subtask will use "5 reruns with a 5-minute interval."
 
-![](.topwrite/assets/image_1752130126629.png =680)
-
-![](.topwrite/assets/image_1752130133390.png =680)
+^
 
 ### Parameter Management (Composite Task → Subtask Propagation)
 
@@ -94,9 +85,7 @@ The scheduling strategy for a composite task is managed through a combination of
 
 * **Entry point**: Composite task detail page → Click "Parameters" → Add parameters in the dialog (e.g., `composite_task_param`):
 
-  ![](.topwrite/assets/image_1752130143435.png =680)
-
-  ![](.topwrite/assets/image_1752130151838.png =680)
+  ^
 
 * **Scope**: Parameters are only valid within the current composite task. Parameters are isolated between different composite tasks.
 
@@ -104,7 +93,7 @@ The scheduling strategy for a composite task is managed through a combination of
 
 In a subtask's parameter configuration, if the parameter name matches a parameter defined in the composite task, the system automatically recognizes it and prompts you to select the value source. To use the globally defined composite task parameter, select "Composite Task" as the value source; otherwise, select "Task".
 
-![](.topwrite/assets/image_1752130161305.png =680)
+^
 
 In subtask code, you can reference parameters using `${parameter_name}`. **Example** (SQL subtask):
 
@@ -124,21 +113,19 @@ SELECT * FROM user_log WHERE dt = '${composite_task_param}'
 
 * **Entry point**: Composite task detail page → "Submit."
 
-  ![](.topwrite/assets/image_1752130174992.png =680)
-
 ## Operations and Monitoring
 
 ### Composite Task Operations
 
 Composite tasks appear in the Operations Center alongside other periodic tasks and support similar operations such as pause, data backfill, and offline.
 
-![](.topwrite/assets/image_1752130184652.png =680)
+^
 
-| Operation      | Description                                                                                                                                                                                    |
-| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pause/Resume   | After pausing, the composite task and its subtasks stop scheduling. After resuming, execution continues according to the current configuration.                                                |
-| Data Backfill  | Select a time range → The composite task generates backfill instances as a whole according to scheduling rules (including all subtask instances).                                               |
-| Offline        | After going offline, the task no longer schedules. Check for downstream dependencies — if any exist, you cannot go offline directly and must use the "Offline (including downstream)" feature. |
+| Operation     | Description                                                                                                                                                                                    |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pause/Resume  | After pausing, the composite task and its subtasks stop scheduling. After resuming, execution continues according to the current configuration.                                                |
+| Data Backfill | Select a time range → The composite task generates backfill instances as a whole according to scheduling rules (including all subtask instances).                                              |
+| Offline       | After going offline, the task no longer schedules. Check for downstream dependencies — if any exist, you cannot go offline directly and must use the "Offline (including downstream)" feature. |
 
 ### Composite Task Instance Operations
 
@@ -157,23 +144,23 @@ In the Instance Operations tab, composite task instances are listed alongside ot
 
 #### Instance Operations
 
-| Operation              | Supported States                      | Behavior                                                                                                                                          |
-| ---------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Rerun                  | Any terminal state (failed/succeeded) | Reruns the entire composite task. Subtasks generate new instances according to their respective rerun rules. Partial subtask selection is not supported. |
-| Mark Success/Failure   | Not Started / Terminal state          | Forces the composite task and all subtask instance statuses to change to succeeded or failed.                                                     |
-| Terminate              | Running                               | Terminates all running or not-started subtask instances and sets their status to failed.                                                          |
+| Operation            | Supported States                      | Behavior                                                                                                                                                 |
+| -------------------- | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Rerun                | Any terminal state (failed/succeeded) | Reruns the entire composite task. Subtasks generate new instances according to their respective rerun rules. Partial subtask selection is not supported. |
+| Mark Success/Failure | Not Started / Terminal state          | Forces the composite task and all subtask instance statuses to change to succeeded or failed.                                                            |
+| Terminate            | Running                               | Terminates all running or not-started subtask instances and sets their status to failed.                                                                 |
 
 ### Monitoring and Alerts
 
 In monitoring and alerts, composite tasks are categorized under periodic scheduling tasks. Existing monitoring items such as "Task Instance Execution Failure" and "Periodic Task Instance Completion Time" apply to composite tasks as well. You can configure monitoring rules for composite tasks the same way you would for regular SQL periodic tasks.
 
-![](.topwrite/assets/image_1752131374833.png =680)
+^
 
 ### Triggering Data Quality Rule Checks
 
 When configuring data quality rules, you can select a composite task as the scheduling trigger in the rule execution trigger settings, as shown below. You can select a specific subtask to trigger the check; if "Subtask" is left blank, the check is triggered after the entire composite task completes.
 
-![](.topwrite/assets/image_1752131279717.png =680)
+^
 
 ## Notes
 
@@ -182,11 +169,13 @@ When configuring data quality rules, you can select a composite task as the sche
 3. **Version management**: Composite tasks only support "submission versions" (no saved versions) and do not currently support version rollback.
 4. **Task dependencies**: Within a task group, a composite task exists as a whole unit. Internal subtasks cannot be added individually to the task group, and dependencies are between the composite task as a whole and other tasks. Internal subtasks of a composite task cannot depend on other tasks in the task group, nor can they be depended upon by other tasks in the task group.
 
----
+***
 
 ## Related Documentation
 
-- [Task Parameters](task_param.md) — Concepts and configuration for composite task parameters
-- [Task Parameter Syntax Reference](task_param_reference.md) — Full syntax for time expressions and built-in parameters
-- [Task Group](task_group.md) — Using task group parameters to share parameters across composite tasks
-- [Task Development and Scheduling](task-develop.md) — Development and scheduling configuration for SQL subtasks
+* [Task Parameters](task_param.md) — Concepts and configuration for composite task parameters
+* [Task Parameter Syntax Reference](task_param_reference.md) — Full syntax for time expressions and built-in parameters
+* [Task Group](task_group.md) — Using task group parameters to share parameters across composite tasks
+* [Task Development and Scheduling](task-develop.md) — Development and scheduling configuration for SQL subtasks
+
+^

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

@@ -2,7 +2,7 @@
 
 ## Python Environment Setup
 
-This guide includes a data generator and several examples, requiring Python 3.8, Java, and some other libraries and utilities.
+This guide includes a data generator and several examples, requiring Python 3.10, Java, and some other libraries and utilities.
 
 To set up these dependencies, we will use conda.
 
@@ -22,7 +22,7 @@ dependencies:
   - pandas=1.5.3
   - pip=23.0.1
   - pyarrow=10.0.1
-  - python=3.8.20
+  - python=3.10
   - python-confluent-kafka
   - python-dotenv=0.21.0
   - python-rapidjson=1.5
@@ -554,20 +554,20 @@ You will use the [Singdata Lakehouse Studio](https://accounts.clickzetta.com/) w
 
 Navigate to Development -> Tasks, click `+` to create a new workspace and worksheet task, then select SQL Worksheet
 
-:-: ![](.topwrite/assets/image_1736147176792.png =481)
+
 
 Create a workspace to store all tasks and code for this project. Workspace name: 01\_Demo\_Data\_Ingest
 
 ^
 
-:-: ![](.topwrite/assets/image_1736147168499.png =474)
+
   
 
 Create the first task, select SQL as the type. Workspace task name: 01\_Setup\_Environment
 
 ^
 
-:-: ![](.topwrite/assets/image_1736147159234.png =460)
+
 
 ###
 
@@ -639,7 +639,7 @@ The config-ingest.json file contains your account login information for Singdata
   "instance": "Please enter your instance ID",
   "workspace": "Please enter your workspace, e.g., gharchive",
   "schema": "Please enter your schema, e.g., public",
-  "vcluster": "Please enter your virtual cluster, e.g., default_ap",
+  "vcluster": "Please enter your virtual cluster, e.g., DEFAULT_AP",
   "sdk_job_timeout": 10,
   "hints": {
     "sdk.job.timeout": 3,
@@ -654,16 +654,13 @@ The config-ingest.json file contains your account login information for Singdata
 
 Navigate to Management -> Data Sources, click "New Data Source" and select Postgres to create a Postgres data source, so that Postgres can be accessed by Singdata Lakehouse.
 
-:-: ![](.topwrite/assets/image_1736147121735.png =510)
 
 * Data Source Name: ingest\_demo\_from\_pg
 * Connection Parameters: Same as the environment connection parameters in the database environment settings.
 * Please make sure to configure the correct time zone of the database to avoid data synchronization failure.
 
-:-: ![](.topwrite/assets/image_1736147111452.png =484)
 
 Once the environment is created, it can be used.
 
-:-: ![](.topwrite/assets/image_1736147099360.png =481)
 
 Test the connection, and if it prompts success, it means the configuration is successful.

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

@@ -18,11 +18,10 @@ Download the code for this guide from the [GitHub repository](https://github.com
 
 Add the project directory to your VS Code workspace.
 
-:-: ![](.topwrite/assets/image_1736229919125.png =512)
 
 ##### Modify Parameters
 
-Rename the file `config/config-ingest-sample.json` to `config/config-ingest.json`, and modify the [parameter values](https://uat-doc.singdata.com/JDBC-Driver) in `config-ingest.json`.
+Rename the file `config/config-ingest-sample.json` to `config/config-ingest.json`, and modify the [parameter values](jdbc-driver.md) in `config-ingest.json`.
 
 ```JSON
 {
@@ -43,9 +42,8 @@ Rename the file `config/config-ingest-sample.json` to `config/config-ingest.json
 
 ##### Bulkload
 
-Run `BulkLoadFile.java` in VS Code:
+Run `BulkLoadFile.java` in VS Code.
 
-:-: ![](.topwrite/assets/image_1736230356428.png =470)
 
 ```JAVA
 import com.clickzetta.client.BulkloadStream;
@@ -400,17 +398,13 @@ throw new ArithmeticException(bulkloadStream.getErrorMessage());
 
 ^
 
-View execution results:
+View execution results.
 
-:-:
-![](.topwrite/assets/image_1736230582408.png =474)
 
 ##### Realtime Ingestion
 
-Run `StreamingInsert.java` in VS Code:
+Run `StreamingInsert.java` in VS Code.
 
-:-:
-![](.topwrite/assets/image_1736230796054.png =477)
 
 ```JAVA
 import com.clickzetta.client.ClickZettaClient;

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

@@ -12,11 +12,9 @@ Existing Kafka data source with high real-time requirements for data synchroniza
 
 Navigate to Development -> Tasks, click "+", select "Real-time Sync", and create a new "Real-time Sync" job.
 
-:-: ![](.topwrite/assets/image_1736319394961.png =740)
 
-Main configuration as follows:
+Main configuration as follows.
 
-:-: ![](.topwrite/assets/image_1736319702232.png =740)
 
 ^
 
@@ -28,13 +26,11 @@ Then select the Lakehouse target on the right, choose an existing data table, or
 
 In the "Create Data Table" SQL code, change the table name to "target\_table\_from\_kafka".
 
-:-: ![](.topwrite/assets/image_1736321482644.png =740)
 
 ^
 
 In the "Field Mapping Configuration" area, Kafka Topic built-in fields will be used for data field mapping by default. If the message format in the Topic is JSON, you can also use the new calculated column method to parse the content in the value field using JSONPath rules. For example, extract the accountId field in the \_\_value\_\_ from the source topic and write it into the target \_\_value\_\_ field as shown in the figure below.
 
-:-: ![](.topwrite/assets/image_1736322127793.png =740)
 
 ^
 
@@ -44,25 +40,20 @@ In the "Sync Rule Configuration", set the maximum concurrency for synchronizatio
 
 After checking that the field mapping meets expectations, set the required information such as "Cluster" in the configuration, click "OK", and then click "Save" to save the task configuration.
 
-:-: ![](.topwrite/assets/image_1736322224165.png =740)
 
 Real-time sync tasks currently do not support direct test runs. You need to submit and publish them, then check if the results are normal.
 
-:-: ![](.topwrite/assets/image_1736322037109.png =740)
 
 #### Next Steps
 
 * In the Operations Center, start the real-time sync task, observe the task running metrics, and verify if the data synchronization results are normal.
 
-  :-: ![](.topwrite/assets/image_1736322337162.png =740)
 
 * For the first start, select the "Stateless Start" method.
 
-  :-: ![](.topwrite/assets/image_1736322414065.png =740)
 
 * After a normal start, you can see the following monitoring metrics, indicating that the sync task is running normally.
 
-  :-: ![](.topwrite/assets/image_1736322603085.png =740)
 
 * Spot check the data in the target table and verify it against the source to see if it meets expectations.
 

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

@@ -16,7 +16,6 @@ Suitable for directly uploading smaller local files (not larger than 2GB) such a
 
 Navigate to Data -> Data Directory, click "Upload Data" to import local files (CSV files generated in the test data generation section) into the table.
 
-:-: ![](.topwrite/assets/image_1736146842294.png =519)
 
 ##### Import Data
 
@@ -27,11 +26,9 @@ Click "Upload Data":
 * Select "Create New Table", table name: lift\_tuckets\_import\_by\_studio\_web
 * Virtual compute cluster created in the Singdata Lakehouse setup section
 
-:-: ![](.topwrite/assets/image_1736146857816.png =513)
 
 After clicking "Next", check if the automatic settings for the uploaded data are correct. If the data preview meets expectations, the automatic settings are correct. Click "Confirm" to complete the data upload.
 
-:-: ![](.topwrite/assets/image_1736146867287.png =516)
 
 ##### Result Verification
 
@@ -39,15 +36,12 @@ Go to "Data" to check the import status and data:
 
 You can see that the number of rows written in the import result is "100,000", which is consistent with the number generated in the "Test Data Generation" step.
 
-:-: ![](.topwrite/assets/image_1736146881028.png =523)
 
 You can further "Preview Data" to confirm the data was loaded successfully:
 
-:-: ![](.topwrite/assets/image_1736146888569.png =518)
 
 At this point, we have loaded local files into the table via Singdata Lakehouse Studio.
 
-:-: ![](.topwrite/assets/image_1736146899159.png =515)
 
 #### Next Steps
 

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

@@ -12,27 +12,22 @@ When the existing data source (including databases, data warehouses) has a publi
 
 Navigate to Development -> Tasks, click "+", select "Offline Sync", and create a new "Offline Sync" job.
 
-:-: ![](.topwrite/assets/image_1736147655855.png =464)
 
 Other parameter configurations are as follows:
 
-:-: ![](.topwrite/assets/image_1736147664609.png =470)
 
 Then select to create a new data table: lift\_tickets\_data\_from\_pg\_batch.
 
 In the "Create New Data Table" SQL code, change the table name to "lift\_tickets\_data\_from\_pg\_batch".
 
-:-: ![](.topwrite/assets/image_1736147671728.png =455)
 
 Check if the field mapping meets expectations, then test run the sync task:
 
-:-: ![](.topwrite/assets/image_1736147681157.png =459)
 
 Check the test results:
 
 View the test task logs and check if the number of nubWrite matches the number of rows in the source table.
 
-:-: ![](.topwrite/assets/image_1736147689681.png =469)
 
 #### Next Steps Recommendations
 

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

@@ -18,7 +18,6 @@ Navigate to Development -> Tasks, click "+", and create a new Python task.
 
 Task Name: 05_Loading Files from the Web into the Lakehouse via Studio's Built-in Python Node.
 
-:-: ![](.topwrite/assets/image_1736148972084.png =427)
 
 ##### Develop Python Task Code
 
@@ -82,25 +81,21 @@ There are two parameters:
 
 ACCESS\_KEY\_ID = '${ak}'ACCESS\_KEY\_SECRET = '${sk}'
 
-Click on the schedule to fill in the default values for the parameters:
+Click on the schedule to fill in the default values for the parameters.
 
-:-: ![](.topwrite/assets/image_1736148983636.png =435)
 
-Click "Load Parameters from Code" and fill in the corresponding values:
+Click "Load Parameters from Code" and fill in the corresponding values.
 
-:-: ![](.topwrite/assets/image_1736148989712.png =431)
 
 ##### Run the Test
 
 Click "Run" to execute the Python code.
 
-:-: ![](.topwrite/assets/image_1736148997078.png =427)
 
 ##### Check the Upload Results
 
 Log in to Alibaba Cloud Object Storage to view the uploaded files.
 
-:-: ![](.topwrite/assets/image_1736149004171.png =415)
 
 #### Next Steps