npm - @clickzetta/cz-cli-darwin-arm64 - Versions diffs - 0.5.15 → 0.5.17 - Mend

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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (243) hide show

package/bin/skills/lakehouse-doc-en/references/RemoteFunction-as-udf.md CHANGED Viewed

@@ -1,11 +1,8 @@
-# Developing Custom Functions (External Function)
+# External Function Overview
-An External Function (also called a Remote Function) is a user-defined function (UDF) created in Singdata Lakehouse using Python or Java. The function logic runs in a cloud function compute service (supports Alibaba Cloud FC and Tencent Cloud SCF) and interacts with Lakehouse via HTTP.
+Singdata Lakehouse supports user-defined functions (UDF/UDAF/UDTF) via the **External Function** mechanism. Unlike built-in SQL functions, External Function execution logic runs in a cloud function compute service (Alibaba Cloud FC, Tencent Cloud SCF, or AWS Lambda); Lakehouse calls them via HTTP and retrieves the result — **you write the function call in SQL, and the function body runs in Python or Java code on the cloud**.
-This lets you call capabilities not natively supported by Lakehouse from SQL:
-- **Online services**: Large language model APIs, cloud platform AI services (image recognition, OCR, translation, etc.)
-- **Offline capabilities**: Custom algorithms packaged for deployment, Hugging Face models, etc.
+The advantage of this mechanism is that you can introduce any third-party library (scikit-learn, jieba, PyTorch, etc.) to implement logic that native SQL functions cannot handle, while still calling them from SQL.
 ---
@@ -14,10 +11,11 @@ This lets you call capabilities not natively supported by Lakehouse from SQL:
 A user calls an External Function in SQL → Lakehouse sends an HTTP request to the external function compute service → retrieves the result and returns it.
 The creation process has four steps:
-1. Enable a cloud function compute service (Alibaba Cloud FC or Tencent Cloud SCF) and object storage
-2. Package and upload function code, dependency libraries, and model files to object storage
-3. Grant Lakehouse permission to access the function service and file packages
-4. Execute DDL to create the External Function and call it in SQL
+1. Enable a cloud function compute service (Alibaba Cloud FC / Tencent Cloud SCF / AWS Lambda) and object storage (OSS / COS / S3)
+2. Create a Storage Connection and External Volume, then package and upload function code and dependencies
+3. Create an API Connection to grant Lakehouse permission to call the function compute service
+4. Execute `CREATE EXTERNAL FUNCTION` to register the function and call it in SQL
 ---
@@ -29,7 +27,7 @@ The creation process has four steps:
 | UDAF (multiple rows in, single row out) | ❌ | ✅ |
 | UDTF (single row in, multiple rows out) | ❌ | ✅ |
-Runtime environments: Java 8 / Python 3.10. When compressed dependencies exceed 500 MB, use container image deployment instead — see [Using Hugging Face Image Recognition Model to Process Image Data](remotefunction-on-acr.md).
+Runtime environments: Java 8 / Python 3.10. When compressed dependencies exceed 500 MB, use container image deployment instead — see [Using Hugging Face Image Recognition Model to Process Image Data](RemoteFunction-on-acr.md).
 ---
@@ -37,7 +35,9 @@ Runtime environments: Java 8 / Python 3.10. When compressed dependencies exceed
 | Page | Description |
 |------|------|
-| [Introduction: External Function](remotefunction-intro.md) | Concepts, architecture, advantages, usage limits, and billing |
-| [Development Guide: Python3](remotefunction-dev-guide-python3.md) | Environment setup, code structure, dependency packaging, deployment to Alibaba Cloud FC |
+| [Introduction: External Function](RemoteFunction-intro.md) | Concepts, architecture, advantages, usage limits, and billing |
+| [Development Guide: Python3](RemoteFunction-dev-guide-python3.md) | Environment setup, code structure, dependency packaging, deployment to Alibaba Cloud FC |
 | [Development Guide: Java](external-function-dev-guide-java.md) | Java 8 function development, packaging, UDF/UDAF/UDTF implementation |
-| [Usage Guide: External Function](remotefunction-best-practice.md) | Complete workflow: authorization, creating connections, registering functions, calling in SQL |
+| [Usage Guide: External Function](RemoteFunction-best-practice.md) | Complete workflow: authorization, creating connections, registering functions, calling in SQL |
+| [CREATE EXTERNAL FUNCTION](create_external_function.md) | Complete DDL syntax and parameter reference |
+| [Storage Connection + API Connection + External Function Combo Practice](external-function-combo-practice.md) | End-to-end examples for three cloud environments (Alibaba Cloud / Tencent Cloud / AWS), including Python ML functions, 30 AI functions, and Java UDF/UDAF/UDTF |

package/bin/skills/lakehouse-doc-en/references/SQL_External_Catalog_Guide.md CHANGED Viewed

@@ -4,15 +4,6 @@
 Federated Queries allow Lakehouse to directly query data in external data catalogs (such as Hive Metastore, Databricks Unity Catalog) without migrating or copying data. Using `CREATE EXTERNAL CATALOG`, you can map external data sources as Catalogs within Lakehouse and use standard SQL for cross-system queries. This guide is organized by business scenario to help you quickly master federated query configuration methods.
-### Quick Navigation
-* [Create Hive External Catalog](#create-hive-external-catalog) -- Mount a Hive Metastore
-* [Query External Catalog Data](#query-external-catalog-data) -- Use three-level namespace queries
-* [View External Schemas and Tables](#view-external-schemas-and-tables) -- Explore external catalog structure
-* [Drop External Catalog](#drop-external-catalog) -- Clean up the federation connection
-***
 ## SQL Commands Covered
 | Command | Purpose | Use Case |
@@ -145,3 +136,4 @@ DROP CATALOG IF EXISTS hive_prod;
 * [External Catalog Introduction](external-catalog-summary.md)
 * [Create External Catalog](create-external-catalog.md)
 * [Create Hive Catalog](create-hive-catalog.md)
+* [Databricks Unity Catalog Federated Query Practice](databricks-external-catalog-practice.md) — Complete configuration steps, tested SQL, and error troubleshooting

package/bin/skills/lakehouse-doc-en/references/SUMMARY.md CHANGED Viewed

@@ -3,12 +3,15 @@
     * [Before You Begin](setup.md)
     * [Account Signup and Setup](logging-in.md)
     * [Supported Cloud Platforms](supported-cloud-platforms.md)
-    * [Pricing and Billing](pricing.md)
     * [Trial Account Quotas and Limits](trial-account-quotas-and-limits.md)
 * [Concept Index](concepts.md)
     * [Key Concepts](key-concepts.md)
     * [Lakehouse Studio Concept](lakehouse-studio-concept.md)
     * [Incremental Computing](incremental-computing.md)
+    * [Ecosystem](ecosystem.md)
+* [Pricing and Billing](pricing.md)
+    * [Lakehouse Pricing](pricing-lakehouse.md)
+    * [AI Gateway Pricing](pricing-ai-gateway.md)
 * [Tutorials](tutorials.md)
     * [Lakehouse Quick Start Experience Guide](lakehouse-quick-experience_guide.md)
     * [Lakehouse Studio Tour](lakehousestudio-tour.md)
@@ -29,11 +32,8 @@
         * [Connect Using Command Line Client](connect-with-cli.md)
         * [Connect Using MySQL Protocol](use-mysql-client.md)
         * [Connect Using SQLAlchemy](sqlalchemy.md)
+        * [Connect Using cz-cli](connect-with-cz-cli.md)
         * [Related Downloads](lakehouse-client-repository.md)
-        * [Quick Start with Copy Command](quickstart-with-copy-command.md)
-        * [Capture Change Data (CDC) and Data Processing through Singdata Lakehouse's Multi-table Real-time Sync and Dynamic Tables](czguide-intro-to-cdc-using-clickzetta-rtsync-dynamic-tables.md)
-        * [Ingesting Data from Alibaba Cloud Data Lake](ingesting-data-from-alibaba-cloud-datalake.md)
-        * [Real-time Data Sync from Oracle via Bluepipe](bluepipe-oracle-lakehouse-datasync.md)
     * [A Comprehensive Guide to Ingesting Data into Singdata Lakehouse](a_comprehensive_guide_to_ingesting_data_into_clickzetta_lakehouse.md)
         * [Overview](comprehensive_guide_to_ingesting_overview.md)
         * [Environment Setup and Test Data Generation](comprehensive_guide_to_ingesting_environment_and_data_generate.md)
@@ -305,9 +305,8 @@
         * [Full-Text Search and Text Analysis in Practice](sql_fulltext_search_guide.md)
         * [Vector Search and RAG Applications in Practice](sql_vector_search_guide.md)
 * [Federation Query](federation-query.md)
-    * [External Object User Guide](external_object_user_guide.md)
-    * [Query Snowflake Open Catalog Iceberg Table](query-snowflake-open-catalog-iceberg-table.md)
-    * [Databricks-Singdata Cross-Platform Data Federation](databricks_yunqi_integration_guide_v2.md)
+    * [Databricks Unity Catalog Federation Query Practice](databricks-external-catalog-practice.md)
+    * [Accessing Databricks Iceberg Tables via Iceberg REST Catalog](iceberg-rest-catalog-databricks.md)
 * [Data Lake Management and Analytics](datalake_volume_analytics.md)
     * [Data Lake Overview](datalake_overview.md)
     * [Data Lake Storage Connection](datalake-storage-connection.md)
@@ -335,12 +334,10 @@
         * [Unstructured Data Analysis](unstructure_data_analysis.md)
             * [Invoke AI Capabilities to Process Unstructured Data](datalake_unstructure_data.md)
     * [Data Lake Permissions](datalake_privilege.md)
-* [Developing Custom Functions](remotefunction-as-udf.md)
-    * [SQL Custom Function Guide](sql-function-guide.md)
-    * [Introduction: External Function](remotefunction-intro.md)
-    * [Development Guide: External Function (Python3)](remotefunction-dev-guide-python3.md)
-    * [Development Guide: External Function (Java)](external-function-dev-guide-java.md)
-    * [Usage Guide: External Function](remotefunction-best-practice.md)
+    * [Private Storage BYOS](bring_your_own_storage.md)
+        * [BYOS Overview](byos_general.md)
+        * [Alibaba Cloud BYOS Configuration](alicloud_byos_configuration.md)
+        * [Tencent Cloud BYOS Configuration](byos_tencentcloud_configuration.md)
 * [Data Sharing](data_sharing_guide.md)
     * [Data Sharing Overview](data-sharing.md)
     * [Cross-Account Data Sharing Guide](data_sharing_between_accounts_guide.md)
@@ -372,11 +369,8 @@
             * [Creating Tencent Cloud Privatelink Service](creating_tencentcloud_privatelinkservice.md)
             * [Obtaining Tencent Cloud ARN and ExternalID](tencentcloud_arn_and_externalid.md)
     * [Dynamic Data Masking](dynamic-mask.md)
+    * [Row-Level Security (Row Filter)](row-filter.md)
     * [Backup and Recovery](data-recover.md)
-    * [Private Storage](bring_your_own_storage.md)
-        * [BYOS Overview](byos_general.md)
-        * [Alibaba Cloud BYOS Configuration](alicloud_byos_configuration.md)
-        * [Tencent Cloud BYOS Configuration](byos_tencentcloud_configuration.md)
     * [Storage Encryption](storage_encryption.md)
 * [INFORMATION SCHEMA](information_schema_guide.md)
     * [Instance-Level INFORMATION SCHEMA](instance-information_schema.md)
@@ -393,6 +387,7 @@
     * [Real-Name Authentication](authentication.md)
     * [Account Funds](account-funds.md)
     * [Billing](billing.md)
+    * [Usage and Billing View](usageandbillingview.md)
 * [Connect Using Ecosystem Tools](ecosystem-all.md)
     * [Airbyte](airbyte.md)
     * [Datax](eco_integration/datax.md)
@@ -419,7 +414,6 @@
         * [MindsDB](mindsdb.md)
     * [Streamlit](eco_integration/streamlit.md)
     * [Logstash Connector](logstash.md)
-    * [Trino Connector](eco_integration/trino.md)
     * [Introduction to Spark Connector](spark-connector-summary.md)
     * [Using Spark Connector](spark-connector-use.md)
     * [Flink Write Connector](flink-write-connector.md)
@@ -468,37 +462,51 @@
         * [AI_TRANSCRIBE](ai_transcribe.md)
         * [Best practices](ai_function_best_practice.md)
             * [RRF Full-Text + Vector Hybrid Search Best Practices](rrf-fulltext-vector-hybrid-search-best-practices.md)
-            * [Create LLM Function](create-llm-function.md)
-            * [Create Embedding Function](create-embedding-function.md)
-* [AI + BI Unified Workflow](unified-workflow.md)
+            * [External AI Function Example 2: Create an LLM Function to Analyze Company Industry](create-llm-function.md)
+            * [External AI Function Example 1: Create an Embedding Function](create-embedding-function.md)
+    * [AI + BI Unified Workflow](unified-workflow.md)
+        * [AI + BI Unified Workflow Introduction](unified-workflow-intro.md)
+        * [Example: Incremental Processing of Vehicle Images in Object Storage](unified-workflow-demo.md)
     * [Lakehouse MCP Server](lakehousemcpserver.md)
-        * [Lakehouse MCP Server Introduction](lakehousemcpserver-intro.md)
+        * [Lakehouse MCP Server Introduction and Quick Deployment](lakehousemcpserver-intro.md)
         * [Dify Integrated with Lakehouse MCP Server](dify_integrated_with_lakehousemcpserver.md)
         * [N8N Integrated with Lakehouse MCP Server](n8n_integrated_with_lakehousemcpserver.md)
             * [Quick Analysis of Public Internet Data](analysis_internet_data_nyc_green_data.md)
-            * [NYC Green Taxi Data Clean Transform with MCP Server](nyc_green_taxi_data_clean_transform_with_mcp_server.md)
-            * [Multi-Cloud Instance Management with MCP Server](multi_cloud_instance_manage_with_mcp_server.md)
-            * [Charge Analysis with Lakehouse MCP Server](charge_analysis_with_lakehouse_mcp_server.md)
-            * [Using MCP to Solve Data Pipeline Issues](using_mcp_solute_data_pipeline_issue.md)
+            * [NYC Green Taxi Data Cleaning and Transformation](nyc_green_taxi_data_clean_transform_with_mcp_server.md)
+            * [Multi-Cloud Instance Management with Lakehouse](multi_cloud_instance_manage_with_mcp_server.md)
+            * [Cost Anomaly Analysis and Root Cause Identification](charge_analysis_with_lakehouse_mcp_server.md)
+            * [Data Operations Troubleshooting](using_mcp_solute_data_pipeline_issue.md)
 * [AI Gateway](aigateway.md)
     * [Product Introduction](introduction.md)
-    * [Model Pricing](modelprice.md)
+    * [Model Price](pricing-ai-gateway.md)
     * [Quick Start](quickstart.md)
+    * [Using Models](use-models.md)
+    * [Calling LLMs via SQL](lakehouse-ai-sql-analysis.md)
+    * [Analyzing Images in SQL](lakehouse-multimodal-ai-pipeline.md)
+    * [Model Management via cz-cli](lakehouse-ai-gateway-cz-cli.md)
 * [Conversational Analytics (Analytics Agent)](datagpt_introduction.md)
     * [Quick Start](datagpt_quickstart.md)
     * [User Guide](datagpt_tutorial.md)
         * [Data Source Management](datagpt_data_source.md)
+        * [Model Selection and Configuration](datagpt-model-config.md)
         * [Metrics and Answer Builder](metrics_answer_build.md)
         * [Scheduled Task](scheduled_task.md)
         * [Table Rendering](table_rendering.md)
         * [Web Search](web_search.md)
         * [Dashboard Version Management](dashboard-version-management-guide.md)
-        * [Data Governance, Answer Builder & Analysis Domains](analytics-agent-core-concepts.md)
         * [Chart Auto-Refresh Configuration](chart-auto-refresh-guide.md)
         * [Row-Level Permissions](row_level_permission.md)
     * [Best Practices](datagpt_bestpractice.md)
         * [Web Data Retrieval and Conversational Data Analysis](simpletosimple_bazhuayu_datagpt.md)
         * [Improve Answer Accuracy](answer-accuracy-improve.md)
+    * [API](open-api-overview.md)
+        * [Quick Start](open-api-quick-start.md)
+        * [GenerateAuthToken - Obtain Authentication Token](open-api-generate-auth-token.md)
+        * [CreateSession - Create a Conversation Session](open-api-create-session.md)
+        * [Text2InsightQuery - Submit a Data Analysis Request](open-api-text2insight-query.md)
+        * [SafeQuestionPoll - Poll for Question Results](open-api-safe-question-poll.md)
+        * [Text2InsightStop - Stop a Question](open-api-text2insight-stop.md)
+        * [Understanding Response Results](open-api-response-guide.md)
     * [Data Privacy](data_privacy.md)
 * [Singdata CLI (cz-cli)](cz-cli.md)
     * [Installation and Configuration Guide](setup_cz_cli.md)
@@ -578,6 +586,7 @@
             * [Partition](partition_table.md)
             * [Cluster](cluster-table.md)
             * [Primary Key](primary-key.md)
+            * [Unique Key](unique-key.md)
             * [Identity Column](identity-column.md)
             * [Generated Column](generated-column.md)
             * [Default Value](default-value.md)
@@ -1343,6 +1352,10 @@
     * [Import Feishu Data into Lakehouse](import-feishu-data.md)
 * [Data Lake Acceleration](datalake-acceleration.md)
     * [In-Place Data Lake Acceleration Implementation Guide](lakehouse-acceleration-guide.md)
+    * [Multi-Cloud Unified Data Lake Acceleration](lakehouse-multi-cloud-acceleration.md)
+    * [Volume + Pipe + Dynamic Table End-to-End Practice](lakehouse-volume-pipe-acceleration-guide.md)
+    * [Medallion Architecture Practice: Pure SQL Dynamic Table Approach](lakehouse-medallion-sql-dt-guide.md)
+    * [Storage Connection + API Connection + External Function Combo Practice](external-function-combo-practice.md)
 * [Migration Guide](tutorial_migration.md)
     * [Data Type Compatibility Reference](migration-sql-compatibility.md)
     * [Migrating Spark Data Engineering Best Practices Project to Singdata Lakehouse](migrate-spark-data-engineering-best-practices-to-lakehouse.md)
@@ -1350,6 +1363,11 @@
     * [Spark SQL Migration Guide](migration-spark-sql.md)
     * [PySpark → ZettaPark Migration: F1 Racing Data Engineering Project](pyspark-to-zettapark-migration-f1.md)
     * [Databricks → Lakehouse Migration: Medallion Three-Layer Data Warehouse](medallion-lakehouse-from-scratch.md)
+    * [Databricks Notebook → Lakehouse Migration: Retail Data Medallion Pipeline](databricks-notebook-to-studio-migration.md)
+    * [Databricks DLT → Lakehouse Migration: Apparel Retail Streaming Pipeline](databricks-dlt-to-lakehouse-migration.md)
+    * [Databricks Unity Catalog → Lakehouse Migration: Permissions and Governance](databricks-uc-governance-to-lakehouse-migration.md)
+    * [Databricks Jobs → Lakehouse Studio Migration: E-commerce ETL Pipeline](databricks-jobs-to-studio-migration.md)
+    * [Databricks Delta Tables → Lakehouse Migration](databricks-delta-to-lakehouse-migration.md)
     * [PySpark RDD → ZettaPark Migration: Web Log Analysis](rdd-to-zettapark-migration-weblog.md)
     * [Migrating Snowflake Real-Time ETL Pipeline to Singdata Lakehouse](migrate-snowflake-realtime-etl-to-lakehouse.md)
     * [Snowflake Dynamic Tables Migration: Bronze–Silver–Gold Three-Layer Pipeline](snowflake-dynamic-tables-to-lakehouse.md)
@@ -1358,6 +1376,7 @@
     * [Hive → Lakehouse Migration: E-commerce User Behavior Data Warehouse](hive-to-lakehouse-ecommerce.md)
     * [pandas → ZettaPark Migration: Retail Data Analysis](pandas-to-zettapark-migration-retail.md)
     * [DBT Snowflake Migration: TPC-H Data Warehouse Pipeline](dbt-snowflake-to-clickzetta-migration.md)
+    * [DBT Databricks → DBT-ClickZetta Migration: Financial Payment Data Pipeline](dbt-databricks-to-clickzetta-migration.md)
     * [DBT BigQuery Migration: Retail Data Warehouse Pipeline](dbt-bigquery-to-clickzetta-migration.md)
 * [Studio Task Development and Operations Practice](studio-task-practice.md)
     * [Studio Python Task Development Guide (ZettaPark)](studio-python-task-zettapark.md)
@@ -1408,6 +1427,7 @@
     * [Data Recovery from Mistakes: Using Time Travel to Restore Deleted and Modified Data](data-recovery-with-time-travel.md)
     * [New ELT method with Lakehouse](refactor-elt-practice.md)
     * [DataOps data security and stable production practice](dataops_practice.md)
+    * [Data Quality Check (DQC): SQL-Driven Automated Validation](lakehouse-dqc-guide.md)
 * [Optimize Computing Resources](optimizing-computing-resources.md)
     * [Analytical cluster planning, configuration, and practical use](analytics_cluster_best_practices.md)
 * [Performance Experience](performence_test.md)
@@ -1477,6 +1497,16 @@
     * [Analytics Agent Release Notes](datagpt-release.md)
         * [April 14, 2026 - v1.1](release-note-0414-1.1.md)
         * [May 19, 2026 - v1.2](release-note-2026-05-19.md)
+    * [AI Gateway Release Notes](aigatewayupdate.md)
+        * [February 5, 2026 - 1.0](aigw-2026-2-5-1.0.md)
+        * [March 8, 2026 - 1.0.1](aigw-2026-3-8-1.0.1.md)
+        * [March 29, 2026 - 1.0.2](aigw-2026-3-29-1.0.2.md)
+        * [April 28, 2026 - 1.1](aigw-2026-4-28-1.1.md)
+        * [May 12, 2026 - 1.1.1](aigw-2026-5-12-1.1.1.md)
+        * [May 15, 2026 - 1.2](aigw-2026-5-15-1.2.md)
+        * [May 21, 2026 - 1.3](aigw-2026-5-21-1.3.md)
+        * [May 28, 2026 - 1.4](aigw-2026-5-28-1.4.md)
+        * [June 3, 2026 - 1.5](aigw-2026-6-3-1.5.md)
 ## Other
 * [User Agreement](service-aggrement.md)

package/bin/skills/lakehouse-doc-en/references/WINDOWFUNCTION.md CHANGED Viewed

@@ -1,8 +1,8 @@
-# Window Function
+# Window Functions
 ## Overview
-Window Functions are a powerful analytical feature in Singdata Lakehouse SQL that allow you to perform calculations across a set of related rows, rather than just on individual rows. By using the WINDOW clause, you can define one or more named windows and then reference those windows in window functions, avoiding repetitive window specifications and making queries more concise and maintainable.
+Window Functions are a powerful analytical feature in Singdata Lakehouse SQL that allow calculations to be performed across a set of related rows, rather than just on individual rows. By using the WINDOW clause, you can define one or more named windows and then reference those windows in window functions, avoiding repetitive window specifications and making queries more concise and maintainable.
 ## Syntax
@@ -23,33 +23,29 @@ WINDOW <window_name> AS (<window_specification>, ...)
 1. **ROWS Frame**: Window frame based on row count
 2. **RANGE Frame**: Window frame based on value range
-## Environment Preparation
+## Test Data Setup
-### Create Test Table
+The following examples use a custom `sales` table (monthly sales data) to demonstrate various window function features. The PARTITION BY example in the Best Practices section uses the `doc_test.employees` table.
 ```sql
-CREATE TABLE IF NOT EXISTS sales(
-    month INT,
-    sales INT,
+CREATE TABLE IF NOT EXISTS sales (
+    month  INT,
+    sales  INT,
     profit DOUBLE
 );
-```
-### Insert Test Data
-```sql
 INSERT INTO sales (month, sales, profit) VALUES
 (1, 100, 0.1),
 (2, 120, 0.15),
-(3, 80, 0.05),
+(3,  80, 0.05),
 (4, 150, 0.2),
-(5, 90, 0.1),
+(5,  90, 0.1),
 (6, 110, 0.12);
 ```
 ## Usage Examples
-### Example 1: Moving Window Aggregation - Moving Sum and Moving Average
+### Example 1: Moving Window Aggregation — Moving Sum and Moving Average
 **Business Scenario**: Calculate the sum and average of sales for the current month and the two preceding months
@@ -80,7 +76,7 @@ WINDOW w AS (ORDER BY month ROWS BETWEEN 2 PRECEDING AND CURRENT ROW);
 ***
-### Example 2: Multi-Window Ranking - Quarterly and Annual Ranking
+### Example 2: Multi-Window Ranking — Quarterly and Annual Ranking
 **Business Scenario**: Simultaneously compute ranking within each quarter and across the full year
@@ -112,13 +108,13 @@ WINDOW w1 AS (PARTITION BY CEIL(month / 3) ORDER BY sales DESC),
 * The w1 window partitions by quarter (every 3 months), computing sales ranking within each quarter
 * The w2 window has no partition, computing sales ranking across the full year
-* CEIL(month/3) divides months into Q1 (months 1-3), Q2 (months 4-6), etc.
+* `CEIL(month/3)` divides months into Q1 (months 1–3), Q2 (months 4–6), etc.
 ***
-### Example 3: Cumulative Aggregation - Year-to-Date Statistics
+### Example 3: Cumulative Aggregation — Year-to-Date Statistics
-**Business Scenario**: Calculate cumulative sales and average profit margin from the beginning of the year to the current month
+**Business Scenario**: Calculate cumulative sales, average profit margin, etc. from the beginning of the year to the current month
 ```sql
 SELECT month, sales, profit,
@@ -149,7 +145,7 @@ WINDOW w AS (ORDER BY month ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW);
 ***
-### Example 4: Time Series Analysis - Period-over-Period Comparison
+### Example 4: Time Series Analysis — Period-over-Period Comparison
 **Business Scenario**: View each month's sales compared to the previous and next month, and the period-over-period change
@@ -179,9 +175,9 @@ WINDOW w AS (ORDER BY month);
 **Explanation**:
-* `LAG(sales, 1)`: Gets the sales from the previous row
-* `LEAD(sales, 1)`: Gets the sales from the next row
-* prev\_sales and next\_sales are NULL for the first and last rows, respectively
+* `LAG(sales, 1)`: Gets the sales value from the previous row
+* `LEAD(sales, 1)`: Gets the sales value from the next row
+* `prev_sales` and `next_sales` are NULL for the first and last rows respectively
 ***
@@ -223,7 +219,7 @@ WINDOW w AS (ORDER BY sales DESC);
 ***
-### Example 6: Position Functions - Accessing Values at Specific Positions
+### Example 6: Position Functions — Accessing Values at Specific Positions
 **Business Scenario**: Get the first, last, and nth values within the window
@@ -254,14 +250,53 @@ WINDOW w AS (ORDER BY month ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLO
 **Explanation**:
 * `FIRST_VALUE()`: Returns the value of the first row in the window
-* `LAST_VALUE()`: Returns the value of the last row in the window (requires UNBOUNDED FOLLOWING to see the actual last row)
+* `LAST_VALUE()`: Returns the value of the last row in the window (requires `UNBOUNDED FOLLOWING` to see the actual last row)
 * `NTH_VALUE(expr, n)`: Returns the value of the nth row in the window
 ***
-### Example 7: RANGE Window Frame - Value-Range-Based Windows
+### Example 6.1: IGNORE NULLS — Skip NULL Values When Accessing
+**Business Scenario**: Skip NULLs when accessing values, for example to forward-fill gaps with the most recent non-null value
+The value access functions `FIRST_VALUE`, `LAST_VALUE`, and `NTH_VALUE` support appending `IGNORE NULLS` after the function call, which skips NULL values during computation. The default behavior is `RESPECT NULLS` (NULLs participate in computation).
+```sql
+-- Prepare data containing NULLs
+CREATE TABLE w_nulls (id INT, v INT);
+INSERT INTO w_nulls VALUES (1, 10), (2, NULL), (3, 30), (4, NULL), (5, 50);
+SELECT id, v,
+       LAST_VALUE(v) IGNORE NULLS OVER (ORDER BY id) AS fill_down,
+       LAST_VALUE(v) OVER (ORDER BY id)              AS keep_null
+FROM w_nulls
+ORDER BY id;
+```
+**Execution Result**:
+```
++----+------+-----------+-----------+
+| id | v    | fill_down | keep_null |
++----+------+-----------+-----------+
+| 1  | 10   | 10        | 10        |
+| 2  | NULL | 10        | NULL      |
+| 3  | 30   | 30        | 30        |
+| 4  | NULL | 30        | NULL      |
+| 5  | 50   | 50        | 50        |
++----+------+-----------+-----------+
+```
+**Explanation**:
-**Business Scenario**: Find all records within a sales value range of +/-10 and compute statistics
+* `IGNORE NULLS`: Skips NULLs; the `fill_down` column fills gaps with the most recent non-null value
+* `RESPECT NULLS` (default): NULLs pass through as-is
+* Functions that support `IGNORE NULLS` / `RESPECT NULLS`: `FIRST_VALUE`, `LAST_VALUE`, `NTH_VALUE`
+* `LAG` and `LEAD` do not currently support `IGNORE NULLS`; using it will raise an error
+***
+**Business Scenario**: Find all records within a sales value range of ±10 and compute statistics
 ```sql
 SELECT month, sales,
@@ -294,7 +329,7 @@ WINDOW w AS (ORDER BY sales RANGE BETWEEN 10 PRECEDING AND 10 FOLLOWING);
 ***
-### Example 8: Comprehensive Analysis - Multi-Dimensional Business Reports (Advanced)
+### Example 8: Comprehensive Analysis — Multi-Dimensional Business Report (Advanced)
 **Business Scenario**: Generate a comprehensive analytical report including ranking, cumulative values, period-over-period comparison, and proportions
@@ -340,14 +375,14 @@ WINDOW
 * This example uses 3 different window definitions simultaneously
 * w1: Ordered by month, used for ranking and period-over-period comparison
 * w2: Cumulative window, used for YTD (Year-To-Date) calculations
-* w3: Full window, used for computing total sum and calculating proportions
-* Demonstrates how to achieve complex multi-dimensional analysis in a single query
+* w3: Full window, used for computing the total sum and calculating proportions
+* Demonstrates how to implement complex multi-dimensional analysis in a single query
 ***
-### Example 9: Data Bucketing - NTILE Function Application
+### Example 9: Data Bucketing — NTILE Function Application
-**Business Scenario**: Divide sales data into high, medium, and low tiers based on performance
+**Business Scenario**: Divide sales data into high, medium, and low performance tiers
 ```sql
 SELECT
@@ -382,7 +417,7 @@ WINDOW w AS (ORDER BY sales DESC);
 ***
-### Example 10: Cumulative Distribution - CUME\_DIST Function Application
+### Example 10: Cumulative Distribution — CUME\_DIST Function Application
 **Business Scenario**: Calculate the cumulative distribution percentile of each sales value within the dataset
@@ -419,18 +454,18 @@ WINDOW w AS (ORDER BY sales);
 ### ROWS vs RANGE
-| Frame Type | Description                        | Example                                         |
-| ---------- | ---------------------------------- | ----------------------------------------------- |
-| ROWS       | Based on physical row count        | `ROWS BETWEEN 2 PRECEDING AND CURRENT ROW`      |
-| RANGE      | Based on logical value range       | `RANGE BETWEEN 10 PRECEDING AND 10 FOLLOWING`   |
+| Frame Type | Description | Example |
+| ---------- | ----------- | ------- |
+| ROWS | Based on physical row count | `ROWS BETWEEN 2 PRECEDING AND CURRENT ROW` |
+| RANGE | Based on logical value range | `RANGE BETWEEN 10 PRECEDING AND 10 FOLLOWING` |
 ### Boundary Keywords
 * `UNBOUNDED PRECEDING`: The first row of the partition
 * `UNBOUNDED FOLLOWING`: The last row of the partition
 * `CURRENT ROW`: The current row
-* `n PRECEDING`: The nth row before the current row (for ROWS) or rows with value - n (for RANGE)
-* `n FOLLOWING`: The nth row after the current row (for ROWS) or rows with value + n (for RANGE)
+* `n PRECEDING`: The nth row before the current row (ROWS) or rows with value − n (RANGE)
+* `n FOLLOWING`: The nth row after the current row (ROWS) or rows with value + n (RANGE)
 ***
@@ -453,9 +488,11 @@ WINDOW w AS (ORDER BY sales);
 * `LAG()`: Access preceding rows
 * `LEAD()`: Access following rows
-* `FIRST_VALUE()`: First value in the window
-* `LAST_VALUE()`: Last value in the window
-* `NTH_VALUE()`: The nth value in the window
+* `FIRST_VALUE()`: First value in the window (supports `IGNORE NULLS`)
+* `LAST_VALUE()`: Last value in the window (supports `IGNORE NULLS`)
+* `NTH_VALUE()`: The nth value in the window (supports `IGNORE NULLS`)
+> `IGNORE NULLS` skips NULLs when accessing values; the default is `RESPECT NULLS`. Only `FIRST_VALUE`/`LAST_VALUE`/`NTH_VALUE` support this; `LAG`/`LEAD` do not.
 ***
@@ -487,29 +524,28 @@ WINDOW w AS (ORDER BY month ROWS BETWEEN 2 PRECEDING AND CURRENT ROW);
 For grouped analysis, use PARTITION BY to perform intra-group calculations without breaking the data structure:
 ```sql
--- Example: Calculate ranking separately by category
-SELECT category, month, sales,
-       RANK() OVER w AS rank_in_category
-FROM sales_by_category
-WINDOW w AS (PARTITION BY category ORDER BY sales DESC);
+-- Example: Calculate salary ranking by department
+SELECT dept, name, salary,
+       RANK() OVER w AS rank_in_dept
+FROM doc_test.employees
+WINDOW w AS (PARTITION BY dept ORDER BY salary DESC);
 ```
 **Execution Result**:
 ```
-+-------------+-------+-------+------------------+
-| category    | month | sales | rank_in_category |
-+-------------+-------+-------+------------------+
-| Clothing    | 2     | 600   | 1                |
-| Clothing    | 3     | 550   | 2                |
-| Clothing    | 1     | 500   | 3                |
-| Electronics | 2     | 1200  | 1                |
-| Electronics | 1     | 1000  | 2                |
-| Electronics | 3     | 900   | 3                |
-+-------------+-------+-------+------------------+
++-------------+-------+----------+--------------+
+| dept        | name  | salary   | rank_in_dept |
++-------------+-------+----------+--------------+
+| Engineering | Alice | 12000.00 | 1            |
+| Engineering | Bob   |  9500.00 | 2            |
+| HR          | Eve   |  6000.00 | 1            |
+| Marketing   | Carol |  8500.00 | 1            |
+| Marketing   | Dave  |  6500.00 | 2            |
++-------------+-------+----------+--------------+
 ```
-Explanation: Rankings are computed independently within each category without affecting each other.
+Explanation: Salary rankings are computed independently within each department without affecting each other.
 ### 3. Pay Attention to LAST\_VALUE Window Scope
@@ -559,3 +595,9 @@ A: You need to explicitly specify `ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDE
 ***
 ^
+## Related Guides
+- [Ranking and Percentile Analysis](SQL_Ranking_Guide.md): Complete usage scenarios for ROW_NUMBER, RANK, DENSE_RANK, NTILE, and PERCENTILE
+- [Cumulative Calculation and Running Total](SQL_Running_Total_Guide.md): Usage patterns for SUM/AVG OVER, moving averages, YTD cumulative values, FIRST_VALUE/LAST_VALUE
+- [Time Series Analysis](SQL_TimeSeries_Guide.md): Implementing rolling windows and period-over-period comparisons using window functions

package/bin/skills/lakehouse-doc-en/references/Zettapark_Data_Engineering_Demo.md CHANGED Viewed

@@ -83,7 +83,7 @@ session.use_schema(Schema_Name)
 # XSMALL VCLUSTER Creation Ready
-Sample config.json file ([Parameter Description](https://doc.clickzetta.com/JDBC-Driver)):
+Sample config.json file ([Parameter Description](jdbc-driver.md)):
 ```json
 {

package/bin/skills/lakehouse-doc-en/references/access-control-configuration.md CHANGED Viewed

@@ -16,11 +16,9 @@ Service instance-level roles can only be granted via the Web UI. Only users with
 In the service instance, navigate to **Admin** -> **Security**, and switch to the **Roles** tab.
-:-: ![](.topwrite/assets/image_1734853864093.png =791)
 Click on the instance role you want to grant to enter its detail page, then click **Grant to User**:
-:-: ![](.topwrite/assets/image_1734853972562.png =793)
 In the dialog, select the users to grant, then click the **Grant** button to complete the instance role assignment.
@@ -44,13 +42,11 @@ For a user to use compute clusters (VClusters) and execute SQL within a workspac
 After entering the service instance, click **Admin** -> **Workspaces** in the menu to go to the workspace list. Click on a workspace name to enter its detail page.
-:-: ![](.topwrite/assets/image_1734854163713.png =795)
 On the workspace detail page, click the **+ Add User** button, and select users in the dialog. Only users who exist in the service instance and are not currently members of this workspace will be displayed. Select one or more users and click **Add User** or **Add User and Grant Role** to add the selected users to the workspace. After successful addition, you can find the new users in the workspace's **Users** list.
 In the workspace's **Users** list, click the **...** menu next to a user and select **Remove User** to remove that user from the workspace. The removed user will immediately lose all granted workspace roles and lose the ability to use compute clusters (VClusters) or execute SQL in that workspace.
-:-: ![](.topwrite/assets/image_1734876545148.png =788)
 Note that users removed from a workspace will retain any data permissions directly granted to them, meaning they can exercise those data permissions in other workspaces to query or modify data. Therefore, it is recommended to manage permissions through role grants to reduce the complexity of permission management in such scenarios.
@@ -116,7 +112,6 @@ To grant permissions to a user, replace `TO ROLE <CUSTOM_ROLE_NAME>` with `TO US
 Submitting scheduled tasks in a workspace can only be done through the **Development** feature in the Web UI. The `workspace_admin` and `workspace_dev` roles have the permission to submit job scripts as scheduled tasks.
-:-: ![](.topwrite/assets/image_1734876961826.png =802)
 ^
@@ -146,20 +141,18 @@ You can grant or revoke roles from users via the Web UI or SQL. Only users with
 On the **Security** -> **Roles** page, you can view instance-level and workspace-level roles in the current instance.
-:-: ![](.topwrite/assets/image_1734878372389.png =784)
 The `instance_admin` role can view all instance-level roles and all workspace-level roles, and manage grants for all instance-level roles.
 The `workspace_admin` role can view all roles within their workspace and manage grants for those roles. If a user holds the `workspace_admin` role in multiple workspaces, they can manage role grants across all those workspaces.
 To grant a role, click the role name to enter its detail page, where you can view all users currently granted the role. Click **+ Grant to User**, select users in the dialog, and click **Grant** to assign the role to users.
-:-: ![](.topwrite/assets/image_1734878510613.png =798)
 To revoke a role, click the **...** menu next to a user and select **Remove User** to remove the user's association with that role.
 In the **Admin** -> **Workspaces** list, enter a workspace detail page, and on the **Roles** tab you can also view the role list within the workspace and grant or revoke roles using the same process.
-:-: ![](.topwrite/assets/image_1734878871234.png =795)
 ***