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

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

@@ -17,7 +17,6 @@ Singdata Lakehouse supports creating dependencies across workspaces. You can con
 
 ## Dependency Configuration Entry
 
-![](.topwrite/assets/image_1756107294537.png)
 After entering a specific task, click "Scheduling" in the task toolbar to open the scheduling configuration dialog.
 Click "Scheduling Dependencies" to select dependent tasks and configure dependency strategies and other behaviors.
 
@@ -36,32 +35,32 @@ Note: Once the downstream task is mounted with dependencies, two conditions must
 
 ### Same Cycle Dependency
 
-| Scenario Classification                | Task Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Diagram                                                                                                                                                                                                                                                                                                                                                                                |
-| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Daily Task B depends on Daily Task A   | Task A: Generates 1 instance every day at 19:00 Task B: Generates 1 instance every day at 09:00 Upstream daily task does not set self-dependency By default, the periodic instance of the downstream daily task mounts dependency to the periodic instance of the upstream daily task in the same cycle. Upstream daily task sets self-dependency Upstream daily task sets self-dependency, and there is a cross-cycle dependency when the downstream daily task depends on the upstream daily task. | ![](.topwrite/assets/7b129dadfb/98452de2e2b79fa155a55371b7f489e1d5cd5cfd.jpeg)  Note: Any type of self-dependency will create a dependency relationship with the previous cycle. If the previous cycle is not completed, it will prevent the next cycle's task from being scheduled. The diagram only demonstrates the daily cycle, subsequent types will not be repeatedly explained. |
-| Hourly Task B depends on Hourly Task A | Task A: 00:31-23:59 interval, generates an instance every 1 hour. A total of 24 instances, the first instance is at 00:31. Task B: 00:10-23:59 interval, generates an instance every 1 hour. A total of 24 instances, the first instance is at 00:10.                                                                                                                                                                                                                                                | ![](.topwrite/assets/7b129dadfb/ab5444530545f6680a270889074a85738a159cef.jpeg)                                                                                                                                                                                                                                                                                                         |
-|                                        | Task A: 12:30-15:59 interval, generate an instance every 1 hour. A total of 4 instances, the first instance at 12:31. Task B: 15:10-18:59 interval, generate an instance every 1 hour. A total of 4 instances, the first instance at 15:10.                                                                                                                                                                                                                                                          | ![](.topwrite/assets/7b129dadfb/1c635dd17ece33adb3faa5ca7ee5a8ab09a05b26.jpeg)                                                                                                                                                                                                                                                                                                         |
-| Minute Task B depends on Minute Task A | Task A: 00:00-01:59 interval, generate an instance every 5 minutes. A total of 12 instances, the first instance at 00:00. Task B: 00:10-00:59 interval, generate an instance every 5 minutes. A total of 10 instances, the first instance at 00:10.                                                                                                                                                                                                                                                  | ![](.topwrite/assets/7b129dadfb/8a0c5f6c04e1e9a55155bbc2724147788c169fcd.jpeg)                                                                                                                                                                                                                                                                                                         |
-|                                        | Task A: 00:22-00:59 interval, generate an instance every 5 minutes. A total of 8 instances, the first instance at 00:12. Task B: 00:36-00:59 interval, generate an instance every 5 minutes. A total of 5 instances, the first instance at 00:15.                                                                                                                                                                                                                                                    | ![](.topwrite/assets/7b129dadfb/03495a4d20f86aec92ca75c1c49b615dba8993f7.jpeg)                                                                                                                                                                                                                                                                                                         |
+| Scenario Classification                | Task Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Diagram                                                                                                                                                                                                                                                                                                                                                     |
+| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Daily Task B depends on Daily Task A   | Task A: Generates 1 instance every day at 19:00 Task B: Generates 1 instance every day at 09:00 Upstream daily task does not set self-dependency By default, the periodic instance of the downstream daily task mounts dependency to the periodic instance of the upstream daily task in the same cycle. Upstream daily task sets self-dependency Upstream daily task sets self-dependency, and there is a cross-cycle dependency when the downstream daily task depends on the upstream daily task. | ![](/.topwrite/assets/image_1780972223354.png =514)  Note: Any type of self-dependency will create a dependency relationship with the previous cycle. If the previous cycle is not completed, it will prevent the next cycle's task from being scheduled. The diagram only demonstrates the daily cycle, subsequent types will not be repeatedly explained. |
+| Hourly Task B depends on Hourly Task A | Task A: 00:31-23:59 interval, generates an instance every 1 hour. A total of 24 instances, the first instance is at 00:31. Task B: 00:10-23:59 interval, generates an instance every 1 hour. A total of 24 instances, the first instance is at 00:10.                                                                                                                                                                                                                                                | ![](/.topwrite/assets/image_1780972417902.png)                                                                                                                                                                                                                                                                                                              |
+|                                        | Task A: 12:30-15:59 interval, generate an instance every 1 hour. A total of 4 instances, the first instance at 12:31. Task B: 15:10-18:59 interval, generate an instance every 1 hour. A total of 4 instances, the first instance at 15:10.                                                                                                                                                                                                                                                          | ![](/.topwrite/assets/image_1780972441640.png)                                                                                                                                                                                                                                                                                                              |
+| Minute Task B depends on Minute Task A | Task A: 00:00-01:59 interval, generate an instance every 5 minutes. A total of 12 instances, the first instance at 00:00. Task B: 00:10-00:59 interval, generate an instance every 5 minutes. A total of 10 instances, the first instance at 00:10.                                                                                                                                                                                                                                                  | ![](/.topwrite/assets/image_1780972466642.png)                                                                                                                                                                                                                                                                                                              |
+|                                        | Task A: 00:22-00:59 interval, generate an instance every 5 minutes. A total of 8 instances, the first instance at 00:12. Task B: 00:36-00:59 interval, generate an instance every 5 minutes. A total of 5 instances, the first instance at 00:15.                                                                                                                                                                                                                                                    | ![](/.topwrite/assets/image_1780972530598.png)                                                                                                                                                                                                                                                                                                              |
 
 ### Large Cycle Depends on Small Cycle
 
-| Scenario                               | Dependency Description                                                                                                                                                                                                                                                                                     | Diagram                                                                                                                                                                                                                                                                                                  |
-| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Daily Task B depends on Hourly Task A  | Task A: 00:31-23:59, generate an instance every 1 hour. A total of 24 instances, the first instance at 00:31. Task B: generate 1 instance daily at 19:00.                                                                                                                                                  | ![](.topwrite/assets/7b129dadfb/0668799023e06d16554eec11c4ba182153ce5f66.jpeg)                                                                                                                                                                                                                           |
-| Hourly Task B depends on Hourly Task A | Task A: 00:31-23:59, generate an instance every 1 hour. A total of 24 instances, the first instance at 00:31. Task B: 00:10-23:59, generate an instance every 2 hours. A total of 12 instances, the first instance at 00:10.                                                                               | ![](.topwrite/assets/7b129dadfb/3d893243e925e6cfe57e9364facf592dd3ba2f07.jpeg)                                                                                                                                                                                                                           |
-|                                        | Task A: Interval from 05:31 to 11:59, generate an instance every 3 hours. A total of 3 instances are generated, with the first instance at 05:31. Task B: Interval from 07:10 to 17:59, generate an instance every 5 hours. A total of 3 instances are generated, with the first instance at 07:10.        | ![](.topwrite/assets/7b129dadfb/e310befdfa2f36d91bf0340f2c2c30172820f0f5.jpeg)                                                                                                                                                                                                                           |
-| Hourly Task B depends on Minute Task A | Task A: Interval from 00:08 to 01:59, generate an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:08. Task B: Interval from 00:15 to 00:59, generate an instance every 1 hour. A total of 1 instance is generated, with the first instance at 00:15.       | ![](.topwrite/assets/7b129dadfb/39973d157180d8aba3a98318be2e0da080614591.jpeg)                                                                                                                                                                                                                           |
-| Minute Task B depends on Minute Task A | Task A: Interval from 00:00 to 01:59, generate an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:00. Task B: Interval from 00:38 to 01:59, generate an instance every 20 minutes. A total of 4 instances are generated, with the first instance at 00:38. | ![](.topwrite/assets/7b129dadfb/b291ee71ad481cd0756c1ed8bda99fa310d21639.jpeg)  Note: If the minute granularity start and end range spans across hours, it will be automatically truncated. For example, the range of the second instance of Task B from left to right in the illustration is \[58, 60). |
+| Scenario                               | Dependency Description                                                                                                                                                                                                                                                                                     | Diagram                                                                                                                                                                                                                                                                       |
+| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Daily Task B depends on Hourly Task A  | Task A: 00:31-23:59, generate an instance every 1 hour. A total of 24 instances, the first instance at 00:31. Task B: generate 1 instance daily at 19:00.                                                                                                                                                  | ![](/.topwrite/assets/image_1780972554009.png)                                                                                                                                                                                                                                |
+| Hourly Task B depends on Hourly Task A | Task A: 00:31-23:59, generate an instance every 1 hour. A total of 24 instances, the first instance at 00:31. Task B: 00:10-23:59, generate an instance every 2 hours. A total of 12 instances, the first instance at 00:10.                                                                               | ![](/.topwrite/assets/image_1780972579351.png)                                                                                                                                                                                                                                |
+|                                        | Task A: Interval from 05:31 to 11:59, generate an instance every 3 hours. A total of 3 instances are generated, with the first instance at 05:31. Task B: Interval from 07:10 to 17:59, generate an instance every 5 hours. A total of 3 instances are generated, with the first instance at 07:10.        | ![](/.topwrite/assets/image_1780972621253.png)                                                                                                                                                                                                                                |
+| Hourly Task B depends on Minute Task A | Task A: Interval from 00:08 to 01:59, generate an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:08. Task B: Interval from 00:15 to 00:59, generate an instance every 1 hour. A total of 1 instance is generated, with the first instance at 00:15.       | ![](/.topwrite/assets/image_1780972670099.png)                                                                                                                                                                                                                                |
+| Minute Task B depends on Minute Task A | Task A: Interval from 00:00 to 01:59, generate an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:00. Task B: Interval from 00:38 to 01:59, generate an instance every 20 minutes. A total of 4 instances are generated, with the first instance at 00:38. | ![](/.topwrite/assets/image_1780972694187.png)
  Note: If the minute granularity start and end range spans across hours, it will be automatically truncated. For example, the range of the second instance of Task B from left to right in the illustration is \[58, 60). |
 
 ### Small Cycle Depends on Large Cycle
 
-| Scenario                               | Dependency Description                                                                                                                                                                                                                                                                               | Illustration                                                                   |
-| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
-| Hourly Task B depends on Daily Task A  | Task A: Generate 1 instance every day at 19:00. Task B: Interval from 00:31 to 23:59, generate an instance every 1 hour. A total of 24 instances are generated, with the first instance at 00:31.                                                                                                    | ![](.topwrite/assets/7b129dadfb/b0d5f070a0e56564e5abd3fed551c3fe5f59a98d.jpeg) |
-| Hourly Task B depends on Hourly Task A | Task A: Interval from 00:31 to 23:59, generate an instance every 2 hours. A total of 12 instances are generated, with the first instance at 00:31. Task B: Interval from 01:10 to 10:59, generate an instance every 1 hour. A total of 10 instances are generated, with the first instance at 01:10. | ![](.topwrite/assets/7b129dadfb/1f4ceabddf7f67a7857757b1df2cb2a87dc8445d.jpeg) |
-| Minute Task B depends on Hourly Task A | Task A: Interval from 00:15 to 00:59, generate an instance every 1 hour. A total of 1 instance is generated, with the first instance at 00:15. Task B: Interval from 00:08 to 01:59, generate an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:08. | ![](.topwrite/assets/7b129dadfb/809a2068b534db2d520a5f2fd421136cfdc17f22.jpeg) |
-| Minute Task B Depends on Minute Task A | Task A: 00:38-01:59 interval, generates an instance every 20 minutes. A total of 4 instances are generated, with the first instance at 00:38. Task B: 00:00-01:59 interval, generates an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:00.         | ![](.topwrite/assets/7b129dadfb/02eb9c9b349e305232f514e8d917769c9403d98c.jpeg) |
+| Scenario                               | Dependency Description                                                                                                                                                                                                                                                                               | Illustration                                   |
+| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
+| Hourly Task B depends on Daily Task A  | Task A: Generate 1 instance every day at 19:00. Task B: Interval from 00:31 to 23:59, generate an instance every 1 hour. A total of 24 instances are generated, with the first instance at 00:31.                                                                                                    | ![](/.topwrite/assets/image_1780972788359.png) |
+| Hourly Task B depends on Hourly Task A | Task A: Interval from 00:31 to 23:59, generate an instance every 2 hours. A total of 12 instances are generated, with the first instance at 00:31. Task B: Interval from 01:10 to 10:59, generate an instance every 1 hour. A total of 10 instances are generated, with the first instance at 01:10. | ![](/.topwrite/assets/image_1780972803587.png) |
+| Minute Task B depends on Hourly Task A | Task A: Interval from 00:15 to 00:59, generate an instance every 1 hour. A total of 1 instance is generated, with the first instance at 00:15. Task B: Interval from 00:08 to 01:59, generate an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:08. | ![](/.topwrite/assets/image_1780972820201.png) |
+| Minute Task B Depends on Minute Task A | Task A: 00:38-01:59 interval, generates an instance every 20 minutes. A total of 4 instances are generated, with the first instance at 00:38. Task B: 00:00-01:59 interval, generates an instance every 10 minutes. A total of 12 instances are generated, with the first instance at 00:00.         | ![](/.topwrite/assets/image_1780972838658.png) |
 
 ## Frequently Asked Questions
 

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

@@ -10,7 +10,6 @@ When configuring Private Link to access the Lakehouse network, to ensure that th
 
 You need to click "Create Role" on the Tencent Cloud Access Control page (<https://console.cloud.tencent.com/cam/role>) and select the role carrier as: Tencent Cloud Account:
 
-:-: ![](.topwrite/assets/image_1733066596983.png =383)
 
 Select "Other Main Account" for "Account Type";
 
@@ -18,12 +17,9 @@ Fill in the UID displayed on the Lakehouse page in the "Account ID";
 
 Check "Enable Verification" in the "External ID" option, and customize a string of characters for subsequent verification use.
 
-:-: ![](.topwrite/assets/image_1733066790847.png =813)
+
 
 In the "Configure Role Policy", find and check the "Private Network (VPC) Read-Only Access" policy (Lakehouse needs to call the DescribeVpcEndPoint and DescribeVpcEndPointService interfaces through this role);
 
-:-: ![](.topwrite/assets/image_1733067463964.png =753)
 
 Define the role name and click the "Complete" button to complete the role creation.
-
-:-: ![](.topwrite/assets/image_1733067522805.png =747)

package/bin/skills/lakehouse-doc-en/references/trial-account-quotas-and-limits.md

@@ -76,9 +76,7 @@ If you occupy too many system resources through abnormal usage, Singdata Lakehou
 
 ***
 
-## Contact Information
-
-![](.topwrite/assets/20250708-181924.jpeg =611)
+^
 
 * **Email**: <<service@singdata.com>>
 

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

@@ -1 +1,70 @@
 # Tutorial: Connect to Lakehouse
+
+Singdata Lakehouse supports multiple connection methods, from command-line tools to programming interfaces, meeting the access needs of different scenarios. Based on your role and technical preference, choose the most suitable connection method below.
+
+---
+
+## Connection Methods at a Glance
+
+| Connection Method | Best For | Recommended Users |
+|---------|---------|---------|
+| **cz-cli Command-Line Tool** | Terminal SQL operations, task management, Agent integration | Data engineers, AI Agent developers |
+| **JDBC Driver** | Java/Scala applications, direct BI tool connections | Application developers, BI engineers |
+| **Command-Line Client (sqlline)** | Java-based interactive SQL terminal | Technical users familiar with traditional database terminals |
+| **MySQL Protocol** | MySQL-compatible tools (Navicat, DataGrip, etc.) | Data analysts, DBAs |
+| **SQLAlchemy** | Python data applications, Jupyter Notebooks | Python developers, data scientists |
+
+---
+
+## Choose by Role
+
+### Data Engineer / Terminal User
+
+Recommended: **cz-cli** — configure a Profile once, and all subsequent SQL and task operations automatically use the same connection parameters, no need to enter a JDBC URL each time.
+
+→ [Connect with cz-cli Command-Line Tool](connect-with-cz-cli.md)
+
+### Java/Scala Application Developer
+
+Recommended: **JDBC Driver** — standard database connection interface that integrates directly into frameworks like Spring and Flink.
+
+→ [JDBC Driver](JDBC-Driver.md)
+
+### Python Developer / Data Scientist
+
+Recommended: **SQLAlchemy** — the standard database abstraction layer in the Python ecosystem, supporting both ORM and native SQL, suitable for Jupyter Notebook analysis scenarios.
+
+→ [Connect with SQLAlchemy](sqlalchemy.md)
+
+### BI Tool / Database Management Tool User
+
+Lakehouse is compatible with the **MySQL protocol**. Tools like Navicat, DataGrip, and DBeaver can connect directly and operate Lakehouse just like MySQL.
+
+→ [Connect with MySQL Protocol](use-mysql-client.md)
+
+### Technical Users Familiar with Traditional Database Terminals
+
+**sqlline** is a Java-based interactive SQL terminal. Enter SQL and get results back in real time — suitable for quick queries and data exploration.
+
+→ [Connect with Command-Line Client](connect-with-cli.md)
+
+---
+
+## Client Downloads
+
+For download links for all client drivers and toolkits, see [Downloads](Lakehouse-client-repository.md).
+
+---
+
+## Common Connection Parameters
+
+Regardless of which connection method you use, the following core information is required:
+
+| Parameter | Description | How to Obtain |
+|------|------|---------|
+| **Service Endpoint** | Service endpoint address | See [Cloud Region Endpoints](connect-with-cz-cli.md#cloud-region-endpoints) |
+| **Instance ID** | Instance identifier | Upper-left corner of the Studio homepage |
+| **Workspace** | Workspace name | Top dropdown in Studio |
+| **Schema** | Default Schema | Run `SHOW SCHEMAS` after connecting |
+| **VCluster** | Virtual Cluster name | Run `SHOW VCLUSTERS` after connecting |
+| **Username / Password** | Authentication credentials | Platform registered account |

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

@@ -28,7 +28,7 @@ Choose your onboarding path by role. Most scenarios can be completed in 30 minut
 
 **Step 3 — Build your data processing pipeline**
 
-[Dynamic Table Incremental Computation](incremental-computing.md) · [Studio Task Development and Scheduling](task-develop.md) · [End-to-End CDC Complete Example](czguide-intro-to-cdc-using-clickzetta-rtsync-dynamic-tables.md)
+[Dynamic Table Incremental Computation](incremental-computing.md) · [Studio Task Development and Scheduling](task-develop.md) · [Data Engineering Agent](dataagent.md) (natural language ETL development, task management) · [End-to-End CDC Complete Example](czguide-intro-to-cdc-using-clickzetta-rtsync-dynamic-tables.md)
 
 **Step 4 — Connect external tools**
 
@@ -79,6 +79,7 @@ Choose your onboarding path by role. Most scenarios can be completed in 30 minut
 | Call LLMs in SQL | [AI Functions (AI\_COMPLETE / AI\_EMBEDDING)](ai_function_in_sql.md) |
 | Manage and switch between multiple LLM models | [AI Gateway](aigateway.md) |
 | Natural language conversational data analysis | [Data Analytics Agent](datagpt_introduction.md) |
+| Natural language ETL development, task management, operations diagnostics | [Data Engineering Agent](dataagent.md) |
 | Python data processing + AI inference | [Zettapark Quick Start](zettapark-quick-start.md) |
 
 </td>
@@ -121,6 +122,7 @@ Choose your onboarding path by role. Most scenarios can be completed in 30 minut
 | Python data read/write | [Zettapark](zettapark-quick-start.md) · [clickzetta-connector](python_reference/connector.md) |
 | Business semantic layer queries | [Semantic View](semantic-view-overview.md) |
 | Collaborate with a specialized data sub-agent | [cz-cli agent run](setup_cz_cli.md) |
+| Browser automation Web Agent | [Singclaw](https://www.singclaw.ai/) |
 
 </td>
 </tr>
@@ -159,6 +161,7 @@ Choose your onboarding path by role. Most scenarios can be completed in 30 minut
 | Experience engine performance (TPC-H) | [Experience Performance with TPC-H Sample Data](get-started-with-sample-data.md) |
 | Write complex business analytics SQL | [SQL Usage Guide](considerations-for-using-sql.md) |
 | Use AI to analyze data conversationally | [Data Analytics Agent (DataGPT)](lakehousedatagpt-tour.md) |
+| Use AI for ETL development / task management | [Data Engineering Agent](dataagent.md) |
 | Build vector search / RAG knowledge base | [Vector Search](vector_search_ai.md) |
 | Process data with Python (Zettapark) | [Zettapark Quick Start](zettapark-quick-start.md) |
 | Migrate from Spark to Lakehouse | [Migration Guide](tutorial_migration.md) |

package/bin/skills/lakehouse-doc-en/references/unique-key.md

@@ -0,0 +1,167 @@
+# Unique Key (UNIQUE) in Lakehouse
+
+## Overview
+
+> **Important difference from traditional databases**
+>
+> The UNIQUE constraint in Singdata Lakehouse is an **informational constraint (declarative constraint)**, and its behavior differs fundamentally from traditional databases such as MySQL and PostgreSQL:
+>
+> - **Uniqueness is not enforced by default**: In the default mode (`DISABLE NOVALIDATE RELY`), the system does not validate uniqueness during SQL writes — duplicate values can be written normally.
+> - **Primary purpose is query optimization**: The UNIQUE constraint is mainly used to declare the data semantics of a column (or set of columns) to the query optimizer, helping it produce better execution plans for deduplication elimination, row count estimation, and join optimization.
+> - **Application layer must enforce uniqueness**: If strict uniqueness is required by the business, it must be guaranteed by the data writer — you cannot rely on the UNIQUE constraint to enforce it.
+
+The `UNIQUE` constraint declares that the values in one column or a combination of columns in a table are unique. Unlike a primary key (`PRIMARY KEY`), a UNIQUE constraint:
+
+- Allows NULL values in columns (primary key columns enforce NOT NULL);
+- Allows multiple UNIQUE constraints on a single table (only one primary key is allowed);
+- Is not used as the operation key for real-time writes (CDC UPSERT/DELETE).
+
+A UNIQUE constraint can only be specified at table creation (`CREATE TABLE`). **Adding it via `ALTER TABLE` is not supported.**
+
+## Syntax
+
+The UNIQUE constraint supports both column-level and table-level syntax, and both forms can include constraint modifiers.
+
+### Column-level syntax
+
+```sql
+CREATE TABLE t (
+    id int UNIQUE,
+    name string
+);
+```
+
+### Table-level syntax
+
+Table-level syntax supports single-column and multi-column composite unique keys:
+
+```sql
+-- Single column
+CREATE TABLE t (
+    id int,
+    name string,
+    UNIQUE(id)
+);
+
+-- Composite unique key
+CREATE TABLE t (
+    a int,
+    b int,
+    UNIQUE(a, b)
+);
+```
+
+### Constraint modifiers
+
+The UNIQUE constraint supports three groups of modifiers in a fixed order (consistent with PRIMARY KEY and FOREIGN KEY):
+
+```
+UNIQUE [ENABLE | DISABLE] [VALIDATE | NOVALIDATE] [RELY | NORELY]
+```
+
+| Modifier | Meaning | Default |
+|----------|---------|---------|
+| `ENABLE` / `DISABLE` | Whether to enforce validation on subsequent writes | `DISABLE` |
+| `VALIDATE` / `NOVALIDATE` | Whether existing data is required to satisfy the constraint | `NOVALIDATE` |
+| `RELY` / `NORELY` | Whether the optimizer trusts and uses this constraint for query optimization | `RELY` |
+
+When no modifiers are specified, the default behavior of a UNIQUE constraint is **`DISABLE NOVALIDATE RELY`**.
+
+## Default behavior: declarative constraint (no deduplication)
+
+In the default `DISABLE NOVALIDATE RELY` mode, the UNIQUE constraint is recorded only as metadata and **does not prevent duplicate values from being written**:
+
+```sql
+CREATE TABLE uk_demo (id int UNIQUE, name string);
+
+-- View the constraint
+DESC EXTENDED uk_demo;
+-- unique_keys: ((id) DISABLE NOVALIDATE RELY)
+
+-- Duplicate id values can both be written
+INSERT INTO uk_demo VALUES(1, 'a');
+INSERT INTO uk_demo VALUES(1, 'b');
+
+SELECT * FROM uk_demo;
+-- 1 | a
+-- 1 | b   (duplicate value was not blocked)
+
+-- Multiple NULLs are allowed
+INSERT INTO uk_demo VALUES(NULL, 'c');
+INSERT INTO uk_demo VALUES(NULL, 'd');
+-- Both writes succeed
+```
+
+## RELY and the optimizer
+
+`RELY` (the default) tells the optimizer it can trust the constraint and optimize queries based on it, even if the constraint is not enforced during writes. The optimizer uses RELY unique keys for:
+
+- Deduplication elimination (simplification of DISTINCT / GROUP BY);
+- Row count and NDV (number of distinct values) estimation;
+- Join cardinality estimation and plan selection.
+
+If the data does not actually satisfy uniqueness but the constraint is declared as RELY, the optimizer may produce incorrect results. In this case, use `NORELY` to tell the optimizer to ignore the constraint:
+
+```sql
+CREATE TABLE uk_demo (id int UNIQUE NORELY, name string);
+-- unique_keys: ((id) DISABLE NOVALIDATE NORELY)
+```
+
+## Actual behavior of modifier combinations
+
+The following table shows observed behavior for each modifier combination:
+
+| Declaration | DESC EXTENDED shows | Write behavior |
+|-------------|---------------------|----------------|
+| `UNIQUE` (default) | `DISABLE NOVALIDATE RELY` | Duplicates allowed, multiple NULLs allowed |
+| `UNIQUE ENABLE` | `ENABLE NOVALIDATE RELY` | Duplicates allowed (no VALIDATE means no check) |
+| `UNIQUE NORELY` | `DISABLE NOVALIDATE NORELY` | Duplicates allowed; optimizer ignores constraint |
+| Multiple `UNIQUE` | Each is `DISABLE NOVALIDATE RELY` | Allowed |
+
+> ⚠️ **Enforced uniqueness (`ENABLE VALIDATE`) is currently not usable**
+>
+> When `UNIQUE ... ENABLE VALIDATE` is declared, table creation succeeds (DESC shows `ENABLE VALIDATE RELY` and HASH bucketing with sort keys is auto-generated), but executing `INSERT` on the table produces a compiler error:
+>
+> ```
+> CZLH-65000: ... Table should have primary keys/unique keys
+> ```
+>
+> This limitation is unrelated to whether the column is declared NOT NULL. **If you need to enforce deduplication at write time, use a primary key (PRIMARY KEY) rather than a UNIQUE constraint.** See [Primary Key](primary-key.md) for details.
+
+## Relationship with PRIMARY KEY
+
+- A table's primary key is also recorded as a unique key, so `DESC EXTENDED`'s `unique_keys` field will include the primary key columns.
+- A table can define both a primary key and multiple (non-enforced) UNIQUE constraints.
+- A table **can have at most one enforced constraint**. If the primary key is already enforced (which is the default), declaring `UNIQUE ... ENABLE VALIDATE` will produce an error at table creation:
+
+```sql
+CREATE TABLE t (id int PRIMARY KEY, code int UNIQUE ENABLE VALIDATE);
+-- CZLH-42000: cannot enforce UNIQUE constraint with an enforced PRIMARY KEY
+```
+
+| Comparison | PRIMARY KEY | UNIQUE |
+|------------|-------------|--------|
+| Count per table | At most 1 | Multiple allowed |
+| Column nullability | Enforces NOT NULL | Allows NULL (multiple NULLs allowed) |
+| Real-time write (CDC) dedup key | Yes | No |
+| Default modifiers | `ENABLE VALIDATE RELY` | `DISABLE NOVALIDATE RELY` |
+| Primary purpose | CDC dedup + query optimization | Query optimization (declarative) |
+
+## Validation rules at table creation
+
+The system performs the following checks on UNIQUE constraints when creating a table:
+
+- **No duplicate column names within a single constraint**: `UNIQUE(a, a)` produces an error.
+- **No redundant constraints**: If a UNIQUE constraint is identical to the primary key, or is a superset of another unique key (or the primary key), an `unnecessary unique key` error is reported.
+- **At most one enforced constraint**: Multiple `ENABLE VALIDATE` constraints (including the primary key) produce an error.
+
+## Usage recommendations
+
+- Treat UNIQUE as a **hint to the optimizer**: If you know that a column is unique in practice (for example, a business primary key synced from an upstream system), declaring UNIQUE can help the optimizer generate better plans.
+- If the declared column may actually contain duplicates, use `NORELY` to prevent the optimizer from making incorrect simplifications based on the constraint.
+- When you need to **truly enforce deduplication at write time**, use a primary key (PRIMARY KEY) together with a real-time write interface — not a UNIQUE constraint.
+
+## References
+
+- [Primary Key](primary-key.md)
+- [CREATE TABLE Syntax](create-table-ddl.md)

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

@@ -0,0 +1,138 @@
+# Usage and Billing View
+
+`sys.information_schema.instance_usage` is a system view in Singdata Lakehouse that records resource consumption and billing details at the instance level. Each row represents the consumption of one SKU during a single billing period (hourly or daily), making it the primary source for bill reconciliation, cost attribution, and usage trend analysis.
+
+Data is retained from instance creation onward.
+
+***
+
+## Field Reference
+
+| Field                      | Type      | Description                                                                     |
+| -------------------------- | --------- | ------------------------------------------------------------------------------- |
+| `account_id`               | int       | Account ID                                                                      |
+| `account_name`             | string    | Account name (i.e. the instance name)                                           |
+| `instance_id`              | int       | Instance ID                                                                     |
+| `region_name`              | string    | Cloud region, e.g. `Alibaba Cloud - East China 2 (Shanghai)`                    |
+| `sku_category`             | string    | SKU category — see classification table below                                   |
+| `sku_name`                 | string    | Specific SKU name                                                                |
+| `workspace_id`             | string    | Workspace ID                                                                    |
+| `workspace_name`           | string    | Workspace name                                                                  |
+| `measurement_start`        | timestamp | Start of the billing period                                                     |
+| `measurement_end`          | timestamp | End of the billing period                                                       |
+| `measurements_unit`        | string    | Unit of measurement, e.g. `yuan/cru`, `yuan/GiB/day`, `yuan/gb`, `M Tokens`    |
+| `measurements_consumption` | double    | Actual consumption during the period (in the given unit)                        |
+| `price_rate`               | string    | Unit price as a string, e.g. `"0.020000"`                                       |
+| `amount`                   | double    | Gross amount before discount (consumption × unit price)                         |
+| `discount_rate`            | double    | Discount rate: `1` means no discount, `0.8` means 20% off                       |
+| `total_after_discount`     | double    | Net amount after discount (the actual billed amount)                            |
+
+***
+
+## SKU Categories
+
+| `sku_category` | `sku_name` examples                                                                                                                        | Description                                           |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- |
+| `compute`      | GP Virtual Cluster, AP Virtual Cluster, Integration Virtual Cluster, Bulk Ingestion, Stream Ingestion, IGS Service, Task Scheduling        | Compute resource consumption, unit: `yuan/cru`        |
+| `storage`      | Managed Storage, Retained Managed Storage, Job Temp Storage, Managed User Volume Storage                                                   | Storage usage, unit: `yuan/GB/day` or `yuan/GiB/day`  |
+| `network`      | Query Internet Data Transfer                                                                                                               | Public internet egress, unit: `yuan/gb`               |
+| `ai`           | AI model calls (multiple models, input/output billed separately)                                                                           | AI function consumption, unit: `M Tokens`             |
+
+***
+
+## Query Examples
+
+### Total cost by SKU category over the last 7 days
+
+```
+SELECT
+  sku_category,
+  SUM(measurements_consumption) AS total_consumption,
+  SUM(amount)                   AS amount_before_discount,
+  SUM(total_after_discount)     AS total_cost
+FROM sys.information_schema.instance_usage
+WHERE measurement_start >= CURRENT_DATE() - INTERVAL 7 DAYS
+GROUP BY sku_category
+ORDER BY total_cost DESC;
+```
+
+### Monthly cost ranking by workspace
+
+```
+SELECT
+  workspace_name,
+  SUM(total_after_discount) AS total_cost
+FROM sys.information_schema.instance_usage
+WHERE measurement_start >= DATE_TRUNC('month', CURRENT_DATE())
+GROUP BY workspace_name
+ORDER BY total_cost DESC;
+```
+
+### Daily cost trend for a specific workspace
+
+```
+SELECT
+  DATE(measurement_start) AS date,
+  sku_category,
+  SUM(total_after_discount) AS daily_cost
+FROM sys.information_schema.instance_usage
+WHERE workspace_name = '<your_workspace>'
+  AND measurement_start >= CURRENT_DATE() - INTERVAL 30 DAYS
+GROUP BY DATE(measurement_start), sku_category
+ORDER BY date DESC, daily_cost DESC;
+```
+
+### CRU consumption breakdown for compute clusters
+
+```
+SELECT
+  workspace_name,
+  sku_name,
+  DATE(measurement_start)  AS date,
+  measurements_consumption AS cru_hours,
+  total_after_discount     AS cost
+FROM sys.information_schema.instance_usage
+WHERE sku_category = 'compute'
+  AND measurement_start >= CURRENT_DATE() - INTERVAL 7 DAYS
+ORDER BY date DESC, cost DESC;
+```
+
+### Workspaces exceeding a storage threshold
+
+```
+SELECT
+  workspace_name,
+  sku_name,
+  DATE(measurement_start)  AS date,
+  measurements_consumption AS storage_gib
+FROM sys.information_schema.instance_usage
+WHERE sku_category = 'storage'
+  AND measurements_consumption > 100
+  AND measurement_start >= CURRENT_DATE() - INTERVAL 7 DAYS
+ORDER BY storage_gib DESC;
+```
+
+### AI function token consumption
+
+```
+SELECT
+  workspace_name,
+  sku_name,
+  SUM(measurements_consumption) AS total_tokens_m,
+  SUM(total_after_discount)     AS total_cost
+FROM sys.information_schema.instance_usage
+WHERE sku_category = 'ai'
+GROUP BY workspace_name, sku_name
+ORDER BY total_cost DESC;
+```
+
+***
+
+## Notes
+
+* `storage` SKUs are measured at **daily** granularity; all other categories are measured **hourly**.
+* Data is not real-time — there is approximately a 4-hour delay before records appear.
+* `price_rate` is a string type. Cast it before arithmetic: `CAST(price_rate AS DOUBLE)`.
+* `total_after_discount` is the final billed amount. `amount` is the pre-discount gross. The difference is the discount applied.
+
+> ⚠️ **Note**: This view requires a user with the `instance_admin` role connected to the `sys` workspace. If your current workspace is not `sys`, use the three-part notation `sys.information_schema.instance_usage` to query across workspaces. Users without `instance_admin` will get empty results.

package/bin/skills/lakehouse-doc-en/references/use-dbt-dev.md

@@ -23,7 +23,7 @@ Enter a number: 1
 service (cn-shanghai-alicloud.api.clickzetta.com): cn-shanghai-alicloud.api.clickzetta.com
 instance (your_instance): <your_instance>
 workspace (your_workspace): <your_workspace>
-vcluster (default_ap): default
+vcluster (default_ap): DEFAULT
 username (your_username): <user_name>
 schema (default schema): dbt_dev
 password (password): <your_passwd>
@@ -49,7 +49,7 @@ cz_dbt_project:
       password: <passwd>
       workspace: <your_workspace_name>
       schema: dbt_prod
-      vcluster: default
+      vcluster: DEFAULT
     dev:
       type: clickzetta
       service: cn-shanghai-alicloud.api.clickzetta.com
@@ -58,7 +58,7 @@ cz_dbt_project:
       password: <passwd>
       workspace: <your_workspace_name>
       schema: dbt_dev
-      vcluster: default
+      vcluster: DEFAULT
 ```
 
 4. Verify the configuration

package/bin/skills/lakehouse-doc-en/references/use-java-sdk-realtime-uploaddata.md

@@ -152,7 +152,7 @@ public class Kafka2Lakehouse {
     }
     // Initialize Lakehouse client and realtimeStream
     private static void initialize() throws Exception {
-        String url = MessageFormat.format("jdbc:clickzetta://jnsxwfyr.uat-api.clickzetta.com/{0}?" + "schema={1}&username={2}&password={3}&vcluster={4}", workspace, schema, user, password, vc);
+        String url = MessageFormat.format("jdbc:clickzetta://jnsxwfyr.api.clickzetta.com/{0}?" + "schema={1}&username={2}&password={3}&vcluster={4}", workspace, schema, user, password, vc);
         Options options = Options.builder().withMutationBufferLinesNum(10).build();
         client = ClickZettaClient.newBuilder().url(url).build();
         realtimeStream = client.newRealtimeStreamBuilder().operate(RowStream.RealTimeOperate.APPEND_ONLY).options(options).schema(schema).table(table).build();

package/bin/skills/lakehouse-doc-en/references/use-java-sdk-upload-data-local.md

@@ -18,7 +18,7 @@ This document introduces how to use the Java SDK's BulkloadStream to batch load
 
 # Usage Example
 
-This example uses reading a local CSV file. The dataset used is the olist_order_items_dataset data from the [Brazilian E-commerce](https://www.kaggle.com/datasets/olistbr/brazilian-ecommerce?select=olist_order_items_dataset.csv) public dataset. If the data source is within the range supported by object storage or Lakehouse Studio data integration, it is recommended to use the COPY command or data integration features.
+This example uses reading a local CSV file. The dataset used is the olist\_order\_items\_dataset data from the [Brazilian E-commerce](https://www.kaggle.com/datasets/olistbr/brazilian-ecommerce?select=olist_order_items_dataset.csv) public dataset. If the data source is within the range supported by object storage or Lakehouse Studio data integration, it is recommended to use the COPY command or data integration features.
 
 ## Prerequisites
 
@@ -53,8 +53,8 @@ Add the Lakehouse Maven dependency to the project's `pom.xml` file. The latest v
 
 ### Writing Java Code
 
-1.  **Initialize Lakehouse Client and BulkloadStream**: Create the `BulkloadFile` class, initialize the Lakehouse connection and BulkloadStream object.
-2.  **Read Local CSV File and Write to Lakehouse**: Use Java IO streams to read the local CSV file and write data to Lakehouse line by line.
+1. **Initialize Lakehouse Client and BulkloadStream**: Create the `BulkloadFile` class, initialize the Lakehouse connection and BulkloadStream object.
+2. **Read Local CSV File and Write to Lakehouse**: Use Java IO streams to read the local CSV file and write data to Lakehouse line by line.
 
 ```java