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

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

@@ -27,46 +27,42 @@ You can use the "Sync Task" feature provided by Lakehouse Studio to sync data fr
 
 1. As shown below, click the button to enter the Lakehouse service instance:
 
-   ![](.topwrite/assets/image_1748337538227.png)
+
 
 2. Navigate to the "Development" page:
 
-   ![](.topwrite/assets/image_1748337566571.png)
 
-3. In the folder area of the left directory tree, click the + (New) button, and select the "Batch Sync" task type from the menu:
 
-   ![](.topwrite/assets/image_1748337579720.png)
+3. In the folder area of the left directory tree, click the + (New) button, and select the "Batch Sync" task type from the menu.
+
+
 
 4. In the dialog, enter the task name (you can create a folder, not required), and click "OK".
 
-   ![](.topwrite/assets/image_1748337590537.png)
 
-5. You can see the newly created sync task on the page, as shown below:
 
-   ![](.topwrite/assets/image_1748337598616.png)
+5. You can see the newly created sync task on the page, as shown below:
 
+ 
 6. Start configuring the required information for the sync task. The core is to configure the source and target information.
    Note: You need to understand the concept of "Data Source" here. A "Data Source" is an object that defines external service connection information, including service address, authentication information, connection method, etc. A defined data source can be used as a data source or data target in data sync tasks.
 
 7. The source configuration is shown below. Click "+" to quickly bring up the interface for creating a new data source:
 
-   ![](.topwrite/assets/image_1748337608071.png)
+ 
 
 8. Select the type of data source to import. In this example, MySQL is selected. Click "Next" to enter the detailed configuration page. The "Usage Instructions" in the upper right corner provides a detailed configuration guide, as shown below. Ensure that the filled-in JDBC connection address, username, and password are correct. The serverTimezone configuration item refers to the timezone where the database is located, which will affect the values of date and time fields after syncing to the target. Please select correctly based on the actual situation.
 
-   ![](.topwrite/assets/image_1748337616322.png)
+
 
 9. After completing the required information configuration for the data source, you can click the "Connectivity Test" button to test whether the data source is reachable. A successful connection test is shown below. If the connection fails, please check the network and whether the configuration information is accurate. After the test passes, click "OK" in the lower right corner to save.
 
-   ![](.topwrite/assets/image_1748337623157.png)
 
 10. After creating the data source, return to the sync task configuration page, select this data source as the source (if it does not display automatically, please reopen the task), and select the namespace (i.e., database) and data object (i.e., table). Other configuration items can be left empty.
 
-    ![](.topwrite/assets/image_1748337630413.png)
 
 11. After completing the source configuration, proceed to configure the target, as shown below:
 
-    ![](.topwrite/assets/image_1748337636870.png)
 
     1) Select the Lakehouse data source type
 
@@ -76,31 +72,26 @@ You can use the "Sync Task" feature provided by Lakehouse Studio to sync data fr
 
     4) Data object: Click the + button to quickly create a new target Lakehouse table. In the dialog, verify the table name and schema information, then click "OK" to complete the table creation.
 
-    ![](.topwrite/assets/image_1748337664468.png)
 
     5) Select "Overwrite" as the data write mode, meaning the target table will be truncated before syncing data from the source.
 
 12. After completing the above steps, the field mapping relationship between the source table and target table will be automatically displayed in the "Field Mapping Configuration" (default is same-name mapping). The default approach is fine here, no modification needed.
 
-    ![](.topwrite/assets/image_1748337679341.png)
 
 13. For other configuration items, such as sync rule configuration and advanced configuration, use the default values.
 
-    ![](.topwrite/assets/image_1748337686553.png)
 
 14. Click the "Save" button above the task configuration area to save all task configurations.
 
-    ![](.topwrite/assets/image_1748337694348.png)
 
 15. Click the "Run" button in the upper right corner to run a test and trigger data sync (use the default value for the cluster option).
 
-    ![](.topwrite/assets/image_1748337705970.png)
+
 
 16. In the "Run History" area at the bottom right of the page, you can view the task's running status.
 
     Note: If you want to test sync speed, it is recommended to use a table with a relatively large data volume to reduce the impact of task startup time.
 
-    ![](.topwrite/assets/image_1748337713243.png)
 
 17. At this point, a sync task has been created and run, importing MySQL data into Lakehouse. You can now perform subsequent analysis and processing based on the imported data.
 

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

@@ -20,13 +20,12 @@ Enterprise business intelligence (BI) generally obtains raw data from the enterp
 
 ### Workflow Diagram
 
-![](.topwrite/assets/image_1692343510673.png =648)
+
 
 ### Business Requirements
 
 The business requirements in this example simulate common BI analysis scenarios in e-commerce, generating a wide table at the detailed layer of the data warehouse by associating user behavior log data with dimension tables such as products, stores, and time zones. This wide table is then provided to downstream data application layers, and BI tools are used for sales and order statistics, funnel conversion models, popular product displays, etc.
 
-![](.topwrite/assets/image_1692975150801.png =704)
 
 ^
 
@@ -54,7 +53,6 @@ Configure task dependencies in the order of data integration tasks first, follow
 
 Deploy all tasks to the production environment.
 
-![](.topwrite/assets/image_1693020935459.png =627)
 
 ^
 
@@ -64,7 +62,7 @@ Refer to the **Preparations** in the previous chapter. Before starting the "Quic
 
 ^
 
-![](.topwrite/assets/9865a42db031a5516b4caf79bf0f4bb.png =715)
+![](/.topwrite/assets/image_1780998919773.png)
 
 ^
 
@@ -78,26 +76,24 @@ In the initialized product environment, you may already have the following objec
 ^
 
 Figure 1 —— User
-
-![](.topwrite/assets/image_1692348046212.png =354)
+![](/.topwrite/assets/image_1780998366942.png)
 
 ^
 
 Figure 2 —— Workspace: QuickStart\_WorkSpace
-
-![](.topwrite/assets/image_1692586908866.png =512)
+![](/.topwrite/assets/image_1780998669158.png)
 
 ^
 
 Figure 3 —— Schema: Public
 
-![](.topwrite/assets/image_1692583856135.png =730)
+![](/.topwrite/assets/image_1780998800756.png)
 
 ^
 
 Figure 4 —— Computing Cluster: Default
 
-![](.topwrite/assets/image_1692586859163.png =728)
+![](/.topwrite/assets/image_1780998850270.png)
 
 ###
 
@@ -117,34 +113,21 @@ Studio provides two ways to create a new data source:
 ^
 
 Figure 1 —— Method 1
-![](.topwrite/assets/image_1692588245122.png =785)
+![](/.topwrite/assets/image_1780999019336.png)
 
 ^
 
 Figure 2 —— Method 2
-![](.topwrite/assets/image_1692588445515.png =719)
-
-^
-
-![](.topwrite/assets/image_1692589881885.png =676)
+![](/.topwrite/assets/image_1780999067659.png)
 
 ^
 
 Select the MySQL type data source on the new data source page and click Next.
 
-![](.topwrite/assets/image_1692605359674.png =399)
-
-^
-
 Enter the database connection information and click connectivity test. If the configuration is correct, a green \[Connection Successful] will be displayed. If the connection test fails, you need to verify the configuration information or change the database's access whitelist policy. \*If you need to add specific IP whitelist entries, please contact Singdata customer service or your account manager.
 
-![](.topwrite/assets/image_1692605303319.png =553)
-
-^
-
 After successful creation, the data source can be seen in the list.
 
-![](.topwrite/assets/image_1692605636158.png =733)
 
 ^
 

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

@@ -21,23 +21,21 @@ Before reading this guide, it is recommended to complete reading and understandi
 
 1. Click the button as shown below to enter the Lakehouse service instance:
 
-   ![](.topwrite/assets/image_1747991184372.png)
+:-: ![](/.topwrite/assets/image_1780975475741.png)
 
 2. Navigate to Management > Workspace page:
 
-   ![](.topwrite/assets/image_1747991196958.png)
+:-: ![](/.topwrite/assets/image_1780975507979.png)
 
 3. Click the "New" button, fill in the information according to the interface prompts, and complete the creation:
 
    * Note that the workspace name must be unique within the service instance and has naming constraints. Please follow the guidance prompts on the page.
    * "Storage Encryption" refers to whether tables under the workspace are physically stored with encryption enabled. This is an advanced configuration feature, enable as needed.
-     ![](.topwrite/assets/image_1747991206223.png)
 
-4. After the workspace is created, you may potentially perform the following operations:
 
-   * Use this workspace in product modules such as task development. The workspace switching entry is located at the top right corner of the page, as shown below:
+4. After the workspace is created, you may potentially perform the following operations:
 
-     ![](.topwrite/assets/image_1747991250081.png)
+   * Use this workspace in product modules such as task development. 
 
    * Add other users to the workspace for collaboration. For details, see: [How to Quickly Manage Users Under a Workspace](quick_start_workspace_user.md)
 

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

@@ -23,19 +23,19 @@ You can use the "Data Quality" feature provided by Lakehouse Studio to configure
 
 ### Steps
 
-1. As shown below, click the button to enter the Lakehouse service instance:
+1. click the button to enter the Lakehouse service instance.
 
-   ![](.topwrite/assets/image_1748337538227.png)
 
-2. Navigate to "Data" > "Data Quality" page:
 
-   ![](.topwrite/assets/image_1749449999835.png)
+2. Navigate to "Data" > "Data Quality" page
+
+
 
 3. On the "Quality Rules" tab, click the "Create Rule" button to open the page for creating a new quality rule. Please verify and ensure that the workspace in the upper right corner of the page is the workspace where the data table to be verified is located. If not, you can click to switch.
-   ![](.topwrite/assets/image_1749450019542.png)
+
 
 4. On the Create Rule page, the workspace value will be automatically set to the workspace selected in the previous step [1]. Select the data object to verify. In this example, select the `test_json` table where data was written by the sync task in the previous ETL pipeline for verification [2]. When a quality rule is executed, it is actually converted to a Lakehouse SQL statement for execution, so an execution cluster is required. For simplicity, it is recommended to directly select the default GP-type cluster `DEFAULT` [3].
-   ![](.topwrite/assets/image_1749450038105.png)
+
 
 5. Configure "Verification Method", "Trigger Method", and "Save" the rule.
 
@@ -45,10 +45,10 @@ You can use the "Data Quality" feature provided by Lakehouse Studio to configure
 
    * Other configuration items can keep default values or be left blank. Finally, click the "Save" [6] button to complete the creation of the quality rule.
 
-   ![](.topwrite/assets/image_1749450069308.png)
+
 
 6. After creation, you can see the newly added rule in the quality rule list page.
-   ![](.topwrite/assets/image_1749450081238.png)
+
 
 7. You can click the "Trial Run" button to test the configuration and verification of the quality rule. On the "Verification Results" tab, you can view the specific results, as shown below: the quality rule was triggered to run, the verification result matches expectations, and everything is normal.
    ![](.topwrite/assets/image_1749450092151.png)

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

@@ -22,25 +22,23 @@ Users with `workspace_admin` or `workspace_dev` role permissions are required to
 
 ### Creating a SQL Task
 
-1. Use the operation entry shown below to create a SQL task:
+1. Use the operation entry to create a SQL task.
 
-   ![](.topwrite/assets/image_1748425848352.png)
 
 2. In the task creation dialog, name the task "SQL_DWS_Aggregation" and create a dedicated folder named "Data Processing".
 
-   ![](.topwrite/assets/image_1748425859150.png)
+
 
 3. After the SQL task is created, as shown below, you can write specific SQL code in the editor area.
 
-   ![](.topwrite/assets/image_1748425869532.png)
+
 
 4. Previously, through the data sync task, MySQL data has been synced to the test_json table in Lakehouse. In the SQL task, perform aggregation processing based on this table's data, such as summing the c2_tinyint_column and c3_smallint_column fields respectively. Navigate to the "Data" tab, locate the target table test_json, and click "Data Query" in the action bar. This will automatically insert a SELECT code template into the editor, as shown below, helping to improve code writing efficiency.
 
-   ![](.topwrite/assets/image_1748425911494.png)
 
 5. Modify the above code template to the desired processing logic, then save. This is just for demonstration purposes, simplified processing, and the aggregation results are not written to a new table.
 
-   ![](.topwrite/assets/image_1748425934078.png)
+
 
    ```SQL
         SELECT   SUM(c2_tinyint_column),         
@@ -54,44 +52,42 @@ After completing the creation of the sync task and SQL task, to build a complete
 
 1. Open the sync task and click the "Schedule" button on the page to open the scheduling configuration.
 
-   ![](.topwrite/assets/image_1748426012421.png =633)
+
 
 2. Configure Scheduling Time: Configure to schedule daily, run multiple times, once every hour, as shown below. Use "Preview Schedule Time" to view the specific scheduled times corresponding to the configuration.
 
-   ![](.topwrite/assets/image_1748426023159.png =722)
 
-   ![](.topwrite/assets/image_1748426030471.png =397)
 
 3. Configure Instance Information: The main thing to configure here is "Instance Rerun Mode". Since this task does not have data idempotency issues when rerunning, it can be rerun. Therefore select "Can be rerun regardless of success or failure". Other properties can use default values.
 
-   ![](.topwrite/assets/image_1748426041609.png =386)
+
 
 4. Configure Scheduling Dependencies: The sync task is the first task in the pipeline and has no upstream dependencies, so leave this blank.
 
-   ![](.topwrite/assets/image_1748426049779.png =386)
+
 
 5. Configure Task Output: Task output is used to describe which table this task writes to, so that downstream tasks consuming this table can intelligently identify the corresponding upstream task. Click the "Smart Parse" button, and the system will automatically resolve the current task's output table through the task configuration and backfill it into the configuration.
 
-   ![](.topwrite/assets/image_1748426056766.png =386)
+
 
 6. After completing the above scheduling configuration, click the "OK" button at the bottom right of the page to save the configuration. Return to the task page, and as shown below, the "Submit" button will become clickable.
 
-   ![](.topwrite/assets/image_1748426062758.png)
+
 
 7. Click the "Submit" button, verify the information again in the popup dialog, then click OK. The sync task will be submitted to the production environment for periodic scheduled execution.
 
-   ![](.topwrite/assets/image_1748426068998.png)
+
 
 8. Switch to the SQL task, and click the "Schedule" button on the page to open the scheduling configuration. The properties to configure are the same as for the sync task, i.e.:
 
       1. Configure to schedule multiple times per day, once every hour.
       2. Configure the rerun property as "Can be rerun regardless of success or failure".
       3. Pay special attention to configuring the SQL task's dependency on the sync task. Click the "Smart Parse" button on the page to automatically identify the sync task that the SQL task depends on and backfill it automatically; you can also add it manually.
-      ![](.topwrite/assets/image_1748426078453.png =386)
+
 
 9. Similarly, after the SQL task's scheduling configuration is complete, click the "OK" button at the bottom right of the page to save the configuration. Return to the task page, and click the "Submit" button to also submit the SQL task for scheduled execution.
 
-   ![](.topwrite/assets/image_1748426087176.png)
+
 
 10. Enter "Task Operations" to view the actual results. There are two ways to enter:
 
@@ -99,19 +95,19 @@ After completing the creation of the sync task and SQL task, to build a complete
 
     * Method 2: Click the "Operations" button directly on the task to go directly to the task's details page in the Operations Center. This method is recommended.
 
-      ![](.topwrite/assets/image_1748426094142.png)
+
 
 11. View the task details, as shown below. As expected, the SQL task depends on the sync task:
 
-    ![](.topwrite/assets/image_1748426100418.png)
+
 
 12. Click the "Task Instances" tab to see the list of specific instances corresponding to the task. Instances have been generated according to the configured scheduled time (only instances after the task submission time are generated):
 
-    ![](.topwrite/assets/image_1748426139524.png)
+
 
 13. Click an instance ID to enter the instance details page for viewing. When the scheduled time arrives, the upstream sync task instance runs first. After it runs successfully, the downstream SQL task instance starts running. Two conditions must be simultaneously met for an instance to be triggered to run (necessary and sufficient conditions): the instance's own scheduled time has arrived, AND the upstream instance is in a successful state.
 
-    ![](.topwrite/assets/image_1748426146577.png)
+
 
 14. At this point, a complete ETL pipeline has been orchestrated, built, and submitted for periodic scheduling and execution.
 

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

@@ -24,11 +24,10 @@ Users with `workspace_admin`, `workspace_dev`, or `workspace_sre` role permissio
 
 #### Entering the Monitoring and Alerting Module
 
-1. As shown below, click the button to enter the Lakehouse service instance:
-   ![](.topwrite/assets/image_1748337538227.png)
+1. click the button to enter the Lakehouse service instance.
+   ![](/.topwrite/assets/image_1780975925233.png =470)
 
 2. Navigate to "Operations Monitoring" > "Monitoring and Alerting" page:
-   ![](.topwrite/assets/image_1749455648524.png)
 
 #### Using Built-in Rules
 
@@ -36,19 +35,18 @@ As mentioned above, the product has built-in global monitoring rules available f
 
 1. As shown below, there are mainly two types of built-in monitoring rules: "Periodic Task Instance Execution Failed" and "Data Quality Check Failed":
 
-   ![](.topwrite/assets/image_1749455660655.png)
+:-:    ![](.topwrite/assets/image_1749455660655.png)
 
 2. Click a specific monitoring rule to view its detailed configuration definition. Taking "Data Quality Check Failed - Strong Rule" as an example, the following figure shows its core information such as monitoring items, alert notification methods, and notification recipients.
-   ![](.topwrite/assets/image_1749455672982.png)
 
    * Monitoring Item: Strong blocking scheduled quality rule verification failed.
    * Alert Notification: For critical-level rules, according to the notification policy definition (not expanded here, see related documents for details), phone alerts will be pushed.
    * Notification Recipients: By default, the object owner will be notified. For data quality rules, the rule creator is notified by default.
 
 3. Enable built-in global alert rules and subscriptions, continuing with "Data Quality Check Failed - Strong Rule" as an example:
-   ![](.topwrite/assets/image_1749455707588.png)
-   * Click "Enable" to activate this rule [1]. According to the rule definition, this alert will be sent to the object owner, i.e., the creator of the quality rule.
-   * If you are not the object owner (e.g., not the creator of the quality rule) but also want to follow this alert, you can click the "Subscribe" button [2].
+
+   * Click "Enable" to activate this rule \[1]. According to the rule definition, this alert will be sent to the object owner, i.e., the creator of the quality rule.
+   * If you are not the object owner (e.g., not the creator of the quality rule) but also want to follow this alert, you can click the "Subscribe" button \[2].
 
 #### Custom Monitoring Rules
 
@@ -57,28 +55,22 @@ Built-in rules primarily provide overall monitoring from a global dimension, fac
 The following example will demonstrate how to monitor the instance execution failure of a specific periodic scheduling task and alert via phone. The main steps are as follows:
 
 1. In the "Monitoring Rules" list, click the "Create Rule" button.
-   ![](.topwrite/assets/image_1749455842124.png)
 
 2. In the Create Rule dialog, fill in the required information for the rule and save.
    * Monitoring Item: Task instance execution failed. Use filters to **select the specific task name**.
    * Alert Notification: Set the level to "Warning" and use the "General Notification Policy" to send SMS alerts. The notification recipient defaults to the current operator.
-     ![](.topwrite/assets/image_1749455860120.png)
-     ![](.topwrite/assets/image_1749455865473.png)
 
 3. After the rule is created, a record will be displayed in the list:
-   ![](.topwrite/assets/image_1749455912549.png)
 
 4. Observe how the monitoring rule works.
 
    * Here, we perform a simulated error change: modify the SQL logic of the monitored task, use an incorrect field name, then submit for scheduled execution to trigger a scheduling instance execution failure.
-     ![](.topwrite/assets/image_1749455960285.png)
-     ![](.topwrite/assets/image_1749456300165.png)
 
    * After the task is scheduled and executed and a failure occurs, you can observe the working status of the monitoring alert rule in "Monitoring and Alerting", which is as expected:
-     * In "Alert Events", you can see a new alert event added:
-       ![](.topwrite/assets/image_1749456335722.png)
-     * In "Notification History", you can see the specific alert notification push status:
-       ![](.topwrite/assets/image_1749456370821.png)
+     * In "Alert Events", you can see a new alert event added.
+
+     * In "Notification History", you can see the specific alert notification push status.
+
 
 At this point, the configuration of built-in and custom monitoring and alerting rules and the observation of their actual working results have been completed.
 

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

@@ -20,20 +20,18 @@ To quickly run a SQL query in the UI, use the Data Development module in Lakehou
 
 The product includes ready-to-use sample code and accompanying sample data. In the page navigation, click **Development** to enter the Data Development interface, where you will see sample code files under the `Tpch_100g` folder. These samples demonstrate how to write SQL queries for quick analysis based on the Tpch_100g sample data, as shown below:
 
-![](.topwrite/assets/image_1747993124883.png)
+
 
 Double-click a sample code file to open it, then click the **Run** button in the upper-right corner of the page to trigger SQL execution. Once execution completes, you can view the results and logs in the lower-right area of the page.
 
-![](.topwrite/assets/image_1747993372483.png)
+
 
 ^
 
 Pay special attention to the **Cluster** option in the upper-right corner of the page. "Cluster" stands for "Compute Cluster," which is the core concept of how Lakehouse provides compute power. See [this document](virtual-cluster.md) for detailed information. When a workspace is created, two clusters are initialized by default: a general-purpose cluster named `DEFAULT` and an analytics cluster named `DEFAULT_AP`. These two types of clusters are optimized for different workloads:
 
 * **General Purpose (GP)**: Suitable for offline job processing. Jobs share compute resources, and new and old jobs are scheduled fairly. Suitable for periodic scheduling tasks to process large volumes of data.
-* **Analytics Purpose (AP)**: Features multiple compute instances and auto-scaling, suitable for online and high-concurrency jobs. Choose this cluster type if you want a better query performance experience. In addition, AP clusters perform intelligent data caching. After the first query, subsequent queries run faster. The following diagram illustrates this difference:
-
-  ![](.topwrite/assets/image_1748326696659.png)
+* **Analytics Purpose (AP)**: Features multiple compute instances and auto-scaling, suitable for online and high-concurrency jobs. Choose this cluster type if you want a better query performance experience. In addition, AP clusters perform intelligent data caching. After the first query, subsequent queries run faster. 
 
 ^
 
@@ -43,7 +41,7 @@ You can also learn more about query analysis using sample data by reading [Quick
 
 In addition to using sample code and sample data, you can also write and run your own SQL. In the page navigation bar, click **Development** to enter the Data Development interface. Under **Tasks**, create a SQL task file by selecting **SQL Script** from the new menu.
 
-![](.topwrite/assets/image_1721484292583.png)
+
 
 In the task file, follow these steps to write and run SQL:
 
@@ -55,15 +53,15 @@ In the task file, follow these steps to write and run SQL:
 
 4. Click the run button on the left or the run button in the upper-right corner to execute the code. The left button only executes the code block where the cursor is located. The upper-right button executes all code by default; you can also select a portion of code first, then click the upper-right run button to execute only the selected portion.
 
-   ![](.topwrite/assets/image_1721484303315.png)
+
 
 5. After execution completes, you can view the results, duration, and run logs in the area at the bottom of the page:
 
-   ![](.topwrite/assets/image_1721484312151.png)
+ 
 
 6. While writing code in the editor, you can also switch to the **Data** tab to quickly browse and use data. After finding the desired table, you can quickly insert the table name, field names, or directly generate a sample query SQL from the action menu:
 
-   ![](.topwrite/assets/image_1721484321409.png)
+
 
 ### Other Common Operations
 
@@ -76,7 +74,6 @@ In addition to the **Run** operation, the system provides the following features
 5. Find: Search for code snippets within the current file by keyword
 6. Shortcuts: Display supported common shortcuts
 
-![](.topwrite/assets/image_1721531293556.png)
 
 ## Limitations
 

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

@@ -30,17 +30,15 @@ You can add data to Lakehouse tables through the "Data Upload" feature available
 2. You can click "Upload Data" in any of the following locations:
 
    * Instance Homepage
-     ![](.topwrite/assets/image_1747999086635.png)
+
    * Development -> Data Tree
-     ![](.topwrite/assets/image_1749035410382.png)
+
    * Data Asset Map
-     ![](.topwrite/assets/image_1749035355497.png)
+
    * Data Asset Map -> Data Management
-     ![](.topwrite/assets/image_1749035495163.png)
 
-3. After clicking, the following dialog will appear. You can add local files by dragging and dropping, or by clicking to browse files on the local system. Only one file can be added at a time, and the size must not exceed 2GiB. You can use this sample file to try uploading: :attachment[walmart.csv]{src=".topwrite/assets/walmart.csv" size="363.73 kB"}.
 
-   ![](.topwrite/assets/image_1749035813956.png =380)
+3. After clicking, the following dialog will appear. You can add local files by dragging and dropping, or by clicking to browse files on the local system. Only one file can be added at a time, and the size must not exceed 2GiB. You can use this sample file to try uploading: :attachment[walmart.csv]{src=".topwrite/assets/walmart.csv" size="363.73 kB"}.
 
 4. Schema: Choose to create the table under a certain schema.
 
@@ -51,7 +49,7 @@ You can add data to Lakehouse tables through the "Data Upload" feature available
 7. Data Import Mode: Supports append write and truncate-then-write modes for importing data into the new table.
 
 8. After confirming all information, click "Next". The system will automatically parse the field information from the uploaded file, as shown below.
-   ![](.topwrite/assets/image_1749035692218.png =380)
+
 
 9. Check and determine whether the automatically parsed field names and field types meet expectations. After confirming correctness, click "Confirm" to complete the table creation and data upload.
    * If you find issues with field parsing, you can modify the **File Properties** configuration items to re-trigger automatic parsing of field names, field types, etc. Or you can manually modify field names or field types.

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

@@ -19,15 +19,15 @@ Before reading this guide, we recommend you review and understand the following
 
 1. After logging in, you will be directed to the "Admin Center" account home page by default, as shown below:
 
-   ![](.topwrite/assets/image_1747990064729.png)
+
 
 2. In the Admin Center's left navigation bar, go to "Account Management > User Management" to access the user management page, as shown below:
 
-   ![](.topwrite/assets/image_1747990075720.png)
+
 
 3. Click the "Create" button in the upper-right corner and select "Create User" to begin creating a user account.
 
-   ![](.topwrite/assets/image_1747990090897.png =297)
+
 
    > Note: "Custom Service User" is an identity created for automation tools, tasks, and applications. It cannot log in via the web UI. You can ignore this for now. For more details, see: [Service User Management](account_user_management.md)
 
@@ -35,24 +35,24 @@ Before reading this guide, we recommend you review and understand the following
 
    * Remember the password you set here, as you will need to provide the username and password to the user later.
    * The phone number must be the user's mobile number so that alerts and notifications can be delivered accurately.
-     ![](.topwrite/assets/image_1747990274287.png)
+
 
 5. After creating the new user account, provide the following two pieces of information to the user:
 
    * Username and password.
    * Account login URL in the format: `<account-name>.accounts.singdata.com`. You can also copy the browser URL shown in the screenshot below and send it to the user.
 
-     ![](.topwrite/assets/image_1747990303813.png)
+
 
 6. After the user logs in with the username and password, they can change the initial password by navigating to "Account Management > User Management" in the left sidebar, finding their account, and selecting "Change Password" from the actions menu.
 
-   ![](.topwrite/assets/image_1747990312625.png)
+
 
 ## Limitations
 
-* Permission Note: Only users with the account administrator (`account_admin`) role can create and manage users. This role is identified as follows:
+* Permission Note: Only users with the account administrator (`account_admin`) role can create and manage users. 
+
 
-  ![](.topwrite/assets/image_1747990332688.png =446)
 
 ## Related Documents
 

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

@@ -8,7 +8,6 @@ To achieve both isolation and ease of data exchange within a service instance, p
 
 When a user has permissions for data objects within a workspace, they can perform cross-space queries or other operations within the scope of their permissions on these data objects in other workspaces.
 
-:-: ![](.topwrite/assets/workspace_1735992503899.png =814)
 
 As shown in the figure above, multiple workspaces can be created within a Lakehouse service instance. A service instance user can be added to multiple workspaces simultaneously and be granted permissions for objects within those workspaces.
 
@@ -37,11 +36,9 @@ After the service instance is activated, the system will create a workspace name
 
 In the "Account Home" of the control center, click on the activated service instance to enter the homepage of the service instance.
 
-:-: ![](.topwrite/assets/image_1721463116737.png =745)
 
 On the homepage of the service instance, click on any function in the left function menu such as "Development", "Computing", "Operations Monitoring", etc. The workspaces that the current account has permission to access will be listed in the upper right corner of the page, supporting switching. When using a single workspace, it defaults to the only workspace within the service instance. At this time, all task scripts and scheduling jobs are within this workspace.
 
-:-: ![](.topwrite/assets/image_1721463152612.png =743)
 
 ## Creating and Using Multiple Workspaces
 
@@ -55,7 +52,6 @@ The instance administrator (instance\_admin) role of the service instance can cr
 
 Enter the "Management - Workspace" menu, click "New Space" on the workspace management page, fill in the required information, and create it.
 
-:-: ![](.topwrite/assets/image_1721463203358.png =794)
 
 ^
 
@@ -65,7 +61,6 @@ The user who creates the new workspace will be granted the workspace administrat
 
 When using multiple workspaces, you can switch between different workspace environments through the workspace button in the upper right corner of the "Development", "Computing", "Operations Monitoring" and other function pages.
 
-:-: ![](.topwrite/assets/image_1736089880260.png =785)
 
 ^