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

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

@@ -1,5 +1,4 @@
 # Develop Dynamic Tables for Near Real-Time Incremental Processing
-**【Preview Release】This feature is currently in an invited preview stage. To try it out, please contact Singdata Technology through the official website.**
 
 ## Tutorial Overview
 

package/bin/skills/lakehouse-doc-en/references/studio-incremental-sync-practice.md

@@ -24,24 +24,27 @@ doc_github_clean (standardized fields, ready for direct query and analysis)
 
 ---
 
-## Step 1: Shell Task — Pull Raw Data
+## Shell Task: Pull Raw Data
 
 ### Script
 
+The Shell layer sets task parameters and calls embedded Python:
+
 ```bash
 #!/bin/bash
-# Task parameter: biz_date = $[yyyy-MM-dd]
 BIZ_DATE='${biz_date}'
 echo "Fetch date: $BIZ_DATE"
+```
 
-python3 - << PYEOF
+The embedded Python code handles table creation, API fetching, and writing to the raw layer (executed via `python3 - << PYEOF ... PYEOF` heredoc):
+
+```python
 import urllib.request, json
 from clickzetta_dbutils import get_active_lakehouse_engine
 from sqlalchemy import text
 
 biz_date = '$BIZ_DATE'
 
-# ── 1. Create table (idempotent) ──────────────────────────────────────────
 engine = get_active_lakehouse_engine(schema="doc_connector_demo")
 with engine.connect() as conn:
     conn.execute(text("CREATE SCHEMA IF NOT EXISTS doc_connector_demo"))
@@ -57,14 +60,12 @@ with engine.connect() as conn:
         )
     """))
 
-# ── 2. Fetch GitHub Releases API ──────────────────────────────────────────
 url = "https://api.github.com/repos/clickzetta/dbt-clickzetta/releases?per_page=10"
 req = urllib.request.Request(url, headers={"User-Agent": "Mozilla/5.0"})
 with urllib.request.urlopen(req, timeout=15) as r:
     releases = json.loads(r.read())
 print(f"API returned {len(releases)} records")
 
-# ── 3. Idempotent write to raw layer ──────────────────────────────────────
 with engine.connect() as conn:
     conn.execute(text(f"DELETE FROM doc_connector_demo.doc_github_raw WHERE load_date = '{biz_date}'"))
     for rel in releases:
@@ -79,7 +80,6 @@ with engine.connect() as conn:
         ))
 print(f"Wrote {len(releases)} raw records, load_date={biz_date}")
 
-# ── 4. Verify ─────────────────────────────────────────────────────────────
 with engine.connect() as conn:
     result = conn.execute(text(
         f"SELECT tag_name, published_at FROM doc_connector_demo.doc_github_raw "
@@ -87,7 +87,6 @@ with engine.connect() as conn:
     ))
     for row in result:
         print(f"  {row[0]:15s} {row[1]}")
-PYEOF
 ```
 
 ### Creating and Executing the Task
@@ -106,7 +105,7 @@ PYEOF
 cz-cli task create github_raw_fetch --type shell --profile <your-profile>
 cz-cli task save-content github_raw_fetch --file github_raw_fetch.sh \
   --params '{"biz_date": "$[yyyy-MM-dd]"}' --profile <your-profile>
-cz-cli task save-config github_raw_fetch --vcluster default --retry-count 1 --profile <your-profile>
+cz-cli task save-config github_raw_fetch --vcluster DEFAULT --retry-count 1 --profile <your-profile>
 cz-cli task save-cron github_raw_fetch --cron "0 1 * * *" --profile <your-profile>
 cz-cli task online github_raw_fetch -y --profile <your-profile>
 cz-cli task execute github_raw_fetch --param "biz_date=2024-12-01" --profile <your-profile>
@@ -125,10 +124,12 @@ Wrote 10 raw records, load_date=2024-12-01
 
 ---
 
-## Step 2: Python Task — Clean and Standardize
+## Python Task: Clean and Standardize
 
 ### Script
 
+Task parameters and Session creation:
+
 ```python
 from clickzetta_dbutils import get_active_lakehouse_engine
 from clickzetta.zettapark.session import Session
@@ -136,12 +137,9 @@ from clickzetta.zettapark import functions as F
 from urllib.parse import urlparse, parse_qs
 import re
 
-# ── Task parameters ───────────────────────────────────────────────────────
-# biz_date = $[yyyy-MM-dd]
 biz_date = '${biz_date}'
 print(f"Cleaning date: {biz_date}")
 
-# ── 1. Create ZettaPark Session ───────────────────────────────────────────
 engine = get_active_lakehouse_engine(schema="doc_connector_demo")
 url_str = str(engine.url)
 parsed = urlparse(url_str.replace('clickzetta://', 'https://'))
@@ -154,25 +152,25 @@ session = Session.builder.configs({
     "magic_token": params['magic_token'][0],
     "workspace":   parsed.path.lstrip('/'),
     "schema":      params.get('schema', ['public'])[0],
-    "vcluster":    params.get('virtualcluster', ['default'])[0],
+    "vcluster":    params.get('virtualcluster', ['DEFAULT'])[0],
 }).getOrCreate()
 
 print(f"Session ready: {session.get_current_catalog()}.{session.get_current_schema()}")
+```
 
-# ── 2. Read from raw layer ────────────────────────────────────────────────
+Read from the raw layer and convert to pandas for cleaning:
+
+```python
 raw = session.table("doc_connector_demo.doc_github_raw").filter(
     F.col("load_date") == biz_date
 )
 print(f"Raw layer record count: {raw.count()}")
 
-# ── 3. Convert to pandas for cleaning ────────────────────────────────────
 df = raw.to_pandas()
 
-# Deduplication: keep only one record per tag_name
 df = df.drop_duplicates(subset=['tag_name'], keep='first')
 print(f"After deduplication: {len(df)} records")
 
-# Parse version number: v1.7.5 → major=1, minor=7, patch=5
 def parse_version(tag):
     m = re.match(r'v?(\d+)\.(\d+)\.(\d+)', tag)
     if m:
@@ -183,14 +181,16 @@ df[['major', 'minor', 'patch']] = df['tag_name'].apply(
     lambda t: parse_version(t)
 ).apply(lambda x: x if x else (None, None, None)).tolist()
 
-# Filter out invalid versions (tags that don't match the vX.Y.Z format)
 df = df.dropna(subset=['major'])
 df['major'] = df['major'].astype(int)
 df['minor'] = df['minor'].astype(int)
 df['patch'] = df['patch'].astype(int)
 print(f"Valid versions: {len(df)} records")
+```
+
+Create table, write back to clean layer, and print summary:
 
-# ── 4. Create table and write back to clean layer ─────────────────────────
+```python
 session.sql("""
     CREATE TABLE IF NOT EXISTS doc_connector_demo.doc_github_clean (
         load_date    STRING,
@@ -212,7 +212,6 @@ result_df = session.create_dataframe(
 result_df.write.mode("append").save_as_table("doc_connector_demo.doc_github_clean")
 print(f"Wrote to clean layer: {len(df)} records, load_date={biz_date}")
 
-# ── 5. Summary output ─────────────────────────────────────────────────────
 summary = (
     session.table("doc_connector_demo.doc_github_clean")
     .filter(F.col("load_date") == biz_date)
@@ -238,14 +237,19 @@ session.close()
 
 **cz-cli**
 
+First get the task_id of `github_raw_fetch` (needed for configuring the dependency):
+
 ```bash
-# First get the task_id of github_raw_fetch (needed for configuring the dependency)
 cz-cli task list --profile <your-profile>
+```
+
+Then create the task and configure the dependency:
 
+```bash
 cz-cli task create github_clean --type python --profile <your-profile>
 cz-cli task save-content github_clean --file github_clean.py \
   --params '{"biz_date": "$[yyyy-MM-dd]"}' --profile <your-profile>
-cz-cli task save-config github_clean --vcluster default --retry-count 1 \
+cz-cli task save-config github_clean --vcluster DEFAULT --retry-count 1 \
   --deps replace \
   --dep-tasks '[{"taskId": <github_raw_fetch_task_id>, "taskName": "github_raw_fetch"}]' \
   --profile <your-profile>

package/bin/skills/lakehouse-doc-en/references/studio-shell-task.md

@@ -138,7 +138,7 @@ cz-cli task save-content shell_etl --file shell_etl.sh \
   --profile <your-profile>
 
 # Configure scheduling
-cz-cli task save-config shell_etl --vcluster default --retry-count 1 --profile <your-profile>
+cz-cli task save-config shell_etl --vcluster DEFAULT --retry-count 1 --profile <your-profile>
 cz-cli task save-cron shell_etl --cron "0 1 * * *" --profile <your-profile>
 
 # Publish and run a one-time execution to verify

package/bin/skills/lakehouse-doc-en/references/supported-cloud-platforms.md

@@ -0,0 +1,32 @@
+# Supported Cloud Platforms and Regions
+
+## Region Support
+
+Singdata Lakehouse, as a SaaS-based data management and analysis service, fully leverages cloud infrastructure to provide users with efficient and convenient service experiences. We are committed to meeting the data connectivity and integration needs of customers and business systems across different cloud service providers and regions.
+
+Currently, Singdata Lakehouse provides services in the following cloud service providers and regions, with plans to expand further:
+
+| Cloud Provider | Region                   | Region Code             |
+| -------------- | ------------------------ | ----------------------- |
+| Alibaba Cloud  | Singapore (Singapore)    | ap-southeast-1-alicloud |
+| AWS            | Asia Pacific (Singapore) | ap-southeast-1-aws      |
+
+## Service Domains
+
+When you register a Singdata Lakehouse account, the system automatically assigns a unique account name. When managing your account, you need to use this account name to log in to the Account Center. In the Account Center, administrators can create and open Lakehouse service instances for you in specified cloud service providers and regions. Please note that Lakehouse service instance names are globally unique.
+
+| Service             | Sub-service                | Domain                                                               |
+| ------------------- | -------------------------- | -------------------------------------------------------------------- |
+| Account Console     | Account Management Center  | \<account\_name>.\<region\_id>.accounts.singdata.com                 |
+| Product Web Console | Lakehouse Instance Console | \<instance\_name>.\<region\_id>.app.singdata.com                     |
+|                     | Lakehouse Workspace List   | \<instance\_name>.app.lakehouse.singdata..com/workspace              |
+| Lakehouse JDBC URL  |                            | jdbc\:clickzetta://\<instance\_name>.\<region\_id>.api.singdata.com/ |
+
+JDBC Domain & Service Endpoint Detailed List
+
+| Cloud Provider | Region                   | region\_id           | JDBC Domain                                                                                                                                                               | Endpoint                                 |
+| -------------- | ------------------------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
+| Alibaba Cloud  | Singapore (Singapore)    | cn-shanghai-alicloud | jdbc\:clickzetta://\<instance\_name>.ap-southeast-1-alicloud.api.singdata.com/\<workspace\_name>?username=\<user\_name>\&password=\&schema=public\&virtualCluster=DEFAULT | ap-southeast-1-alicloud.app.singdata.com |
+| AWS            | Asia Pacific (Singapore) | cn-north-1-aws       | jdbc\:clickzetta://\<instance\_name>.ap-southeast-1-aws.api.singdata.com/\<workspace\_name>?username=\<user\_name>\&password=\&schema=public\&virtualCluster=DEFAULT      | cn-north-1-aws.api.clickzetta.com        |
+
+Note: For creating and obtaining the account name \<account\_name> and instance name \<instance\_name>, please refer to [Getting Started](logging-in.md).

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

@@ -2,33 +2,39 @@
 
 ## Feature Overview
 
-The Table Rendering feature allows users to describe table styles using natural language. DataGPT will automatically generate data tables containing complex layouts such as grouping, aggregation, color marking, fixed headers, and dual-layer headers. No manual formatting is needed -- just describe the table style you want as if chatting.
+The Table Rendering feature allows users to describe table styles using natural language. The Data Analytics Agent (DataGPT) will automatically generate data tables with complex layouts such as grouping, aggregation, color marking, fixed headers, and dual-layer headers. No manual formatting is needed — just describe the table style you want as if chatting.
 
 ## Usage
 
-In the AI dialog, describe the table content and style you need, and the Agent will automatically generate the corresponding table.
+In the AI dialog box, describe the table content and style you need, and the Agent will automatically generate the corresponding table.
 
 ### Example
 
 "Help me analyze the sales performance of different brands. Group by brand, differentiate between B-end and C-end, include full-year summary data and monthly information, and add commentary. Numeric columns should support sorting, with sorting limited to within each brand only."
 
-![](.topwrite/assets/image_1776086131763.png)
+:-: ![](/.topwrite/assets/image_1780907304860.png =699)
 
 **Output Report**:
-![](.topwrite/assets/image_1776085505385.png)
+![](/.topwrite/assets/image_1780907330577.png)
 
 You can optimize table details by continuing the conversation, for example:
 
-1. Also need to count the sales performance of each brand, TOB total, and TOC total.
-2. In the "Notes" section, highlight meeting expectations in green and falling short in red.
-   ![](.topwrite/assets/image_1776085615132.png)
-   Sorting:
-   ![](.topwrite/assets/image_1776085953072.png)
+1. Use a compact table style with minimum row height, reduced padding, no text wrapping, and a tight layout similar to Excel.
+
+![](/.topwrite/assets/image_1780907466748.png)
 
  **Notes**
 
-1. The table style is automatically generated by the Agent based on natural language descriptions. The more specific the description, the better the generated result matches expectations.
+1\. The table style is automatically generated by the Agent based on natural language descriptions. The more specific the description, the better the generated result matches expectations.
+
+2\. For complex layout requirements, it is recommended to fully describe all style requirements (grouping method, aggregation dimensions, color rules, etc.) in a single query.
+
+3\. To adjust a generated table style, you can modify it by appending a follow-up description (e.g., "Change the background color to blue").
+
+## Related Documentation
 
-2. For complex layout requirements, it is recommended to fully describe all style requirements (grouping method, aggregation dimensions, color rules, etc.) in a single query.
+* [Chart Auto-Refresh Configuration](chart-auto-refresh-guide.md) — Set up auto-refresh for generated charts
+* [Dashboard Version Management](dashboard-version-management-guide.md) — Manage dashboard versions across multiple revisions
+* [Conversational Data Analytics (Analytics Agent)](datagpt_introduction.md) — Return to the feature overview
 
-3. To adjust a generated table style, you can modify it by adding follow-up descriptions (e.g., "Change the background color to blue").
+^

package/bin/skills/lakehouse-doc-en/references/task-develop.md

@@ -8,15 +8,15 @@ Click "Development" in the left navigation menu to enter the main interface.
 
 ## Interface Overview
 
-![](.topwrite/assets/image_1735640592511.png)
+![](/.topwrite/assets/image_1780886907584.png =793)
 
-| No. | Function                                                        |
-| -- | --------------------------------------------------------- |
-| 1  | Function switch                                                      |
-| 2  | Switch workspace: This section displays the name of the current data development project space and the region you are in. You can click the dropdown icon to switch to other project spaces. |
-| 3  | Development directory tree: The directory tree is used to manage task code in an orderly manner. You can create directory trees according to business needs to manage tasks by category and hierarchy.        |
-| 4  | SQL editing area: The main operation interface for development. Different types of editing areas have different operation interfaces.                         |
-| 5  | Run results: Presents the results after running operations in the SQL editing area.                            |
+| No. | Function                                                                                                                                                                                               |
+| --- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 1   | Function switch                                                                                                                                                                                        |
+| 2   | Switch workspace: This section displays the name of the current data development project space and the region you are in. You can click the dropdown icon to switch to other project spaces.           |
+| 3   | Development directory tree: The directory tree is used to manage task code in an orderly manner. You can create directory trees according to business needs to manage tasks by category and hierarchy. |
+| 4   | SQL editing area: The main operation interface for development. Different types of editing areas have different operation interfaces.                                                                  |
+| 5   | Run results: Presents the results after running operations in the SQL editing area.                                                                                                                    |
 
 ## Directory Tree
 
@@ -61,20 +61,20 @@ Supported operations on the directory tree:
 
 ![](.topwrite/assets/43961fb877/97e53c195a68bc32dc20f8d05406a65814f50ebf.png =283)
 
-| Status Legend                                                                              | Description                       |
-| --------------------------------------------------------------------------------- | ------------------------ |
-| ![](.topwrite/assets/43961fb877/cf868103bc526077f03e907734acc40282147b16.png =54) | After task submission, the saved version differs from the submitted version.   |
+| Status Legend                                                                     | Description                                                                         |
+| --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
+| ![](.topwrite/assets/43961fb877/cf868103bc526077f03e907734acc40282147b16.png =54) | After task submission, the saved version differs from the submitted version.        |
 | ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =52) | After task submission, the server-side saved version matches the submitted version. |
-| ![](.topwrite/assets/43961fb877/3c8f88221d1cb5096a50fe2f871717264c355624.png =50) | After task submission, click the offline operation.            |
-| ![](.topwrite/assets/43961fb877/4ffcc5e1d5ceda6d460b753cce8e713d4cd1eb58.png =45) | Other status types.                  |
+| ![](.topwrite/assets/43961fb877/3c8f88221d1cb5096a50fe2f871717264c355624.png =50) | After task submission, click the offline operation.                                 |
+| ![](.topwrite/assets/43961fb877/4ffcc5e1d5ceda6d460b753cce8e713d4cd1eb58.png =45) | Other status types.                                                                 |
 
-| Icon Legend                                                                              | Description       |
-| --------------------------------------------------------------------------------- | -------- |
-| ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =45) | Real-time sync     |
-| ![](.topwrite/assets/43961fb877/c7a4258cc7c3fffb428b3393d189d5b56d1352b8.png =40) | Offline sync     |
-| ![](.topwrite/assets/43961fb877/b0a4f31a60e860ec4168f2a6aa6c75bd349882ff.png =46) | SQL script    |
-| ![](.topwrite/assets/43961fb877/a34b52a1a518262075162653a0e7bd5efdf8373d.png =43) | Shell script  |
-| ![](.topwrite/assets/43961fb877/9a58c3506c9ddc8c176f67d1224b55de6a08ebb0.png =40) | Python script |
+| Icon Legend                                                                       | Description    |
+| --------------------------------------------------------------------------------- | -------------- |
+| ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =45) | Real-time sync |
+| ![](.topwrite/assets/43961fb877/c7a4258cc7c3fffb428b3393d189d5b56d1352b8.png =40) | Offline sync   |
+| ![](.topwrite/assets/43961fb877/b0a4f31a60e860ec4168f2a6aa6c75bd349882ff.png =46) | SQL script     |
+| ![](.topwrite/assets/43961fb877/a34b52a1a518262075162653a0e7bd5efdf8373d.png =43) | Shell script   |
+| ![](.topwrite/assets/43961fb877/9a58c3506c9ddc8c176f67d1224b55de6a08ebb0.png =40) | Python script  |
 
 ## Task Development Process
 
@@ -86,7 +86,7 @@ Currently, two types of task nodes are supported: data integration and data deve
 
 Click "New" and select the specific development type. A popup will appear. Enter the task name, select the specific directory level where the task should be saved, and then enter the development interface.
 
-![](.topwrite/assets/image_1690523560494.png =210)
+^
 
 ### Operation Bar Description
 
@@ -102,45 +102,43 @@ After clicking the task directory tree on the left or creating a new task node,
 
 Tab color status mapping:
 
-| Status Icon | Description   |
-| ---- | ---- |
-| Green   | Run successful |
-| Red   | Run failed |
-| Blue   | Running |
-| Gray   | No run |
+| Status Icon | Description    |
+| ----------- | -------------- |
+| Green       | Run successful |
+| Red         | Run failed     |
+| Blue        | Running        |
+| Gray        | No run         |
 
 #### SQL Function Area
 
 ![](.topwrite/assets/43961fb877/d87ab875a66382a674db74e3afeeeb3b722100d6.png)
 
-| No. | Function Name   | Description                                                                                                     |
-| -- | ------ | ------------------------------------------------------------------------------------------------------ |
-| 1  | Save     | Save the task, including the current node code and related configurations.                                                                               |
-| 2  | Format    | Format the written code to make the syntax structure look clean and concise.                                                                                 |
-| 3  | Parameters     | Not yet online.                                                                                                  |
-| 4  | Versions     | Click Versions to view the submitted and saved versions of the current task. Supports code viewing and code rollback between versions.                                                             |
-| 5  | Scheduling     | Click to open a sidebar panel for scheduling configuration. See Scheduling Settings for details.                                                                          |
-| 6  | Submit     | The "Submit" function is only needed for tasks that require scheduled dispatch. After "Submit", the task is published to the Operations Center and runs according to the configured schedule. Before submission, scheduling configuration is required. See Scheduling Settings for details.                  |
-| 7  | Operations     | Click to enter the "Operations" center.                                                                                             |
-| 8  | Task flow tips | Hover over the task flow tips to display the online flowchart for the development task.                                                                       |
-| 9  | Cluster filter   | The "default" shown in the figure indicates the Virtual Cluster used for task execution. Click to switch to another Virtual Cluster. To add a new Virtual Cluster, go to "Compute". |
-| 10 | Run/Stop  | Run/Stop the current node's code. When running SQL code, you can select and run a portion of the code.                                                                   |
+| No. | Function Name  | Description                                                                                                                                                                                                                                                                                 |
+| --- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1   | Save           | Save the task, including the current node code and related configurations.                                                                                                                                                                                                                  |
+| 2   | Format         | Format the written code to make the syntax structure look clean and concise.                                                                                                                                                                                                                |
+| 3   | Parameters     | Not yet online.                                                                                                                                                                                                                                                                             |
+| 4   | Versions       | Click Versions to view the submitted and saved versions of the current task. Supports code viewing and code rollback between versions.                                                                                                                                                      |
+| 5   | Scheduling     | Click to open a sidebar panel for scheduling configuration. See Scheduling Settings for details.                                                                                                                                                                                            |
+| 6   | Submit         | The "Submit" function is only needed for tasks that require scheduled dispatch. After "Submit", the task is published to the Operations Center and runs according to the configured schedule. Before submission, scheduling configuration is required. See Scheduling Settings for details. |
+| 7   | Operations     | Click to enter the "Operations" center.                                                                                                                                                                                                                                                     |
+| 8   | Task flow tips | Hover over the task flow tips to display the online flowchart for the development task.                                                                                                                                                                                                     |
+| 9   | Cluster filter | The "default" shown in the figure indicates the Virtual Cluster used for task execution. Click to switch to another Virtual Cluster. To add a new Virtual Cluster, go to "Compute".                                                                                                         |
+| 10  | Run/Stop       | Run/Stop the current node's code. When running SQL code, you can select and run a portion of the code.                                                                                                                                                                                      |
 
 #### SQL Editing Area
 
-![](.topwrite/assets/43961fb877/daf1fe91a75052ac12b25b198449827de8d56ff5.png)
-
 * Schema switching: Click the dropdown to switch schemas in the current workspace. The default is "public".
 * Shortcuts: Various capabilities supported in the Studio development editing area. See Others: Common Shortcut Operations for details.
 * SQL editing area: The SQL editor in Studio provides the following features to improve data development and analysis efficiency.
 
-| Feature       | Description                                        |
-| -------- | ------------------------------------------- |
-| Code folding     | Collapse code blocks to reduce reading distractions.                             |
-| Real-time syntax error prompts | Prompt users of syntax errors found during code writing to help avoid mistakes.             |
-| Syntax highlighting     | Use different colors or fonts to highlight keywords and syntax structures in the editor or IDE to enhance readability. |
-| Intelligent completion     | Automatically complete keywords, function names, variable names, etc., in code based on context and known information to improve coding efficiency and precision.   |
-| Partial code execution   | Run only a portion of the code instead of the entire program for quick testing of small code segments or debugging.             |
+| Feature                        | Description                                                                                                                                                       |
+| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Code folding                   | Collapse code blocks to reduce reading distractions.                                                                                                              |
+| Real-time syntax error prompts | Prompt users of syntax errors found during code writing to help avoid mistakes.                                                                                   |
+| Syntax highlighting            | Use different colors or fonts to highlight keywords and syntax structures in the editor or IDE to enhance readability.                                            |
+| Intelligent completion         | Automatically complete keywords, function names, variable names, etc., in code based on context and known information to improve coding efficiency and precision. |
+| Partial code execution         | Run only a portion of the code instead of the entire program for quick testing of small code segments or debugging.                                               |
 
 ### Scheduling Settings
 
@@ -148,46 +146,44 @@ After the task has been tested and everything works correctly, if you want to ru
 
 #### Basic Information
 
-| Parameter     | Description                                                                                                                                         |
-| ------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Owner    | Required. Only one member allowed, defaults to the task creator. Can be changed to another workspace member as needed.                                                                                                  |
-| Description     | Optional. Provides a detailed description of the task for future reference and management.                                                                                                                  |
-| Run attributes   | Required. Normal scheduling: Runs according to the user's scheduling rules. Dry-run scheduling: When a task's logic does not need to run temporarily but you don't want to disrupt the data pipeline, set it to dry-run; the task will be marked as successful. Paused: After setting the task to "Paused" and publishing to the Operations Center, the task status is "Paused" and no task instances are generated, but backfill operations are still possible. |
-| Cluster     | Required. Defines the scheduling resource group used when the task is published to production.                                                                                                            |
-| Schema | Required. Defines the prefix schema used when the task runs in production.                                                                                                            |
-| Task priority  | Optional. Sets the scheduling priority for Lakehouse SQL tasks, supporting 10 levels (0-9), where higher numbers mean higher priority.                                                                                          |
-| Parameter configuration   | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: more system built-in parameters will be supported in future versions.                                |
+| Parameter               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Owner                   | Required. Only one member allowed, defaults to the task creator. Can be changed to another workspace member as needed.                                                                                                                                                                                                                                                                                                                                           |
+| Description             | Optional. Provides a detailed description of the task for future reference and management.                                                                                                                                                                                                                                                                                                                                                                       |
+| Run attributes          | Required. Normal scheduling: Runs according to the user's scheduling rules. Dry-run scheduling: When a task's logic does not need to run temporarily but you don't want to disrupt the data pipeline, set it to dry-run; the task will be marked as successful. Paused: After setting the task to "Paused" and publishing to the Operations Center, the task status is "Paused" and no task instances are generated, but backfill operations are still possible. |
+| Cluster                 | Required. Defines the scheduling resource group used when the task is published to production.                                                                                                                                                                                                                                                                                                                                                                   |
+| Schema                  | Required. Defines the prefix schema used when the task runs in production.                                                                                                                                                                                                                                                                                                                                                                                       |
+| Task priority           | Optional. Sets the scheduling priority for Lakehouse SQL tasks, supporting 10 levels (0-9), where higher numbers mean higher priority.                                                                                                                                                                                                                                                                                                                           |
+| Parameter configuration | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: more system built-in parameters will be supported in future versions.                                                                                                                                                                                        |
 
 #### Scheduling Time
 
-![](.topwrite/assets/image_1756191463019.png =379)
-
-| Parameter       | Description                                                                                |
-| -------- | --------------------------------------------------------------------------------- |
-| Scheduling cycle     | Daily: Runs every day. Monthly specified day: User selects specific days each month. Weekly specified day: User selects specific days each week.           |
-| Scheduling frequency     | Execute once: Only the start scheduling time needs to be configured. Execute multiple times: Also requires scheduling interval, start time, end time, and exclusion time settings. |
-| Scheduling interval | When executing multiple times, users can customize the interval between each execution, from 1 minute to 12 hours.                                     |
-| Start scheduling time   | The time when daily instances begin executing.                                                                       |
-| End scheduling time   | The time when daily instances stop executing.                                                                       |
-| Exclusion time settings   | No instances will be generated during the specified exclusion time ranges.                                              |
-| Effective time     | The date from which the task takes effect.                                                                        |
-| Expiry time     | The date from which the task expires.                                                                        |
-| Preview scheduling time   | Click to preview the actual run times after configuration.                                                         |
+| Parameter               | Description                                                                                                                                                                        |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Scheduling cycle        | Daily: Runs every day. Monthly specified day: User selects specific days each month. Weekly specified day: User selects specific days each week.                                   |
+| Scheduling frequency    | Execute once: Only the start scheduling time needs to be configured. Execute multiple times: Also requires scheduling interval, start time, end time, and exclusion time settings. |
+| Scheduling interval     | When executing multiple times, users can customize the interval between each execution, from 1 minute to 12 hours.                                                                 |
+| Start scheduling time   | The time when daily instances begin executing.                                                                                                                                     |
+| End scheduling time     | The time when daily instances stop executing.                                                                                                                                      |
+| Exclusion time settings | No instances will be generated during the specified exclusion time ranges.                                                                                                         |
+| Effective time          | The date from which the task takes effect.                                                                                                                                         |
+| Expiry time             | The date from which the task expires.                                                                                                                                              |
+| Preview scheduling time | Click to preview the actual run times after configuration.                                                                                                                         |
 
 #### Instance Information
 
 Studio supports two instance generation modes: **Effective next day** and **Effective after publishing**.
 
-| Parameter         | Description                                                                                                          |
-| ---------- | ----------------------------------------------------------------------------------------------------------- |
-| Instance generation mode     | Effective after publishing: Instances are generated immediately after publishing and run according to the configured schedule. Effective next day: Instances run on the following day.                                               |
-| Instance retry on error     | Defines whether a task instance can be retried, considering data idempotency. Set as needed. Can retry after success or failure. Cannot retry after success, can retry after failure. Cannot retry after success or failure.                        |
-| Auto retry count     | Custom number of retries.                                                                                                     |
-| Instance timeout duration     | Not enabled / Custom. If a task instance runs longer than the set duration, it will be marked as failed. Changes only apply to new instances after the task is submitted.                                           |
-| Preview scheduling time     | Click to preview the actual run times after configuration.                                                                                   |
-| Parameter configuration       | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: More system built-in parameters will be supported in future versions. |
-| Scheduling wait duration     | If a task instance reaches its scheduled time and waits longer than this setting (still waiting for upstream tasks to finish), the system will mark it as failed to prevent scheduling backlogs.              |
-| Delayed run skip duration | Based on the difference between the task instance's actual start time and the configured scheduled time. If the difference exceeds this setting, the instance is skipped as a dry run and marked as successful.                                        |
+| Parameter                 | Description                                                                                                                                                                                                                                                               |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Instance generation mode  | Effective after publishing: Instances are generated immediately after publishing and run according to the configured schedule. Effective next day: Instances run on the following day.                                                                                    |
+| Instance retry on error   | Defines whether a task instance can be retried, considering data idempotency. Set as needed. Can retry after success or failure. Cannot retry after success, can retry after failure. Cannot retry after success or failure.                                              |
+| Auto retry count          | Custom number of retries.                                                                                                                                                                                                                                                 |
+| Instance timeout duration | Not enabled / Custom. If a task instance runs longer than the set duration, it will be marked as failed. Changes only apply to new instances after the task is submitted.                                                                                                 |
+| Preview scheduling time   | Click to preview the actual run times after configuration.                                                                                                                                                                                                                |
+| Parameter configuration   | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: More system built-in parameters will be supported in future versions. |
+| Scheduling wait duration  | If a task instance reaches its scheduled time and waits longer than this setting (still waiting for upstream tasks to finish), the system will mark it as failed to prevent scheduling backlogs.                                                                          |
+| Delayed run skip duration | Based on the difference between the task instance's actual start time and the configured scheduled time. If the difference exceeds this setting, the instance is skipped as a dry run and marked as successful.                                                           |
 
 #### Scheduling Dependencies
 
@@ -195,7 +191,7 @@ Complex production tasks typically have upstream and downstream dependencies. Fo
 
 Dependency strategy: Currently supports default strategy, forward dependency, and forward nearest dependency. For specific instance generation methods for each strategy, see [Task Scheduling Dependencies](task_scheduling_dependency.md).
 
-![](.topwrite/assets/image_1756191826292.png =660)
+:-: ![](/.topwrite/assets/image_1780886973179.png)
 
 #### Task Output
 
@@ -205,7 +201,7 @@ Method 1: Automatically generate output table names through code auto-parsing me
 
 Method 2: Manually add by searching table names.
 
-![](.topwrite/assets/image_1690523641208.png =437)
+^
 
 For more information about task scheduling, refer to: [Task Scheduling Dependencies](task_scheduling_dependency.md), [Task Scheduling and Instance Execution](f6fc6447ee.md).
 
@@ -223,7 +219,7 @@ Click to jump to the "Operations" center to view task operations.
 
 Run history provides up to 20 recent run result records for the current task tab within 7 days.
 
-![](.topwrite/assets/43961fb877/5356056744906f50b383683a6665b649efc6178d.png)
+^
 
 ### Run Results
 
@@ -236,13 +232,13 @@ Use the expand and collapse buttons to adjust the log display area.
 
 Use the refresh button to force refresh the logs.
 
-![](.topwrite/assets/43961fb877/e3e8ee2c80e29d7dc8bcc52df9c14e68564c9cc3.png)
+^
 
 #### Data
 
 After the task completes, results (such as from SELECT statements) are displayed in the "Data" tab:
 
-![](.topwrite/assets/43961fb877/2b76b47e9714fd6d8ae4276a935f173a971296e1.png)
+^
 
 ## Others: Common Shortcut Operations
 
@@ -269,9 +265,11 @@ The following shortcuts are supported in the code editor to improve editing effi
 
 ## Related Documents
 
-- [Task Parameters](task_param.md) — Use dynamic parameters (dates, timestamps, etc.) in SQL tasks
-- [Task Parameter Syntax Reference](task_param_reference.md) — Complete syntax for system built-in parameters, time expressions, and time functions
-- [Task Parameter Scenario Examples](task_param_examples.md) — Complete business scenarios such as daily, monthly, and weekly reports
-- [Workflow (Composite Task)](composite_task.md) — Orchestrate multiple SQL tasks into a DAG
-- [Task Groups](task_group.md) — Share parameters across tasks and manage them uniformly
-- [Python Tasks](python-task.md) — Use parameters in Python scripts
+* [Task Parameters](task_param.md) — Use dynamic parameters (dates, timestamps, etc.) in SQL tasks
+* [Task Parameter Syntax Reference](task_param_reference.md) — Complete syntax for system built-in parameters, time expressions, and time functions
+* [Task Parameter Scenario Examples](task_param_examples.md) — Complete business scenarios such as daily, monthly, and weekly reports
+* [Workflow (Composite Task)](composite_task.md) — Orchestrate multiple SQL tasks into a DAG
+* [Task Groups](task_group.md) — Share parameters across tasks and manage them uniformly
+* [Python Tasks](python-task.md) — Use parameters in Python scripts
+
+^