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

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

@@ -0,0 +1,75 @@
+# Getting Started: How to Quickly Configure and Use Data Quality Rules
+
+## Applicable Scenarios
+
+Data quality rules are used to verify whether the quality of data objects meets requirements, such as data correctness, validity, and consistency, especially for tables produced by tasks serving production use. If you have configured an ETL pipeline, such as the [Getting Started: How to Quickly Configure, Orchestrate, and Schedule ETL Pipelines](quick_start_etl.md), and plan to add a data quality check, it is recommended to read this guide.
+
+## Prerequisite Reading
+
+Before reading this guide, it is recommended to complete reading and understanding the following documents:
+
+* [Lakehouse Product Introduction](what_is_clickzetta_lakehouse.md)
+* [Key Concepts](key_concepts.md)
+* [Lakehouse Studio Quick Tour](lakehousestudiotour.md)
+
+## Operation Guide
+
+You can use the "Data Quality" feature provided by Lakehouse Studio to configure quality rules for checking. Checks are mainly performed based on data quality rules. Rules predefine the verification object, check logic, and expected results, and can be triggered to run in multiple ways. This example demonstrates how to configure a rule for a Lakehouse table field to verify that its value is not null.
+
+### Usage Notes
+
+* Users with `workspace_admin` or `workspace_dev` role permissions have access to the "Data Quality" feature.
+* The "Data Quality" feature is currently primarily used to monitor Lakehouse data objects, such as Tables, Views, Volumes, Dynamic Tables, etc. For other data types such as MySQL, it is not currently supported.
+
+### Steps
+
+1. As shown below, 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)
+
+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.
+
+   * Verification Method [4]: In this example, we plan to monitor whether the c1_id field in the test_json table has non-null values, so select "Single Metric Value Verification". "Metric Value Change Verification" compares two metrics and verifies the change value. The product has many built-in metric rules, ready to use out of the box. Here, select field null count, select the field name, and set the expected result to equal 0.
+
+   * Trigger Method [5]: As the name implies, the product provides three methods: scheduled triggering, periodic task triggering, and manual triggering. Periodic task triggering is bound to the scheduling system and can trigger the execution of quality rules after the task scheduling instance completes running, enabling more timely verification. For production scenarios, this method is recommended. Especially the "Strong Blocking Scheduling" option can block the entire scheduling pipeline when a quality rule verification fails, preventing the spread of quality issues. When selecting this method, you need to choose the bound scheduling task (i.e., the task that produces this data table).
+
+   * 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)
+   ![](.topwrite/assets/image_1749450096317.png)
+
+8. Wait for the scheduled task's timing to arrive and observe the quality rule triggering.
+
+   * In "Task Operations", you can view the triggering and running status of quality rules through the logs of periodic task instance execution.
+     ![](.topwrite/assets/image_1749450116093.png)
+
+   * In "Data Quality" > "Verification Results", you can see the newly added verification record, with the trigger method being "Periodic Task Triggered".
+     ![](.topwrite/assets/image_1749450124984.png)
+
+9. At this point, the configuration of quality rules and observation of verification execution have been completed. After completing the data quality rule configuration, if you need to promptly receive monitoring and alerting information when quality rule verification fails, you also need to configure monitoring. The specific operations are omitted here. For details, see the [Data Quality](dataquality.md) help document.
+
+## Related Documents
+
+* You can read the [Data Quality](dataquality.md) help document to understand the complete usage guide for the Data Quality module.
+
+## Next Steps
+
+* After completing quality rule configuration, you can refer to the guide [How to Quickly Configure and Use Monitoring and Alerting Rules](quick_start_monitoring_and_alerting.md) to configure monitoring rules and send alerts for quality rule verification results and task running status.
+
+^

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

@@ -0,0 +1,131 @@
+# Getting Started: How to Quickly Configure, Orchestrate, and Schedule ETL Pipelines
+
+## Applicable Scenarios
+
+One of the main tasks of a data warehouse engineer is building an offline data warehouse, i.e., creating and maintaining periodically scheduled ETL pipelines. This document provides an overview of how to configure and orchestrate ETL tasks based on Lakehouse Studio and configure scheduling properties so that the entire ETL pipeline can be scheduled and run periodically according to dependencies.
+
+## Prerequisite Reading
+
+Before reading this guide, it is recommended to complete reading and understanding the following documents:
+
+* [Lakehouse Product Introduction](what_is_clickzetta_lakehouse.md)
+* [Key Concepts](key_concepts.md)
+* [Lakehouse Studio Quick Tour](lakehousestudiotour.md)
+
+## Operation Guide
+
+In [Getting Started: How to Quickly Create a Sync Task to Import Data](quick_start_batch_sync_data.md), we already created a data sync task. This document will demonstrate, by example, how to create a SQL processing task and make it depend on the data sync task, thereby building an ETL pipeline, and configure scheduling to run periodically.
+
+### Usage Notes
+
+Users with `workspace_admin` or `workspace_dev` role permissions are required to use the features of task development, submission and publishing, and operations center.
+
+### Creating a SQL Task
+
+1. Use the operation entry shown below 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),         
+                 SUM(c3_smallint_column),
+        FROM     test_json;
+   ```
+
+### Task Orchestration and Scheduling Configuration
+
+After completing the creation of the sync task and SQL task, to build a complete offline periodic ETL pipeline, you also need to configure scheduling timing and task dependencies.
+
+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:
+
+    * Method 1: Through the left navigation Operations Monitoring > Task Operations
+
+    * 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.
+
+## Limitations
+
+* Permission Control: Users with `workspace_admin` or `workspace_dev` role permissions are required to use the features of task development, submission and publishing, and the operations center.
+
+## Related Documents
+
+* You can read the [Task Development](ide.md) help document to learn in detail how to perform task development and scheduling configuration. The [Task Group](task_group.md) feature provides a visual way to orchestrate ETL pipelines, which is more intuitive and recommended.
+* You can read the [Task and Instance Operations](task-instance-maintenance.md) help document to learn in detail how to perform various operations on tasks and instances.
+
+## Next Steps
+
+* None for now.
+
+^

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

@@ -0,0 +1,93 @@
+# Getting Started: How to Quickly Configure and Use Monitoring and Alerting Rules
+
+## Applicable Scenarios
+
+If you have configured an ETL pipeline, such as completing the [Getting Started: How to Quickly Configure, Orchestrate, and Schedule ETL Pipelines](quick_start_etl.md), and plan to add monitoring for task execution stability and data quality checks of the output, and send alert notifications when anomalies occur, it is recommended to read this guide.
+
+## Prerequisite Reading
+
+Before reading this guide, it is recommended to complete reading and understanding the following documents:
+
+* [Lakehouse Product Introduction](what_is_clickzetta_lakehouse.md)
+* [Key Concepts](key_concepts.md)
+* [Lakehouse Studio Quick Tour](lakehousestudiotour.md)
+
+## Operation Guide
+
+The "Monitoring and Alerting" product module of Lakehouse Studio provides a powerful set of features that allows users to monitor key metrics such as task running status in real-time through system built-in rules or custom rules. Once an anomaly is detected, the system will send timely alert notifications to help you ensure the stability and reliability of data flows.
+
+### Usage Notes
+
+Users with `workspace_admin`, `workspace_dev`, or `workspace_sre` role permissions can use the "Monitoring and Alerting" feature.
+
+### Steps
+
+#### Entering the Monitoring and Alerting Module
+
+1. As shown below, click the button to enter the Lakehouse service instance:
+   ![](.topwrite/assets/image_1748337538227.png)
+
+2. Navigate to "Operations Monitoring" > "Monitoring and Alerting" page:
+   ![](.topwrite/assets/image_1749455648524.png)
+
+#### Using Built-in Rules
+
+As mentioned above, the product has built-in global monitoring rules available for selection and activation.
+
+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)
+
+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].
+
+#### Custom Monitoring Rules
+
+Built-in rules primarily provide overall monitoring from a global dimension, facilitating quick use. However, in practice, for some specific objects, there is also a need for finely-grained custom monitoring. In such cases, custom monitoring rule capabilities are needed.
+
+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)
+
+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.
+
+## Related Documents
+
+* It is strongly recommended that you further read the [Monitoring and Alerting](monitoring_and_alerting.md) help document to understand the complete usage guide for the Monitoring and Alerting module, especially to further understand core concepts such as monitoring rules, notification policies, alert events, and notification history.
+
+## Next Steps
+
+* None
+
+^

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

@@ -0,0 +1,93 @@
+# Getting Started: How to Quickly Run a SQL Query
+
+## Applicable Scenarios
+
+Lakehouse provides an integrated engine for data processing, transformation, and analysis, with SQL as its development language. This guide introduces how to quickly write and run a SQL statement for query analysis using the task development feature in Lakehouse Studio.
+
+## Prerequisites
+
+Before reading this guide, we recommend reviewing the following documents:
+
+* [Lakehouse Product Introduction](what_is_clickzetta_lakehouse.md)
+* [Key Concepts](key-concepts.md)
+* [Lakehouse Studio Quick Tour](lakehousestudio-tour.md)
+
+## How-to Guide
+
+To quickly run a SQL query in the UI, use the Data Development module in Lakehouse Studio. There are two approaches:
+
+### Method 1: Run with Sample SQL and Sample Data
+
+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)
+
+^
+
+You can also learn more about query analysis using sample data by reading [Quick Start Query Analysis with Sample Data](sample-data-using.md).
+
+### Method 2: Write and Run Your Own SQL
+
+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:
+
+1. Select the correct data Schema on the page. When writing code, you can reference tables under this Schema by their table names directly; otherwise, use the `schema.table` two-part or `workspace.schema.table` three-part format. Usually, the system default Schema is sufficient.
+
+2. Enter the SQL you want to run in the code editing area.
+
+3. Choose the appropriate compute cluster type. For ad-hoc queries or when you need faster query response times, the Analytics Purpose (AP) cluster is recommended. General Purpose (GP) clusters are suitable for large-volume offline, periodically scheduled task processing and analysis.
+
+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
+
+In addition to the **Run** operation, the system provides the following features as shown below:
+
+1. Global code search: Find files by code keywords
+2. Save: Save changes to the current file
+3. Format: Format the current code
+4. Version history: View the file's version history, with support for comparison and rollback
+5. Find: Search for code snippets within the current file by keyword
+6. Shortcuts: Display supported common shortcuts
+
+![](.topwrite/assets/image_1721531293556.png)
+
+## Limitations
+
+* Access control: Only users with the `workspace_admin` role or `workspace_dev` role can use the task development feature and run SQL.
+
+## Related Documents
+
+* Read [Task Development](ide.md) to learn more about the detailed features of the task development module.
+
+## Next Steps
+
+* [How to Quickly Upload and Import Local Data for Analysis](quick_start_upload_data.md)
+
+^

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

@@ -0,0 +1,69 @@
+# Getting Started: How to Quickly Upload and Import Local Data
+
+## Applicable Scenarios
+
+Lakehouse provides an integrated engine to support data processing, transformation, and analysis, using SQL as the development language. This document provides an overview of how to quickly write and run a SQL statement for data query and analysis through the task development feature module of Lakehouse Studio.
+
+## Prerequisite Reading
+
+Before reading this guide, it is recommended to complete reading and understanding the following documents:
+
+* [Lakehouse Product Introduction](what_is_clickzetta_lakehouse.md)
+* [Key Concepts](key_concepts.md)
+* [Lakehouse Studio Quick Tour](lakehousestudiotour.md)
+
+## Operation Guide
+
+You can add data to Lakehouse tables through the "Data Upload" feature available on the Lakehouse Studio interface.
+
+### Usage Notes
+
+* Suitable for relatively small (no larger than 2GB) local files (CSV, TXT, Parquet, Avro, ORC) to be uploaded directly to Singdata Lakehouse tables. No programming required, the simplest approach.
+* Currently only supports uploading one file at a time.
+* The data upload feature currently does not support parsing fields of the struct, map, and array data types within files.
+* Users with `workspace_admin`, `workspace_dev`, or `workspace_analyst` role permissions are required to use the data upload feature.
+
+### Steps
+
+1. Log into your Singdata Studio account
+
+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)
+
+4. Schema: Choose to create the table under a certain schema.
+
+5. Select Table: Choose "New Table" and enter the new table name in the field behind.
+
+6. Cluster: The available cluster under the workspace where the current schema is located.
+
+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.
+   * Note: Modified field types may not match the system's parsing, potentially causing upload failure.
+
+## Related Documents
+
+* You can read the [Upload Data Using the Data Upload Feature](upload_data.md) help document to learn more about data upload methods, such as uploading data to existing tables.
+* You can read the [Comprehensive Guide to Ingesting Data into Lakehouse](a_comprehensive_guide_to_ingesting_data_into_clickzetta_lakehouse.md) to learn more ways to import data into Lakehouse.
+
+## Next Steps
+
+* After completing data upload, you can refer to the guide [How to Quickly Run a SQL Query](quick_start_sql_query.md) to query and analyze the data in the table.
+
+^

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

@@ -0,0 +1,72 @@
+# Quick Start: How to Add and Manage Users
+
+## Use Cases
+
+After completing product [registration and login](logging-in.md), you will receive an initial account with the highest global privileges, commonly referred to as the "account administrator" or "admin". You can use this account to access all product features. If you need to collaborate with colleagues and create individual accounts for different team members, please read this guide. Otherwise, you may skip this document and refer to the following guides to start using the product:
+
+* [How to Quickly Run a SQL Query](quick_start_sql_query.md)
+* [How to Quickly Upload and Import Data](quick_start_upload_data.md)
+
+## Prerequisites
+
+Before reading this guide, we recommend you review and understand the following documents:
+
+* [Singdata Lakehouse Product Introduction](what_is_clickzetta_lakehouse.md)
+* [Key Concepts](key_concepts.md)
+* [Lakehouse Studio Quick Tour](lakehousestudiotour.md)
+
+## Step-by-Step Guide
+
+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)
+
+4. Follow the on-screen instructions to fill in the required information. Please note 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:
+
+  ![](.topwrite/assets/image_1747990332688.png =446)
+
+## Related Documents
+
+You can read the following documents for more details on managing accounts and users:
+
+* [Manage Accounts](manageaccounts.md)
+* [Manage Users](account_user_management.md)
+
+## Next Steps
+
+* After creating user accounts, you may need to add users to workspaces and assign permissions. See:
+  * [How to Quickly Create and Use a Workspace](quick_start_create_workspace.md)
+  * [How to Quickly Manage Workspace Users](quick_start_workspace_user.md)
+
+* For the complete Lakehouse Studio user guide, see [Lakehouse Studio Complete User Guide](studio_manual.md)
+
+^

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

@@ -0,0 +1,72 @@
+# Building a Data Development Environment Using Workspaces
+
+## Basic Concepts
+
+A workspace is one of the core concepts in the Lakehouse product. It is used to organize Lakehouse resource objects (such as data objects and computing resources) and provides a relatively isolated environment for data development and scheduling task management and operations.
+
+To achieve both isolation and ease of data exchange within a service instance, permissions between different workspaces are isolated: a service instance user needs to be added to a workspace by the workspace administrator role (workspace\_admin) to be authorized and use the data or computing resources within the workspace.
+
+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.
+
+Using the objects in the figure above as an example, the isolation and data interoperability of workspaces are introduced:
+
+When the user user\_a is added to both workspace A (workspace\_a) and workspace B (workspace\_b) and is granted the necessary permissions for using computing clusters and querying data objects in both workspaces, user\_a can execute the following statements in the task script demo\_script\_ws\_a in workspace A and the task script demo\_script\_ws\_b in workspace B and obtain the query results normally.
+
+```
+select * from table workspace_a.schema_a.table_a limit 10;
+```
+
+User **user\_b** is only added to **Workspace B (workspace\_b**) and granted a set of permissions within **Workspace B**. When executing the task script **demo\_script\_ws\_b** to query **workspace\_a.schema\_a.table\_a**, an error message will indicate that **user\_b** does not have the **SELECT** permission on the table.
+
+## Usage Scenarios
+
+A service instance (instance) can create multiple workspaces. You can choose to use a single workspace or multiple workspaces based on your business needs. A single workspace facilitates unified management of data assets and computing resources; multiple workspaces facilitate natural boundaries of permissions, data, and computing resources between multiple teams or projects.
+
+## Using a Single Workspace
+
+When you are in the following usage scenarios, it is recommended to use only the default workspace as a single workspace to use Lakehouse:
+
+* **Individual or Small Team**: The team size is small, and the scale of data and computing is not large, hoping to collaborate and manage in the same environment.
+* **Single Product Line or Business Department**: Only need to manage the data and data processing flow of one business domain, with relatively low demand for fine-grained data and access control.
+
+After the service instance is activated, the system will create a workspace named "quick\_start" by default. You can directly use this workspace for task development and other work.
+
+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
+
+When you are in the following usage scenarios, it is recommended to create and use multiple workspaces:
+
+* **Cross-department or Multi-project Isolation**: When data and resource access need to be isolated between business departments or projects, multiple workspaces can achieve natural permission boundaries.
+* **High Security and Compliance Requirements**: Industries such as finance, healthcare, and government agencies that have high requirements for data security, compliance, and auditability need to enhance data security through strong isolation.
+* **Different Billing or Budget Centers**: If multiple departments or projects bear the budget separately, independent workspaces can facilitate financial settlement and cost tracking.
+
+The instance administrator (instance\_admin) role of the service instance can create workspaces. The operation method is as follows:
+
+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)
+
+^
+
+Once the workspace name is created, it cannot be changed. The new workspace will create a schema named "public" by default, and three different types of computing clusters (general computing cluster, analytical computing cluster, and synchronization computing cluster) to facilitate quick operations in the workspace.
+
+The user who creates the new workspace will be granted the workspace administrator (workspace\_admin) role by default.
+
+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)
+
+^
+
+A service instance user, if they need to use the data and computing resources in a workspace, needs to be added to the workspace and granted the corresponding permissions. This operation needs to be performed by a user with the workspace administrator (workspace\_admin) role. For more operation instructions, please refer to the relevant content in "Access Control" - "Configure Access Control" under [Workspace Level Management](access-control-configuration.md).