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

package/bin/skills/lakehouse-doc-en/references/federation-query.md

@@ -7,7 +7,7 @@ Federation Query lets you query data in external data systems (Hive, Databricks,
 ## Supported External Data Sources
 
 | External System | Connection Method | Typical Use Case |
-|---------|---------|---------|
+|-----------------|-------------------|------------------|
 | Apache Hive | Hive Metastore URIs | In-place acceleration of existing Hive warehouses, replacing Presto/Trino |
 | Databricks Unity Catalog | Databricks API | Cross-platform federated analytics without moving Databricks data |
 | Iceberg REST Catalog | Iceberg REST API | Query any data lake compatible with the Iceberg REST protocol |
@@ -17,9 +17,58 @@ Federation Query lets you query data in external data systems (Hive, Databricks,
 
 ## Core Concepts
 
-**External Catalog** is the entry point for federation queries. It maps the metadata catalog of an external data system into Lakehouse, accessed using three-level naming: `catalog.schema.table`.
+There are three independent approaches to access external data, each suited to different scenarios:
 
-**External Schema** is an alternative approach that mounts an external Hive database into the current workspace, using two-level naming `schema.table`. It is better suited for integrating a Hive database into an existing workspace.
+### External Catalog (Recommended)
+
+Maps an external data system (Hive/Databricks/Snowflake/Iceberg REST) as a top-level catalog; the Schemas and Tables underneath automatically correspond to the external system's structure:
+
+```
+External Catalog                ← Top-level catalog, maps the external system
+  └── External Schema           ← Corresponds to a Schema/Database in the external system
+        └── External Table      ← Corresponds to an actual table in the external system
+```
+
+Queries use three-level naming: `external_catalog.schema.table`
+
+```sql
+SELECT * FROM databricks_catalog.table_types_demo.orders_external;
+```
+
+Supports: Hive, Databricks Unity Catalog, Iceberg REST (including Snowflake Open Catalog)
+
+### External Schema (Standalone)
+
+Without going through an External Catalog, directly mounts an external Hive Database into the **current Workspace's internal Catalog**, using two-level naming `schema.table` (equivalent to `<current internal catalog>.schema.table`). Direct HMS mapping — all tables under the entire Database are immediately queryable, and newly added tables are automatically visible without per-table definitions.
+
+```sql
+SELECT * FROM hive_orders.order_detail LIMIT 100;
+```
+
+Supports: Hive (OSS/COS/GCS/HDFS). Read-only; DML is not supported.
+
+### External Table (Standalone)
+
+Creates a single table pointing to external storage under an ordinary Schema in the **current Workspace's internal Catalog**, using two-level naming `schema.table`. Unlike External Schema: column names and types can be customized, and renaming and modifying comments are supported.
+
+```sql
+CREATE EXTERNAL TABLE my_schema.delta_orders
+    LOCATION 's3://bucket/orders/'
+    USING DELTA;
+```
+
+Supports: Kafka, Delta Lake, Hudi. Read-only; DML is not supported.
+
+### Comparison of the Three Approaches
+
+| | External Catalog | External Schema (Standalone) | External Table (Standalone) |
+|---|---|---|---|
+| Catalog location | Independent external Catalog | Current Workspace's internal Catalog | Current Workspace's internal Catalog |
+| Naming | Three-level `catalog.schema.table` | Two-level `schema.table` | Two-level `schema.table` |
+| Use case | Cross-platform federated analytics | Mount an entire Hive database into the workspace | Custom mapping for a single external table |
+| Supported sources | Hive, Databricks, Iceberg REST, Snowflake | Hive | Kafka, Delta Lake, Hudi |
+| Schema definition | Auto-mapped from external system | Auto-mapped from HMS | Manually define column names and types |
+| New external tables visible | Requires re-mapping | Automatically visible | Must be created one by one |
 
 Selection guide: [External Catalog vs External Schema](org-hierarchy.md)
 
@@ -58,10 +107,10 @@ JOIN my_lakehouse_table u ON o.user_id = u.id;
 ## This Section
 
 | Page | Description |
-|------|------|
+|------|-------------|
 | [External Object User Guide](external_object_user_guide.md) | Complete operations for creating, querying, and managing External Catalog / Schema / Table |
 | [Query Snowflake OpenCatalog Iceberg Tables](query-snowflake-open-catalog-iceberg-table.md) | Federated queries on Snowflake-managed Iceberg data via Iceberg REST API |
-| [Databricks Cross-Platform Data Federation](databricks_yunqi_integration_guide_v2.md) | Best practices for cross-platform federation between Databricks Unity Catalog and Singdata Lakehouse |
+| [Databricks Unity Catalog Federation Query Practice](databricks-external-catalog-practice.md) | Full step-by-step setup guide with verified results and common error troubleshooting |
 
 ---
 
@@ -71,4 +120,5 @@ JOIN my_lakehouse_table u ON o.user_id = u.id;
 - [External Catalog Federation Query Guide](external-catalog-concept.md) — Detailed operation examples and architecture principles
 - [Create External Catalog](create-external-catalog.md) — DDL syntax reference
 - [Create Hive Catalog](create-hive-catalog.md) — Hive connection configuration details
-- [In-Place Lake Acceleration Guide](lakehouse-acceleration-guide.md) — Complete guide for replacing Spark/Hive and Presto/Trino without moving data
+- [In-Place Lake Acceleration Guide](lakehouse-acceleration-guide.md) — Complete guide for replacing Spark/Hive and Presto/Trino without moving data
+- [Databricks Unity Catalog Federation Query Practice](databricks-external-catalog-practice.md) — Full step-by-step setup guide with verified results

package/bin/skills/lakehouse-doc-en/references/finebi-mysql.md

@@ -1,3 +1,5 @@
+# FineBI Connection Guide
+
 FineBI is a Business Intelligence product launched by FanRuan Software Co., Ltd. FineBI is a new-generation big data analytics BI tool designed to help business personnel fully understand and utilize their data. This article describes how to use the MySQL protocol to connect to Lakehouse.
 
 # Prerequisites

package/bin/skills/lakehouse-doc-en/references/get-started-with-sample-data.md

@@ -5,14 +5,14 @@
 Through this tutorial, you will learn how to use the built-in sample dataset of the Lakehouse platform to quickly use SQL for query analysis and evaluate SQL functionality and performance without preparing data in advance.
 
 > This tutorial leverages the Lakehouse Tutorial, providing an online tutorial guide and script import function. After logging into the Lakehouse Web console, you can enter the tutorial through the Lakehouse Tutorial entry and follow the online guide to complete the tutorial.
-> ![](.topwrite/assets/image_1736854694431.png)
+
 
 ### Import Script
 
 Open the "Lakehouse Tutorial" page in the console and select the "Quick Start Query Analysis with Sample Data" course. Follow the prompts on the page to import the script files needed for this course.
 
 View the "Tutorial\_Run\_TPCH\_Queries\_USING\_SQL" directory in the "Development Module".
-![](.topwrite/assets/image_1725286019515.png)
+
 
 ### Sample Dataset
 
@@ -32,34 +32,33 @@ Through the above steps, you will be able to evaluate the performance of SQL que
 ## Preparation
 
 First, after logging into the Lakehouse Web console and entering the specified workspace, you can access the data module to check if the relevant tables under "clickzetta\_sample\_data.tpch\_100g" exist in the data object list under data management.
-![](.topwrite/assets/image_1716285499384.png)
+
 
 Next, we will temporarily create an independent compute cluster for query analysis for this test. You can create a new cluster through the "Compute → Clusters" menu in the Lakehouse Web console by following the page wizard.
-![](.topwrite/assets/tpch_100g_vc.png)
+
 
 At the same time, you can also create a cluster through SQL commands. When operating through SQL commands, you can control cluster creation, scaling, pausing/resuming, and destruction actions without leaving the SQL development context, often improving the efficiency of computing resource operations during Ad-hoc or ETL development processes.
 
 This tutorial creates the compute cluster needed for analyzing the TPCH dataset by running the \[Tutorials/Tutorial\_Run\_TPCH\_Queries\_USING\_SQL/Step01.Preparation] SQL script task in the "Development" module.
-![](https://studio-prod-sh.oss-cn-shanghai.aliyuncs.com/fe-asset/tutorials/resources/tu_tpch_vc01.png?OSSAccessKeyId=LTAI5tBH4MDxrfQw7VTx4w2B\&Expires=1880885164\&Signature=wYmSy3IVRKBT7mWtGhuKwT%2BwufQ%3D)
+
 
 ## TPC-H Query on Sample Data
 
 Open the \[Tutorials/Tutorial\_Run\_TPCH\_Queries\_USING\_SQL/Step02.Run\_TPCH\_Queries] SQL script file in the "Development" module. You will see that the 22 TPC-H query statements have been entered. Select the test cluster just created from the \[Cluster] dropdown list, then select all scripts in the task and click the \[Run] button to perform serial queries.
-![](.topwrite/assets/image_1725354834261.png)
+
 
 After execution, you can view the runtime of this task through the current SQL Editor's run history.
 
 If you want to perform performance testing, you can execute the queries more than twice consecutively so that the compute cluster can fully cache the data and achieve optimal performance. The following is the result of the second run, showing a significant performance improvement after the compute cluster caches the data compared to the first run without caching.
-![](https://studio-prod-sh.oss-cn-shanghai.aliyuncs.com/fe-asset/tutorials/resources/tu_tpch_run_queries2.png?OSSAccessKeyId=LTAI5tBH4MDxrfQw7VTx4w2B\&Expires=1880886165\&Signature=XHaygkpuFRtqy%2FG1EExOjIfq7vw%3D)
+
 
 If you want to see the execution details of each of the 22 queries, you can access Compute → Job History, filter the query history by the query tag "tpch100g\_benchmark" and view it.
 
-![](.topwrite/assets/image_1716285600039.png)
 
 ## Query After Expanding Cluster Specifications
 
 Through the Compute → Cluster Management page, you can modify the size of the test cluster you just created, changing it from Large to XLarge, where the XLarge size is twice that of Large.
-![](https://studio-prod-sh.oss-cn-shanghai.aliyuncs.com/fe-asset/tutorials/resources/tu_tpch_resize_vc.png?OSSAccessKeyId=LTAI5tBH4MDxrfQw7VTx4w2B\&Expires=1880886486\&Signature=MJGwOtPq%2BHpD5E1WsHu1iyGrDnQ%3D)
+
 
 Or execute the following command in the SQL script to modify:
 
@@ -69,11 +68,11 @@ alter vcluster TPCH_100GB SET VCLUSTER_SIZE = 'XLARGE';
 ```
 
 After modification, use the resized cluster to perform the query test again.
-![](https://studio-prod-sh.oss-cn-shanghai.aliyuncs.com/fe-asset/tutorials/resources/tu_tpch_round2.png?OSSAccessKeyId=LTAI5tBH4MDxrfQw7VTx4w2B\&Expires=1880886763\&Signature=UCaQAhoOLbeCKPrNUz22TVfAXNs%3D)
+
 After the new expanded compute nodes are fully cached, the performance will continue to improve.
 By observing the runtime of the job, it can be seen that with the same data scale and query tasks, by increasing the size of the compute cluster, the overall runtime of the task is greatly reduced. After two executions, as the data is cached, query performance can be improved.
 
 ## Environment Cleanup
 
 Open the "Development" module \[Tutorial\_Run\_TPCH\_Queries\_USING\_SQL->Step03.Clean\_Up] SQL script file, and execute the script to delete the test cluster for this tutorial.
-![](.topwrite/assets/image_1725288859033.png)
+

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

@@ -7,7 +7,6 @@ If the address of the Git repository you need to associate is not public, you ne
 Operation entry: Left navigation menu -> More -> Associate Git
 
 Click Add to create an account link.
-![](/.topwrite/assets/image_1775805505891.png)
 
 Display Name: A user-defined name for the currently managed account.
 
@@ -18,7 +17,6 @@ Access Token: The access token created by the user in GitLab. Note that if you n
 ## Create Git Folder
 
 On the development page, click "New" and select the "Git Folder" type to create a special folder type associated with a Git repository.
-![](/.topwrite/assets/image_1775805519588.png)
 
 **Type**: Git Folders support two types. Only Git Folders of the same type can be created within the same workspace.
 
@@ -42,7 +40,6 @@ After creating a Git Folder, the content of the remote repository will be cloned
 > Singdata Studio will only clone content that complies with the Singdata task script specification. If there is content in the remote repository that does not comply with the specification, it will be automatically filtered out.
 
 Click the "Git" button on the toolbar to open the Git operation panel. Through this panel, you can implement version control, collaboration, and CI/CD with the remote Git repository. The Git panel supports operations including: Commit and Push, Pull, Branch Merge, and visual diff comparison during commits.
-![](/.topwrite/assets/image_1775805531974.png)
 
 1. The branch you are currently using. This is the branch you selected for cloning when creating the Git Folder. Switching to other branches is currently not supported.
 2. Commit your work to the working branch and push the updated branch to the remote Git repository.
@@ -55,3 +52,5 @@ Click the "Git" button on the toolbar to open the Git operation panel. Through t
 
 6. Add a commit message, and optionally add a detailed description of the changes.
 7. Display the current branch history.
+
+^

package/bin/skills/lakehouse-doc-en/references/grant-privileges.md

@@ -1,3 +1,5 @@
+# GRANT
+
 ## Function Description
 
 Grants specified privileges to a role or user, enabling fine-grained access control for workspace resources.

package/bin/skills/lakehouse-doc-en/references/iceberg-rest-catalog-databricks.md

@@ -0,0 +1,166 @@
+# Accessing Databricks Iceberg Tables via Iceberg REST Catalog
+
+Singdata Lakehouse accesses Iceberg-format tables in Databricks Unity Catalog through the Iceberg REST Catalog protocol. Metadata is synchronized in real time, and data remains in the original S3 storage without any migration.
+
+![](.topwrite/assets/anim-16-iceberg-rest-databricks.svg)
+
+---
+
+## Prerequisites
+
+- Databricks workspace: Unity Catalog must be enabled
+- Singdata Lakehouse instance: must be on the same cloud platform (both AWS) as the Databricks data storage (S3)
+- Iceberg table data stored in an **S3 bucket you control**, with cross-account read permissions configured for the Lakehouse
+- Databricks Service Principal: OAuth Client ID and Secret already obtained
+
+---
+
+## Databricks-Side Preparation
+
+### 1. Obtain OAuth Credentials
+
+Go to `https://accounts.cloud.databricks.com` → **Service principals** → create or select a Service Principal → **Credentials & secrets** → record the Application ID (Client ID) and Secret.
+
+### 2. Grant Catalog Permissions
+
+```sql
+GRANT USE CATALOG ON CATALOG <catalog_name> TO `<application-id>`;
+GRANT USE SCHEMA ON SCHEMA <catalog_name>.<schema_name> TO `<application-id>`;
+GRANT SELECT ON SCHEMA <catalog_name>.<schema_name> TO `<application-id>`;
+GRANT EXTERNAL USE SCHEMA ON SCHEMA <catalog_name>.<schema_name> TO `<application-id>`;
+```
+
+### 3. Enable Metastore External Data Access
+
+Databricks Workspace → **Catalog** → gear icon → **Metastore** → **External data access** → enable.
+
+### 4. Iceberg Table Format Requirements (Critical)
+
+> ⚠️ **Note**: Only Iceberg-format tables can be queried via Iceberg REST Catalog. Tables in Delta, Parquet, CSV, and other formats are visible in `SHOW TABLES`, but `SELECT` will return `table not found`.
+
+| Table Format | SHOW TABLES | SELECT | Notes |
+|--------------|-------------|--------|-------|
+| **Iceberg** | ✅ | ✅ | The only supported type |
+| Delta | ✅ | ❌ | Metadata visible, cannot query |
+| Parquet / CSV / JSON | ✅ | ❌ | Same as above |
+
+Creating an Iceberg table in Databricks:
+
+```sql
+CREATE TABLE catalog.schema.my_iceberg_table
+USING ICEBERG
+LOCATION 's3://your-bucket/path/';
+```
+
+### 5. S3 Storage Requirements
+
+Iceberg table data must be in an **S3 bucket you control**. Tables in Databricks-managed storage (`s3://dbstorage-prod-*`) have accessible metadata, but data queries will return `S3 403 Forbidden`.
+
+The Lakehouse AWS account also needs read access to the S3 bucket. You can obtain the Lakehouse AWS account ID through technical support.
+
+---
+
+## Create a Catalog Connection
+
+```sql
+CREATE CATALOG CONNECTION IF NOT EXISTS databricks_iceberg_conn
+TYPE ICEBERG_REST
+URI = 'https://<workspace>.cloud.databricks.com/api/2.1/unity-catalog/iceberg-rest'
+OAUTH_SERVER_URI = 'https://<workspace>.cloud.databricks.com/oidc/v1/token'
+ACCESS_REGION = '<s3-bucket-region>'
+OAUTH_CLIENT_ID = '<oauth-client-id>'
+OAUTH_CLIENT_SECRET = '<oauth-client-secret>'
+OAUTH_SCOPE = 'all-apis'
+WAREHOUSE = '<databricks-catalog-name>';
+```
+
+### Parameter Reference
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `TYPE` | Yes | Fixed as `ICEBERG_REST` — do not add `=` |
+| `URI` | Yes | Iceberg REST API endpoint — note the **new path** `/iceberg-rest`, not the old path `/iceberg` |
+| `OAUTH_SERVER_URI` | **Yes** | Databricks OAuth token endpoint. Different path from URI — omitting it causes `Credential was not sent` |
+| `ACCESS_REGION` | Yes | Region of the S3 bucket, not the Databricks workspace region |
+| `OAUTH_CLIENT_ID` | Yes | Service Principal Application ID (UUID format) |
+| `OAUTH_CLIENT_SECRET` | Yes | Service Principal OAuth Secret |
+| `OAUTH_SCOPE` | Yes | Fixed as `all-apis` |
+| `WAREHOUSE` | Yes | Catalog name in Databricks Unity Catalog (e.g., `workspace`, `main`) |
+
+> ⚠️ **Note**: `TYPE = ICEBERG_REST` will cause a syntax error. The correct form omits `=`: `TYPE ICEBERG_REST`
+
+---
+
+## Create an External Catalog
+
+```sql
+CREATE EXTERNAL CATALOG databricks_iceberg_catalog
+  CONNECTION databricks_iceberg_conn;
+```
+
+> Note: Iceberg REST Catalog does not require `OPTIONS ('catalog' = '...')` — the warehouse was already specified in the connection above.
+
+---
+
+## Verification
+
+```sql
+-- Verify connectivity
+SHOW SCHEMAS IN databricks_iceberg_catalog;
+
+-- List tables
+SHOW TABLES IN databricks_iceberg_catalog.<schema>;
+
+-- Describe table structure
+DESC TABLE databricks_iceberg_catalog.<schema>.<iceberg_table>;
+
+-- Query data
+SELECT * FROM databricks_iceberg_catalog.<schema>.<iceberg_table> LIMIT 10;
+```
+
+---
+
+## Common Errors
+
+### `Credential was not sent or was of an unsupported type`
+
+`OAUTH_SERVER_URI` is not set. The Databricks OAuth token endpoint and the Iceberg REST endpoint are at different paths and must be specified separately.
+
+### Legacy Iceberg endpoints deprecated
+
+`URI` is using the old path `/iceberg`. Change to the new path `/iceberg-rest`.
+
+### Must provide 'warehouse' parameter
+
+`WAREHOUSE` is not set. Databricks' new Iceberg REST API requires the catalog name to be explicitly specified.
+
+### S3 403 Forbidden
+
+The Iceberg table data is in Databricks-managed storage (`s3://dbstorage-prod-*`), which Lakehouse does not have permission to read. You need to migrate the table data to a user-controlled S3 bucket and configure cross-account permissions.
+
+### table or view not found (on SELECT)
+
+The table is not in Iceberg format (it may be Delta / Parquet / CSV). `SHOW TABLES` displays all formats, but only Iceberg-format tables can be queried with `SELECT`.
+
+---
+
+## Management
+
+```sql
+-- View connection details
+DESC CONNECTION databricks_iceberg_conn;
+
+-- Drop Catalog
+DROP CATALOG databricks_iceberg_catalog;
+
+-- Drop connection
+DROP CONNECTION databricks_iceberg_conn;
+```
+
+---
+
+## Related Documentation
+
+- [Create Catalog Connection](create-catalog-connection.md) — Full DDL syntax
+- [Databricks Unity Catalog Federated Query Practice](databricks-external-catalog-practice.md) — TYPE DATABRICKS approach
+- [External Catalog Federated Query](SQL_External_Catalog_Guide.md)

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

@@ -5,4 +5,4 @@
 * [Task Group](task_group.md)
 * [Task Parameters](task_param.md)
 
-^
+^

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

@@ -6,7 +6,7 @@ A branch task implements conditional routing in workflow scheduling. It dynamica
 
 This article describes the structure and logic of branch tasks.
 
----
+***
 
 ## Use Cases
 
@@ -14,7 +14,7 @@ If you are designing a workflow and need to decide how to proceed based on the o
 
 ## How It Works
 
-![](/.topwrite/assets/image_1778741703249.png)
+^
 
 1. **Upstream task output**: The upstream task (SQL, Python, Shell, etc.) passes a dataset to the downstream branch node via the `$[output]` parameter.
 
@@ -26,7 +26,7 @@ If you are designing a workflow and need to decide how to proceed based on the o
 
 3. **Downstream task reference**: When a downstream task configures its dependency, it must specify which output name of the upstream branch node to associate with.
 
----
+***
 
 ## Steps
 
@@ -51,7 +51,7 @@ The output identifier produced after the branch condition is evaluated. Used to
 * When the branch condition is met: The downstream node associated with the corresponding output name is triggered.
 * When the branch condition is not met: The downstream node associated with the corresponding output name is not executed, and its status is set to **Ended because branch condition was not met**.
 
-Output name format: Supports Chinese characters, English letters, and underscores `_`. Maximum 128 characters. **Duplicate output names are not allowed within the same branch task.**
+Output name format: Supports Chinese characters, English letters, and underscores `_`. Maximum 128 characters. **Duplicate output names are not allowed within the same branch task**.
 
 **Branch Description**
 
@@ -79,82 +79,84 @@ Example: A branch node has two downstream nodes named `aaa` and `bbb`. When bran
 
 **Currently not supported**: Mathematical operations, date/time functions, JSON Path / object property access, regular expression matching, null coalescing, and similar functions.
 
----
+***
 
 ### Logical Functions
 
-| Function Signature         | Return Type | Description                                                                                                                                    |
-| -------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `and(arg1, arg2, ...)`     | `boolean`   | Returns `true` when all arguments convert to `true`. Supports 1 or more arguments. Example: `and(true, bool(1), equals('a', 'a'))` |
-| `or(arg1, arg2, ...)`      | `boolean`   | Returns `true` when any argument converts to `true`. Supports 1 or more arguments.                                                            |
-| `not(arg)`                 | `boolean`   | Returns the boolean negation of the argument.                                                                                                  |
+| Function Signature     | Return Type | Description                                                                                                                        |
+| ---------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `and(arg1, arg2, ...)` | `boolean`   | Returns `true` when all arguments convert to `true`. Supports 1 or more arguments. Example: `and(true, bool(1), equals('a', 'a'))` |
+| `or(arg1, arg2, ...)`  | `boolean`   | Returns `true` when any argument converts to `true`. Supports 1 or more arguments.                                                 |
+| `not(arg)`             | `boolean`   | Returns the boolean negation of the argument.                                                                                      |
 
----
+***
 
 ### Comparison Functions
 
 When both sides can be converted to numbers, comparison is numeric; otherwise, lexicographic string comparison is used.
 
-| Function Signature               | Return Type | Description                                          |
-| -------------------------------- | ----------- | ---------------------------------------------------- |
-| `equals(left, right)`            | `boolean`   | Returns `true` if the two normalized values are equal. |
-| `greater(left, right)`           | `boolean`   | `left > right`                                       |
-| `greaterOrEquals(left, right)`   | `boolean`   | `left >= right`                                      |
-| `less(left, right)`              | `boolean`   | `left < right`                                       |
-| `lessOrEquals(left, right)`      | `boolean`   | `left <= right`                                      |
+| Function Signature             | Return Type | Description                                            |
+| ------------------------------ | ----------- | ------------------------------------------------------ |
+| `equals(left, right)`          | `boolean`   | Returns `true` if the two normalized values are equal. |
+| `greater(left, right)`         | `boolean`   | `left > right`                                         |
+| `greaterOrEquals(left, right)` | `boolean`   | `left >= right`                                        |
+| `less(left, right)`            | `boolean`   | `left < right`                                         |
+| `lessOrEquals(left, right)`    | `boolean`   | `left <= right`                                        |
 
----
+***
 
 ### Collection Functions
 
 Collection functions apply to arrays (`List` / `Collection` / `JSONArray`) and strings. Some also support dictionaries (`JSONObject` / `Map`).
 
-| Function Signature                   | Return Type        | Description                                                                                                                                    |
-| ------------------------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `contains(container, expected)`      | `boolean`          | String: checks if the substring is contained. Collection: compares items by normalized value. JSONObject / Map: checks if the key exists.      |
-| `empty(value)`                       | `boolean`          | Returns `true` for `null`, empty string, empty collection, or empty JSONObject / Map.                                                          |
-| `first(value)`                       | First element      | String: returns the first character. List / Collection: returns the first element. Returns `null` when empty.                                  |
-| `last(value)`                        | Last element       | String: returns the last character. List / Collection: returns the last element. Returns `null` when empty.                                    |
-| `length(value)`                      | `integer`          | String: returns character count. Collection / Map: returns element count. Returns `0` for `null`.                                              |
-| `skip(value, count)`                 | Same as input type | Skips the first `count` characters or elements. Returns the original value when `count < 0`, non-integer, or `value` is `null`.               |
-| `take(value, count)`                 | Same as input type | Keeps the first `count` characters or elements. Returns the original value when `count < 0`, non-integer, or `value` is `null`.               |
-| `union(list1, list2, ...)`           | `List`             | Merges multiple lists with deduplication, preserving first-occurrence order. All arguments must be convertible to lists, otherwise returns `null`. |
-| `intersection(list1, list2, ...)`    | `List`             | Returns the intersection of multiple lists, ordered by the first list. All arguments must be convertible to lists, otherwise returns `null`.   |
-| `join(list, separator)`              | `String`           | Joins all list elements with the separator. The first argument must be convertible to a list, otherwise returns `null`.                        |
-
----
+| Function Signature                | Return Type        | Description                                                                                                                                        |
+| --------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `contains(container, expected)`   | `boolean`          | String: checks if the substring is contained. Collection: compares items by normalized value. JSONObject / Map: checks if the key exists.          |
+| `empty(value)`                    | `boolean`          | Returns `true` for `null`, empty string, empty collection, or empty JSONObject / Map.                                                              |
+| `first(value)`                    | First element      | String: returns the first character. List / Collection: returns the first element. Returns `null` when empty.                                      |
+| `last(value)`                     | Last element       | String: returns the last character. List / Collection: returns the last element. Returns `null` when empty.                                        |
+| `length(value)`                   | `integer`          | String: returns character count. Collection / Map: returns element count. Returns `0` for `null`.                                                  |
+| `skip(value, count)`              | Same as input type | Skips the first `count` characters or elements. Returns the original value when `count < 0`, non-integer, or `value` is `null`.                    |
+| `take(value, count)`              | Same as input type | Keeps the first `count` characters or elements. Returns the original value when `count < 0`, non-integer, or `value` is `null`.                    |
+| `union(list1, list2, ...)`        | `List`             | Merges multiple lists with deduplication, preserving first-occurrence order. All arguments must be convertible to lists, otherwise returns `null`. |
+| `intersection(list1, list2, ...)` | `List`             | Returns the intersection of multiple lists, ordered by the first list. All arguments must be convertible to lists, otherwise returns `null`.       |
+| `join(list, separator)`           | `String`           | Joins all list elements with the separator. The first argument must be convertible to a list, otherwise returns `null`.                            |
+
+***
 
 ### String Functions
 
-| Function Signature                      | Return Type    | Description                                                                                                                                                                  |
-| --------------------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `concat(arg1, arg2, ...)`               | `String`       | Concatenates all arguments in order. `null` arguments are ignored. Supports 1 or more arguments.                                                                            |
-| `guid()`                                | `String`       | Generates a random UUID string. Accepts no arguments.                                                                                                                       |
-| `indexOf(text, search)`                 | `integer`      | Returns the position of the first occurrence of the substring. Returns `-1` if not found.                                                                                   |
-| `lastIndexOf(text, search)`             | `integer`      | Returns the position of the last occurrence of the substring. Returns `-1` if not found.                                                                                    |
-| `replace(text, oldValue, newValue)`     | `String`       | Replaces all matching substrings. Returns empty string if `text` is `null`. Treats `oldValue` or `newValue` as empty string when `null`.                                    |
-| `split(text, separator)`                | `List<String>` | Splits the string by the separator. Splits by single character when separator is empty. Returns empty list if `text` is `null`.                                              |
-| `startsWith(text, prefix)`              | `boolean`      | Checks if the string starts with the specified prefix.                                                                                                                      |
-| `endsWith(text, suffix)`                | `boolean`      | Checks if the string ends with the specified suffix.                                                                                                                        |
-| `substring(text, start, length)`        | `String`       | Extracts `length` characters starting from position `start`. Returns empty string when `start` is out of bounds, arguments are invalid, or negative. Auto-truncates at end. |
-| `toLower(value)`                        | `String`       | Converts to lowercase. Returns empty string for `null`.                                                                                                                     |
-| `toUpper(value)`                        | `String`       | Converts to uppercase. Returns empty string for `null`.                                                                                                                     |
-| `trim(value)`                           | `String`       | Trims leading and trailing whitespace. Returns empty string for `null`.                                                                                                     |
-| `string(value)`                         | `String`       | Converts the value to a string. Returns empty string for `null`.                                                                                                            |
-
----
+| Function Signature                  | Return Type    | Description                                                                                                                                                                 |
+| ----------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `concat(arg1, arg2, ...)`           | `String`       | Concatenates all arguments in order. `null` arguments are ignored. Supports 1 or more arguments.                                                                            |
+| `guid()`                            | `String`       | Generates a random UUID string. Accepts no arguments.                                                                                                                       |
+| `indexOf(text, search)`             | `integer`      | Returns the position of the first occurrence of the substring. Returns `-1` if not found.                                                                                   |
+| `lastIndexOf(text, search)`         | `integer`      | Returns the position of the last occurrence of the substring. Returns `-1` if not found.                                                                                    |
+| `replace(text, oldValue, newValue)` | `String`       | Replaces all matching substrings. Returns empty string if `text` is `null`. Treats `oldValue` or `newValue` as empty string when `null`.                                    |
+| `split(text, separator)`            | `List<String>` | Splits the string by the separator. Splits by single character when separator is empty. Returns empty list if `text` is `null`.                                             |
+| `startsWith(text, prefix)`          | `boolean`      | Checks if the string starts with the specified prefix.                                                                                                                      |
+| `endsWith(text, suffix)`            | `boolean`      | Checks if the string ends with the specified suffix.                                                                                                                        |
+| `substring(text, start, length)`    | `String`       | Extracts `length` characters starting from position `start`. Returns empty string when `start` is out of bounds, arguments are invalid, or negative. Auto-truncates at end. |
+| `toLower(value)`                    | `String`       | Converts to lowercase. Returns empty string for `null`.                                                                                                                     |
+| `toUpper(value)`                    | `String`       | Converts to uppercase. Returns empty string for `null`.                                                                                                                     |
+| `trim(value)`                       | `String`       | Trims leading and trailing whitespace. Returns empty string for `null`.                                                                                                     |
+| `string(value)`                     | `String`       | Converts the value to a string. Returns empty string for `null`.                                                                                                            |
+
+***
 
 ### Conversion Functions
 
-| Function Signature | Return Type | Description                                                                          |
-| ------------------ | ----------- | ------------------------------------------------------------------------------------ |
+| Function Signature | Return Type | Description                                                                                                                        |
+| ------------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------- |
 | `bool(value)`      | `boolean`   | Returns a boolean value according to the built-in boolean conversion rules (see the type description at the top of this document). |
 
----
+***
 
 ## Related Documentation
 
-- [Task Parameters](task_param.md) — Using dynamic parameter values in condition expressions
-- [Task Parameter Syntax Reference](task_param_reference.md) — Full syntax for time expressions and built-in parameters
-- [Composite Task](composite_task.md) — Incorporating branch tasks into a DAG
-- [Task Development and Scheduling](task-develop.md) — Development and scheduling for SQL tasks
+* [Task Parameters](task_param.md) — Using dynamic parameter values in condition expressions
+* [Task Parameter Syntax Reference](task_param_reference.md) — Full syntax for time expressions and built-in parameters
+* [Composite Task](composite_task.md) — Incorporating branch tasks into a DAG
+* [Task Development and Scheduling](task-develop.md) — Development and scheduling for SQL tasks
+
+^

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

@@ -8,11 +8,11 @@ Context parameters, in parameter configuration, refer to configuring two special
 
 ## Usage Guide
 
-* **Upstream Node (Provider)**: Responsible for generating a value and using it as an output parameter.
+* **Upstream Node (Provider**): Responsible for generating a value and using it as an output parameter.
 
-  * **Configure and Assign Output Parameter**: The system captures the query result of the last line of the node's code (e.g., `SELECT * from table_A;`) and **assigns** it to a built-in output parameter **`outputs`**, then passes the value of this parameter to downstream nodes. The parameter value depends on the code execution result.
+  * **Configure and Assign Output Parameter**: The system captures the query result of the last line of the node's code (e.g., `SELECT * from table_A;`) and **assigns** it to a built-in output parameter \`\`, then passes the value of this parameter to downstream nodes. The parameter value depends on the code execution result.
 
-* **Downstream Node (Consumer)**: Receives and uses the value provided by the upstream node.
+* **Downstream Node (Consumer**): Receives and uses the value provided by the upstream node.
 
   * **Establish Scheduling Dependency**: Configure a scheduling dependency on the upstream node.
   * **Configure Input Parameter**: In the downstream node's **parameter configuration** area, add an input parameter and set its value source to the upstream node's output parameter.
@@ -21,12 +21,13 @@ Context parameters, in parameter configuration, refer to configuring two special
 ## Configuration Instructions
 
 ### Configure Output Parameters
-![](/.topwrite/assets/image_1775099138460.png)
+
+^
 
 If you wish to pass the current node's result to downstream, follow these steps:
 
 1. Click the node, then Parameters > Output Parameters
-2. Click "New", and the system will automatically fill in the built-in parameter $[output].
+2. Click "New", and the system will automatically fill in the built-in parameter $\[output].
 
 > If the task is of Python/Shell type, the output result defaults to the output of the last line, with result data split by delimiter.
 >
@@ -47,7 +48,7 @@ Configure the input parameter.
   * Upstream Dependency: From the currently configured upstream tasks, select those that have output parameters as the input parameter value source.
   * Others: To add a task with output parameters from elsewhere, use "Others" to select it. Once selected, the dependency on that task will be automatically configured.
 
-![](/.topwrite/assets/image_1775099157450.png)
+^
 
 #### Reference Parameters
 
@@ -67,4 +68,6 @@ If the upstream node passes the assigned result to downstream, the parameter val
   * Cell: `${param[i][j]}`.
   * If the upstream is Python/Shell (one-dimensional array): Row: `${param[i]}`.
 
-> *Indexes start from 0.*
+> *Indexes start from 0*.
+
+^