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

@clickzetta/cz-cli-darwin-arm64 0.5.16 → 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/vcluster_size_description.md CHANGED Viewed

@@ -8,18 +8,18 @@ The specific adjustments to the specifications are as follows:
 From XS to 5XLarge, each level increase doubles the computing resources and also doubles the resource consumption:
-|         |        |                           |
-| ------- | ------ | ------------------------- |
-| **Specification**  | **Abbreviation** | **Hourly Consumption** (**CRU**\***hour**) |
-| XSMALL  | XS     | 1                         |
-| SMALL   | S      | 2                         |
-| MEDIUM  | M      | 4                         |
-| LARGE   | L      | 8                         |
-| XLARGE  | XL     | 16                        |
-| 2XLARGE | 2XL    | 32                        |
-| 3XLARGE | 3XL    | 64                        |
-| 4XLARGE | 4XL    | 128                       |
-| 5XLARGE | 5XL    | 256                       |
+|                   |                  |                                            |
+| ----------------- | ---------------- | ------------------------------------------ |
+| **Specification** | **Abbreviation** | **Hourly Consumption** (**CRU**\***hour**) |
+| XSMALL            | XS               | 1                                          |
+| SMALL             | S                | 2                                          |
+| MEDIUM            | M                | 4                                          |
+| LARGE             | L                | 8                                          |
+| XLARGE            | XL               | 16                                         |
+| 2XLARGE           | 2XL              | 32                                         |
+| 3XLARGE           | 3XL              | 64                                         |
+| 4XLARGE           | 4XL              | 128                                        |
+| 5XLARGE           | 5XL              | 256                                        |
 ## **New Calculation Cluster Specifications**
@@ -27,11 +27,11 @@ Each type of calculation cluster is represented by CRU (Compute Resource Unit).
 The detailed specifications of various calculation clusters are as follows:
-| **Type**                         | **Minimum Specification** (**CRU**) | **Maximum Specification** (**CRU**) | **Default Value** (**CRU**) | **Step Size**&#xA; (Minimum unit of specification increase/decrease)                                                        |
-| ------------------------------ | ----------------- | ----------------- | ---------------- | ----------------------------------------------------------------------------- |
-| General Purpose&#xA; (GP Vcluster)          | 1                 | 256               | 1                | 1 (Specification examples: 1, 2, 3, 4, 5, 6...256)                                                      |
-| Analytical&#xA; (AP Vcluster)          | 1                 | 256               | 1                | Powers of 2 (Specification examples: 1, 2, 4, 8, 16, 32, 64, 128, 256)                                          |
-| Integration&#xA; (Integration Vcluster) | 0.25              | 256               | 0.5              | 1 (Specification sequence: there are two special small specifications of 0.25 CRU and 0.5 CRU, the step size for other specifications is 1. Specification examples: 0.25, 0.5, 1, 2, 3, 4, 5, 6...256) |
+| **Type**                                | **Minimum Specification** (**CRU**) | **Maximum Specification** (**CRU**) | **Default Value** (**CRU**) | **Step Size**&#xA; (Minimum unit of specification increase/decrease)                                                                                                                                   |
+| --------------------------------------- | ----------------------------------- | ----------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| General Purpose&#xA; (GP Vcluster)      | 1                                   | 256                                 | 1                           | 1 (Specification examples: 1, 2, 3, 4, 5, 6...256)                                                                                                                                                     |
+| Analytical&#xA; (AP Vcluster)           | 1                                   | 256                                 | 1                           | Powers of 2 (Specification examples: 1, 2, 4, 8, 16, 32, 64, 128, 256)                                                                                                                                 |
+| Integration&#xA; (Integration Vcluster) | 0.25                                | 256                                 | 0.5                         | 1 (Specification sequence: there are two special small specifications of 0.25 CRU and 0.5 CRU, the step size for other specifications is 1. Specification examples: 0.25, 0.5, 1, 2, 3, 4, 5, 6...256) |
 The amount of computing resources consumed by each cluster per hour is its CRU specification\*1 hour, i.e., the unit is CRU\*hour. For example, an analytical calculation cluster with a specification of 3 CRU running for 1 hour consumes 3 CRU \* 1 hour = 3 CRU\*hour. The cost is also calculated according to the "CRU\*hour" unit price in the region where the calculation cluster is located.
@@ -41,24 +41,25 @@ The amount of computing resources consumed by each cluster per hour is its CRU s
 The specifications of existing calculation clusters will be automatically converted to the new specifications, and the computing resource consumption and costs per unit time will not change. The specific correspondence of specifications is as follows:
-|         |         |          |
-| ------- | ------- | -------- |
+|                    |               |                      |
+| ------------------ | ------------- | -------------------- |
 | **Original Value** | **New Value** | **Applicable Scope** |
-| XSMALL  | 1       | All types of VC   |
-| SMALL   | 2       | All types of VC   |
-| MEDIUM  | 4       | All types of VC   |
-| LARGE   | 8       | All types of VC   |
-| XLARGE  | 16      | All types of VC   |
-| 2XLARGE | 32      | All types of VC   |
-| 3XLARGE | 64      | All types of VC   |
-| 4XLARGE | 128     | All types of VC   |
-| 5XLARGE | 256     | All types of VC   |
+| XSMALL             | 1             | All types of VC      |
+| SMALL              | 2             | All types of VC      |
+| MEDIUM             | 4             | All types of VC      |
+| LARGE              | 8             | All types of VC      |
+| XLARGE             | 16            | All types of VC      |
+| 2XLARGE            | 32            | All types of VC      |
+| 3XLARGE            | 64            | All types of VC      |
+| 4XLARGE            | 128           | All types of VC      |
+| 5XLARGE            | 256           | All types of VC      |
 ### SQL Create New Compute Cluster
 After the new specification code is launched, the SQL statements for creating and modifying compute clusters will temporarily be compatible with the old specification codes. That is, the Vcluster\_size parameter can support both numerical expressions and code expressions like 'XSMALL, SMALL' for compute cluster specifications. Please migrate to using numerical expressions for compute cluster specifications as soon as possible to avoid affecting the normal creation of compute clusters when switching to an incompatible version.
 Example code for creating a new cluster is as follows:
 ```SQL
 -- Create a compute cluster
 CREATE VCLUSTER [IF NOT EXISTS] vc_name
@@ -69,11 +70,12 @@ objectProperties
 objectProperties ::=
             VCLUSTER_SIZE = NUM --0.25-256. Compatible with XSMALL | SMALL | MEDIUM | LARGE | XLARGE | 2XLARGE | 3XLARGE | 4XLARGE | 5XLARGE
 ```
 ### Create a New Compute Cluster on the Web
 When creating and modifying compute clusters on the web, the specifications of the compute cluster are now expressed in numerical terms. An example is shown below:
-:-: ![](.topwrite/assets/image_1733751304880.png =420)
+^
 ### Query Compute Cluster via SQL
@@ -83,7 +85,7 @@ When querying compute cluster specifications via SQL, all fields representing co
 The specifications of the compute cluster on the web are now expressed in numerical terms.
-:-: ![](.topwrite/assets/image_1733751321636.png)
+^
 ## Billing Instructions
@@ -93,4 +95,4 @@ After the change, estimating the hourly resource consumption and cost of a clust
 There is no need to remember that the "S" specification corresponds to 2 CRU per hour, and then multiply by the unit price to estimate the cost.
-A compute cluster of 2 CRU consumes "2 CRU\*hour" per hour, and you only need to match the unit price to calculate the hourly cost.
+A compute cluster of 2 CRU consumes "2 CRU\*hour" per hour, and you only need to match the unit price to calculate the hourly cost.

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

@@ -14,11 +14,11 @@ A virtual cluster's specification defines the amount of compute resources availa
 > ⚠️ **Note**: Starting from December 2024, the old specification codes for virtual clusters (XS through 5XLarge) have been replaced with numeric specifications. For details, see [Virtual Cluster Specification Code Change Description](vcluster_size_description.md).
-| **Type**                              | **Minimum Spec (CRU)** | **Maximum Spec (CRU)** | **Default (CRU)** | **Step Size** (minimum increment/decrement unit)                                          |
-| ------------------------------------- | ---------------------- | ---------------------- | ----------------- | ----------------------------------------------------------------------------------------- |
-| General Purpose (GP VCluster)         | 1                      | 256                    | 1                 | 1 CRU per step. Examples: 1, 2, 3, 4, 5, 6...256                                         |
-| Analytics (AP VCluster)               | 1                      | 256                    | 1                 | Powers of 2. Examples: 1, 2, 4, 8, 16, 32, 64, 128, 256                                  |
-| Integration (Integration VCluster)    | 0.25                   | 256                    | 0.5               | Supports any decimal specification. Examples: 0.25, 0.5, 0.75, 1, 1.25...256             |
+| **Type**                           | **Minimum Spec (CRU**) | **Maximum Spec (CRU**) | **Default (CRU**) | **Step Size** (minimum increment/decrement unit)                             |
+| ---------------------------------- | ---------------------- | ---------------------- | ----------------- | ---------------------------------------------------------------------------- |
+| General Purpose (GP VCluster)      | 1                      | 256                    | 1                 | 1 CRU per step. Examples: 1, 2, 3, 4, 5, 6...256                             |
+| Analytics (AP VCluster)            | 1                      | 256                    | 1                 | Powers of 2. Examples: 1, 2, 4, 8, 16, 32, 64, 128, 256                      |
+| Integration (Integration VCluster) | 0.25                   | 256                    | 0.5               | Supports any decimal specification. Examples: 0.25, 0.5, 0.75, 1, 1.25...256 |
 > ⚠️ **Note**: Analytics cluster specifications must be a power of 2 (1, 2, 4, 8, 16, 32, 64, 128, 256). Setting any other value will result in an error.
@@ -28,29 +28,28 @@ The compute resources consumed by a cluster per hour equal its CRU specification
 Virtual clusters come in three types: General Purpose, Analytics, and Integration.
-* **General Purpose (GENERAL)**: Suitable for offline jobs. Jobs share compute resources, and new and existing jobs are allocated resources using fair scheduling.
-* **Analytics (ANALYTICS)**: Supports multiple compute instances and auto-scaling. Suitable for online and high-concurrency workloads. When the concurrency limit is reached, subsequent jobs queue up, ensuring first-submitted jobs are executed first.
-* **Integration (INTEGRATION)**: Suitable for offline and real-time integration tasks. Multiple integration tasks can share a single Integration cluster instance. Tasks that exceed the cluster's capacity enter a queue.
+* **General Purpose (GENERAL**): Suitable for offline jobs. Jobs share compute resources, and new and existing jobs are allocated resources using fair scheduling.
+* **Analytics (ANALYTICS**): Supports multiple compute instances and auto-scaling. Suitable for online and high-concurrency workloads. When the concurrency limit is reached, subsequent jobs queue up, ensuring first-submitted jobs are executed first.
+* **Integration (INTEGRATION**): Suitable for offline and real-time integration tasks. Multiple integration tasks can share a single Integration cluster instance. Tasks that exceed the cluster's capacity enter a queue.
 The relationship between cluster types and task types is shown below:
-| **Task Type**           | **Supported Cluster Types**  | **Recommended Cluster Type**                                                  |
-| ----------------------- | ---------------------------- | ----------------------------------------------------------------------------- |
-| Offline Sync            | Integration                  | Integration                                                                   |
-| SQL                     | General Purpose, Analytics   | **ETL tasks**: General Purpose<br>**Ad-hoc queries**: Analytics               |
-| Python                  | No cluster required          | /                                                                             |
-| Shell                   | No cluster required          | /                                                                             |
-| JDBC                    | No cluster required          | /                                                                             |
-| Virtual Node            | No cluster required          | /                                                                             |
-| Databricks SQL          | No cluster required          | /                                                                             |
-| Databricks Notebook     | No cluster required          | /                                                                             |
-| Real-time Sync          | Integration                  | Integration                                                                   |
-| Multi-table Real-time Sync | Integration               | Integration                                                                   |
-| Dynamic Table           | General Purpose, Analytics   | **Low-frequency, large data volume**: General Purpose<br>**High-frequency, small data volume**: Analytics |
-| Streaming SQL           | General Purpose, Analytics   | **Low-frequency, large data volume**: General Purpose<br>**High-frequency, small data volume**: Analytics |
-:-: ![](.topwrite/assets/image_1743421840284.png =782)
+| **Task Type**              | **Supported Cluster Types** | **Recommended Cluster Type**                                                                          |
+| -------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------- |
+| Offline Sync               | Integration                 | Integration                                                                                           |
+| SQL                        | General Purpose, Analytics  | **ETL tasks**: General Purpose**Ad-hoc queries**: Analytics                                           |
+| Python                     | No cluster required         | /                                                                                                     |
+| Shell                      | No cluster required         | /                                                                                                     |
+| JDBC                       | No cluster required         | /                                                                                                     |
+| Virtual Node               | No cluster required         | /                                                                                                     |
+| Databricks SQL             | No cluster required         | /                                                                                                     |
+| Databricks Notebook        | No cluster required         | /                                                                                                     |
+| Real-time Sync             | Integration                 | Integration                                                                                           |
+| Multi-table Real-time Sync | Integration                 | Integration                                                                                           |
+| Dynamic Table              | General Purpose, Analytics  | **Low-frequency, large data volume**: General Purpose**High-frequency, small data volume**: Analytics |
+| Streaming SQL              | General Purpose, Analytics  | **Low-frequency, large data volume**: General Purpose**High-frequency, small data volume**: Analytics |
+^
 ^
 ### Minimum Instances
@@ -81,23 +80,22 @@ Singdata Lakehouse provides two ways to manage virtual clusters: 1) Web UI; 2) S
 Log in to the Lakehouse platform and click "Compute" in the left menu to open the "Virtual Clusters" list page. Here you can view all virtual clusters in the current workspace that you have access to.
-![](.topwrite/assets/image_1741611037239.png)
+^
 Click any cluster name to open the details page, where you can view job execution status, configuration details, and your permissions for that cluster.
-:-: ![](.topwrite/assets/image_1728532541352.png =805)
+^
 #### Creating a Virtual Cluster
 On the "Virtual Clusters" list page, click "New Cluster" to open the creation interface. Fill in the cluster name, select the cluster type, configure the specification, and click "Create Cluster." The new cluster will appear in the list and can be used once its status changes to "Running."
-:-: ![](.topwrite/assets/image_1742214451076.png =813)
+^
 ^
 **Creating a General Purpose Cluster**
-:-: ![](.topwrite/assets/image_1742216967064.png =414)
+^
 If you need to run ETL or other batch workloads, create a General Purpose cluster:
@@ -114,8 +112,7 @@ After completing the configuration, click "OK" to finish creating the General Pu
 **Creating an Analytics Cluster**
-:-: ![](.topwrite/assets/image_1742216902917.png =404)
+^
 ^
 If you need compute resources for ad-hoc queries or BI dashboards, create an Analytics cluster:
@@ -130,7 +127,7 @@ If you need compute resources for ad-hoc queries or BI dashboards, create an Ana
 **Creating an Integration Cluster**
-:-: ![](.topwrite/assets/image_1742217991159.png =411)
+^
 If you need to run offline or real-time integration tasks, create an Integration cluster:
@@ -141,7 +138,7 @@ If you need to run offline or real-time integration tasks, create an Integration
 * Integration clusters provide a "Specification Estimation" feature to help you choose an appropriate size. Enter the "Number of Tasks" and "Average Task Concurrency," and the system calculates an estimated specification using the formula: Specification = Number of Tasks × Average Task Concurrency × 0.05.
-:-: ![](.topwrite/assets/image_1742218209994.png =441)
+^
 * Choose whether to enable "Auto Resume" and "Auto Suspend," and configure a suitable "Auto Suspend" time. We recommend enabling "Auto Resume" to handle jobs promptly, and setting "Auto Suspend" to 1 minute so the cluster shuts down quickly after jobs complete, saving costs.
@@ -151,21 +148,20 @@ If you need to run offline or real-time integration tasks, create an Integration
 In the cluster list, select the cluster and click "Modify" in the "Actions" column to adjust its configuration. Configuration changes may affect cluster status. When modifying key attributes such as specification or instance count, make sure there are no jobs currently running on the cluster.
-:-: ![](.topwrite/assets/image_1733812147311.png =813)
+^
 #### Starting and Stopping a Virtual Cluster
 In the cluster list, click "Start" or "Stop" in the "Actions" column to start or stop the cluster. When stopping a cluster, it waits for all running jobs to complete before fully stopping.
-:-: ![](.topwrite/assets/image_1733812217836.png =813)
+^
 ^
 #### Deleting a Virtual Cluster
 In the cluster list, click "Delete" in the "Actions" column to delete the specified cluster. The cluster must be stopped and all jobs must be complete before deletion can proceed.
-:-: ![](.topwrite/assets/image_1733812348735.png =810)
+^
 ### SQL
@@ -193,14 +189,14 @@ In practice, it is recommended to test queries with different cluster sizes (for
 The following table provides sample specifications across several dimensions — business load type, execution frequency, job concurrency, data volume, and SLA requirements — for reference:
-| Business Scenario                       | Load Type                  | Execution Frequency | Job Concurrency | Data Volume | VCluster Type   | Job Latency SLA              | VCluster Size |
-| --------------------------------------- | -------------------------- | ------------------- | --------------- | ----------- | --------------- | ---------------------------- | ------------- |
-| ETL Scheduling Jobs                     | Near real-time offline     | Hourly              | 1               | 1 TB        | General Purpose | 15 min                       | 4             |
-|                                         | T+1 offline                | Daily               | 1               | 10 TB       | General Purpose | 4 hours                      | 8             |
-| Tableau/FineBI                          | Ad-hoc analytics           | Ad-hoc              | 8               | 1 TB        | General Purpose | <1 min, TP90 <5s             | 16            |
-| Data Application Products               | Applications               | On demand           | 8               | 100 GB      | Analytics       | <1s                          | 4             |
-|                                         |                            | On demand           | 96              | 100 MB      | Analytics       | <1s                          | 4             |
-| Singdata Web UI (Data Development/Test) | Ad-hoc analytics           | Ad-hoc              | 8               | 3 TB        | General Purpose | <1 min, TP90 <15s            | 16            |
+| Business Scenario                       | Load Type              | Execution Frequency | Job Concurrency | Data Volume | VCluster Type   | Job Latency SLA   | VCluster Size |
+| --------------------------------------- | ---------------------- | ------------------- | --------------- | ----------- | --------------- | ----------------- | ------------- |
+| ETL Scheduling Jobs                     | Near real-time offline | Hourly              | 1               | 1 TB        | General Purpose | 15 min            | 4             |
+|                                         | T+1 offline            | Daily               | 1               | 10 TB       | General Purpose | 4 hours           | 8             |
+| Tableau/FineBI                          | Ad-hoc analytics       | Ad-hoc              | 8               | 1 TB        | General Purpose | <1 min, TP90 <5s  | 16            |
+| Data Application Products               | Applications           | On demand           | 8               | 100 GB      | Analytics       | <1s               | 4             |
+|                                         |                        | On demand           | 96              | 100 MB      | Analytics       | <1s               | 4             |
+| Singdata Web UI (Data Development/Test) | Ad-hoc analytics       | Ad-hoc              | 8               | 3 TB        | General Purpose | <1 min, TP90 <15s | 16            |
 #### Load Isolation with Multiple Clusters
@@ -211,3 +207,5 @@ The following table provides sample specifications across several dimensions —
   * Periodic ELT tasks and online business report queries should use separate clusters for isolation. Use General Purpose for ELT and Analytics for reports to take full advantage of each type's performance characteristics. This also makes it easy to configure different auto-suspend times — set a short auto-suspend (e.g., 1 minute) for the ELT cluster, and a slightly longer one (e.g., 5 minutes) for the reporting cluster.
   * Isolate clusters running large jobs from those running small jobs. Configure a larger cluster for large jobs to ensure sufficient runtime, and a smaller cluster for small jobs to avoid underutilization and resource waste.
+^

package/bin/skills/lakehouse-doc-en/references/web-job-history.md CHANGED Viewed

@@ -1,121 +1,106 @@
 # Lakehouse Job History
-Through the job history page, you can view detailed information about queries executed in the Lakehouse account over the past 7 days. This page displays a list of historical jobs, including tasks submitted using your own jdbc jar, studio temporary queries, and studio periodic scheduling tasks.
+Through the job history page, you can view detailed information about queries executed in the Lakehouse account over the past 7 days. This page displays a list of historical jobs, including tasks submitted using a JDBC jar, Studio ad-hoc queries, and Studio scheduled tasks.
 ## Job History
-### View History
-Click on Compute in the left navigation bar, then click on Job History to enter the job history page:
-![](.topwrite/assets/image_1740557896004.png)
-## Job History Search
-- Supports searching by job ID generated by SQL jobs
-- Supports searching by status
-     - setup: SQL initialization phase, including operations such as compilation and optimization
-     - resuming_cluster: Waiting for vc to start, if it takes a long time, please contact technical support
-     - queued: Job is queued waiting for resources, if it takes a long time, check if vc resources are fully occupied, consider expanding vc
-     - running: SQL data processing time, you can click on diagnostics to view the time taken by each operator
-     - finish: Job has ended, some jobs may have a cleanup process in this stage, which can take time
-- Supports filtering by duration
-- Supports filtering by time, currently up to 10,000 jobs from the past seven days can be queried
-- Supports filtering by the name of the cluster where the job ran
-- Supports filtering by the job submitter
-- Supports filtering by queryTag
-    Users can use the command set query_tag="" to indicate the source of the job and tag the job when submitting SQL. This makes it easy to filter in this interface
-    - Set query_tag in the studio interface, select two days of SQL to execute simultaneously
-    ```SQL
-        set query_tag="test";
-        select 1;
-    ```
-- Add `query_tag` in the JDBC URL, so each submitted SQL will carry the `query_tag` to indicate the source, which can be filtered on the page.
-    ```text
-    jdbc:clickzetta://xxxx.api.singdata.com/default?schema=public&query_tag=test
-    ```
-- Set query_tag in python code
-```python
-# Establish connection
-conn = connect(username='',
- password='',
-service='api.singdata.com',
-instance='jnsxwfyr',
- workspace='', schema='public', vcluster='default')
-# Execute SQL
-cursor = conn.cursor()
-my_param["hints"]["query_tag"] ="test"
-cursor.execute('select 1;', parameters=my_param)
-```
-- The default Schema for the job, the context in which the submitted SQL runs, can be obtained through select current_schema().
+## View History
+Click "Compute" in the left navigation bar, then click "Job History" to enter the job history page:
+^
+## Interface
+* Supports searching by job ID generated by SQL jobs
+* Supports searching by status
+  * Initializing: SQL initialization phase, including operations such as compilation and optimization
+  * Cluster Starting: Waiting for the Virtual Cluster to start. If it takes a long time to start, please contact technical support
+  * Queued: Job is queued waiting for resources. If it takes a long time, check whether the Virtual Cluster resources are fully occupied and consider scaling up the Virtual Cluster
+  * Running: SQL data processing time. You can click into diagnostics to view the time taken by each operator
+  * Succeeded: Job has ended. Some jobs may have a cleanup process at this stage, which can take time
+* Supports filtering by duration
+* Supports filtering by time. Currently, up to 10,000 jobs from the past seven days can be queried
+* Supports filtering by the name of the cluster where the job ran
+* Supports filtering by the job submitter
+* Supports filtering by queryTag
+  Users can use the command `set query_tag=""` when submitting SQL to indicate the job source and tag the job, making it easy to filter in this interface.
+  * Set query\_tag in the Studio interface, select two SQL statements and execute simultaneously:
+  ```SQL
+      set query_tag="test";
+      select 1;
+  ```
+  * Add query\_tag in the JDBC URL so that every submitted SQL carries the query\_tag to indicate the source, which can be filtered on the page:
+  ```text
+  jdbc:clickzetta://demo_instance.cn-shanghai-alicloud.api.clickzetta.com/default?schema=public&query_tag=test
+  ```
+  * Set query\_tag in Python code:
+  ```python
+  # Establish connection
+  conn = connect(username='',
+   password='',
+  service='cn-shanghai-alicloud.api.clickzetta.com',
+  instance='demo_instance',
+   workspace='', schema='public', vcluster='DEFAULT')
+  # Execute SQL
+  cursor = conn.cursor()
+  my_param["hints"]["query_tag"] ="test"
+  cursor.execute('select 1;', parameters=my_param)
+  ```
+* The default Schema for the job is the context in which the submitted SQL runs, which can be obtained through `select current_schema()`.
 ## Job Details
 Enter the job details to view detailed information about the job.
-![](.topwrite/assets/image_1740557994319.png)
-**Field Information Explained as Follows**
-|        |                                                                                                                      |
-| ------ | -------------------------------------------------------------------------------------------------------------------- |
-| Field  | Description                                                                                                          |
-| Status | Indicates the status of the job, currently includes&#xA;Ready to execute: The job is being compiled and other operations&#xA;Waiting to execute: Waiting for resources&#xA;Executing: Running, the job is processing data&#xA;Execution successful: The job ran successfully&#xA;Execution terminated: The job was terminated&#xA;Execution failed: The job failed to run |
-| Submit Time | The time the server received the request to start                                                                 |
-| End Time    | The time the job ended                                                                                           |
-| Duration    | Includes compilation optimization, starting computing resources, queuing, and job running time                                                        |
-| Owner       | The user who submitted the job                                                                                   |
-| Spill to Disk | The size of the data spilled to disk, this parameter can help understand if the performance is slow due to insufficient cluster memory resources                                      |
-| Read from Cache | In the analytical cluster, the already read data will be cached first to speed up computation                                                      |
-| Output Records   | The number of output records of the job                                                                                                            |
-| Consumption     | Refers to the computing resources used by the job, excluding the computing resources while the job is waiting for IO.                                                                                        |
-| Cluster     | The cluster used to run the job                                                                                                            |
+^
 ### Stage Interface
-SQL execution is divided into each stage, and stages are executed from bottom to top. Clicking on a specific stage will show the specific time consumption of each stage.
+SQL execution is divided into stages, which are executed from bottom to top. Clicking on a specific stage will show the specific time consumption of each stage.
-![](.topwrite/assets/image_1740558003358.png)
+^
 **Field information is explained as follows**
-|            |                                                                                   |
-| ---------- | --------------------------------------------------------------------------------- |
-| Field         | Description                                                                                |
-| Status         | Indicates the status of the job, currently includes: &#xA;Waiting for execution: waiting for resources&#xA;Executing: running, the job is processing data&#xA;Execution successful: job ran successfully&#xA;Execution failed: job ran unsuccessfully |
-| Start Time       | The start time of the stage, stages in the analytical cluster will run simultaneously                                                       |
-| End Time       | The end time of the job                                                                          |
-| Duration         | The duration of the stage running                                                                       |
-| Spilled to Disk      | The size of the data spilled to disk, this parameter can help understand if the slow performance is due to insufficient memory resources in the cluster                                             |
-| Read from Cache     | In the analytical cluster, the already read data will be cached first. This speeds up computation                                                     |
-| Contains Operator | Stage                                                                             |
+|                    |                                                                                                                                                                                                                |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Field              | Description                                                                                                                                                                                                    |
+| Status             | Indicates the status of the job. Currently includes:&#xA;Queued: Waiting for resources&#xA;Running: Running, the job is processing data&#xA;Succeeded: Job ran successfully&#xA;Failed: Job ran unsuccessfully |
+| Start Time         | The start time of the stage. In AP clusters, stages run in parallel                                                                                                                                            |
+| End Time           | The end time of the job                                                                                                                                                                                        |
+| Duration           | The duration of the stage running                                                                                                                                                                              |
+| Spill to Disk      | The size of the data spilled to disk. This parameter indicates whether slow performance is due to insufficient cluster memory resources                                                                        |
+| Read from Cache    | In AP clusters, data that has already been read is cached first to accelerate computation                                                                                                                      |
+| Contains Operators | Stage                                                                                                                                                                                                          |
 ### Operator Interface
-In the operator interface, you can view the type of each operator and the upstream and downstream dependencies. An operator is a concept in the query plan that represents the specific steps and strategies for executing a query, including data access, transformation, and update.
+In the operator interface, you can view the type of each operator and its upstream and downstream dependencies. An operator is a concept in the query plan that represents the specific steps and strategies for executing a query, including data access, transformation, and updates.
-![](.topwrite/assets/image_1740558011631.png)
+^
 **Field information is explained as follows**
-|         |                                       |
-| ------- | ------------------------------------- |
-| Belongs to Stage | The stage corresponding to the operator                       |
-| Spilled to Disk   | The size of the data spilled to disk, this parameter can help understand if the slow performance is due to insufficient memory resources in the cluster |
-| Read from Cache  | In the analytical cluster, the already read data will be cached first. This speeds up computation         |
-| Total Rows     | The data currently processed by the operator                        |
-| Time Consumed | operate will run concurrently, currently showing the average time of operate |
-| Field         | Corresponds to the SQL script, corresponding field                          |
+| Field            | Description                                                                                                                             |
+| :--------------- | :-------------------------------------------------------------------------------------------------------------------------------------- |
+| Belongs to Stage | The stage corresponding to the operator                                                                                                 |
+| Spill to Disk    | The size of the data spilled to disk. This parameter indicates whether slow performance is due to insufficient cluster memory resources |
+| Read from Cache  | In AP clusters, data that has already been read is cached first to accelerate computation                                               |
+| Total Rows       | The data currently processed by the operator                                                                                            |
+| Duration         | Operators run concurrently. The displayed value is the average time of the operator                                                     |
+| Field            | Corresponds to the fields in the SQL script                                                                                             |
 ### Table Mode
-Supports stage switching table mode
+Supports switching stages to table mode
+^
-![](.topwrite/assets/image_1740558022227.png)
+Supports switching operators to table mode
-Supports operator switching table mode
-![](.topwrite/assets/image_1740558027758.png)
 ## Analyzing Failed Jobs
@@ -124,55 +109,56 @@ When a job fails to run, you can view the reason for the failure through the det
 ### SQL Syntax Error
 **Error Example**:
 ```SQL
 Execute select * from ttt;
 Error: CZLH-42000:[1,15] Semantic analysis exception - table or view not found - uat_demo_project.`public`.ttt
 ```
-**Error Code CZLH-42000** indicates an error related to SQL language parsing. [1,15] indicates that the error occurred on line 1, column 15 of the SQL. In this example, the reason is that the `ttt` table does not exist. Please note that if you submit tasks through Studio development, the job editor in development will include descriptive information, which is not submitted to the SQL engine. Therefore, the correct line number should subtract the preceding descriptive information. You can view the correct positional relationship through the job content in the job details or find the error location in the SQL editor.
+**Error code CZLH-42000** indicates an error related to SQL language parsing. `[1,15]` means the error occurred at line 1, column 15 of the SQL. In this example, the reason is that the `ttt` table does not exist.
 ## Analyzing Slow Running Jobs
-Slow running jobs may encounter issues during the compilation phase, the virtual cluster startup phase, or the execution phase. Below are the analyses and solutions for these phases:
+Slow running jobs may encounter issues during the compilation phase, the Virtual Cluster startup phase, or the execution phase. Below are analyses and solutions for these phases:
 ### Compilation Phase
-**Issue**: Job status shows "Preparing to execute".
+**Issue**: Job status shows "Initializing".
 **Possible Causes and Solutions**:
-1. **Complex execution plan**: The job may require a long time to optimize. Please be patient; it should not take more than 10 minutes under normal circumstances.
-2. **Compilation resources are fully occupied**: If you submit a large number of SQLs at once, it may lead to insufficient compilation resources. Please reduce the frequency of SQL submissions. If you have a large number of high-concurrency query requirements, please submit a ticket for assistance.
+1. **Complex execution plan**: The job may require a long time to optimize. Please be patient — it should not take more than 10 minutes under normal circumstances.
+2. **Compilation resources are fully occupied**: If you submit a large number of SQL statements at once, it may lead to insufficient compilation resources. Please reduce the frequency of SQL submissions. If you have a large number of high-concurrency query requirements, please submit a ticket for assistance.
 ### Virtual Cluster Startup Phase
-**Issue**: Job status shows "Cluster starting". The current status is that the computing cluster is being started.
+**Issue**: Job status shows "Cluster Starting". (The current status is that the compute cluster is being started)
-### Waiting Execution Phase
+### Queued Phase
-**Issue**: Job status shows "Waiting to execute".
+**Issue**: Job status shows "Queued".
 **Possible Causes and Solutions**:
-**Insufficient computing resources in the current cluster**: You can filter and view the currently running jobs through the interface. A large number of running jobs may be causing resource waiting. You can expand resources or terminate large running jobs to free up resources.
+1. **Insufficient computing resources in the current cluster**: You can filter and view the currently running jobs through the interface. A large number of running jobs may be causing resource queuing. You can scale up resources, or terminate large running jobs to free up resources.
 ### Execution Phase
-**Issue**: Job status shows "Running". At this stage, you can click to view the execution status of each operator.
+**Issue**: Job status shows "Running". At this stage you can click in to view the execution status of each operator.
 **Possible Causes and Solutions**:
 1. **Waiting for resources**: The job may be waiting for resource allocation. Please check the resource usage. If necessary, please submit a ticket for assistance.
-2. **Slow data reading speed**: The job may be executing slowly due to slow data reading speed. Please check the data storage and reading strategy. If necessary, optimize the data storage structure or adjust the reading strategy.
+2. **Slow data reading speed**: The job may be executing slowly due to slow data reading. Please check the data storage and reading strategy. If necessary, optimize the data storage structure or adjust the reading strategy.
-## Viewing Execution Plan and Operator Details
+### Share for Diagnosis
-During the execution phase, you can click on the executing operator to query specific steps and strategies. For example, moving the mouse over a specific operator can correspond to the specific operator executed in the SQL. This helps you identify which specific operator is causing the job to run slowly.
+After entering the job details page, click the "Share" button to share the job with a third party. Recipients can view the content without logging in.
+\:-: ![](.topwrite/assets/image_1740557522715.png =774)
+If you have any questions or need further assistance, please copy the link above and contact the Lakehouse team. We will diagnose and resolve the issue for you.
+## Viewing Execution Plan and Operator Details
-![](.topwrite/assets/image_1740558276614.png)
-## Share for Diagnosis
+During the execution phase, you can click on a specific operator to query its execution steps and strategies. For example, moving the mouse over a specific operator will highlight the corresponding operator in the SQL. This helps you identify which specific operator is causing the job to run slowly.
-After entering the assignment details page, click the “Share” button to share the assignment with others. Recipients can view the content without logging in.
-![](.topwrite/assets/image_1740558353576.png)
-If you need to stop sharing, you can revoke access to the link at any time.
-If you have any questions or need further assistance, please copy the link above and contact the Lakehouse team. We will diagnose and resolve the issue for you.
+^