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/pricing.md CHANGED Viewed

@@ -1,314 +1,70 @@
-# Overview of Billing Methods
+# Pricing and Billing
-Singdata Lakehouse is an integrated data platform built on cloud-native technology. The platform records the resources you consume in scenarios such as data integration, data analysis, storage, and network data transmission, and charges you accordingly based on three resource types — computing, storage, and network — depending on the cloud platform and region where the service occurs.
+Singdata bills by "product + resource type". Lakehouse is billed by three resource types — compute (CRU), storage, and network data transfer. AI Gateway is billed by tokens, with unit prices varying by model. Analytics Agent is a separate paid product with its own subscription-based pricing; for details please contact Singdata sales. The bills of each product are independent and can be viewed separately in the Billing Center of the console.
-The billing of Singdata Lakehouse is mainly based on the following aspects:
+<table style="width:100%; table-layout:auto;">
+<tr>
+<td style="width:50%; vertical-align:top; padding:0 16px 16px 0; overflow-wrap:break-word;">
-* **Computing Resources**: The billing unit for computing resources is **CRU\*hour**, where 1 CRU\*hour represents running with the same computing power for 1 hour in a service region of a cloud platform. The use of general-purpose, analytical, and synchronous computing clusters for data integration or data analysis, tasks processed using Python or Shell scripts, and operations such as automatic materialized views (Auto\_MV), data compression, and job scheduling automatically handled by the system will all generate computing resource consumption. Singdata will measure and bill based on the actual amount of computing power consumed.
-* **Storage Resources**: The billing unit for storage resources is **GiB**, and billing is based on the actual storage capacity you use on Singdata Lakehouse. The following scenarios will occupy storage capacity: 1) Data stored in Lakehouse in the form of tables, materialized views, etc.; 2) Data deleted but not yet cleaned up within the lifecycle of the data table; 3) Cached query results. Items 2 and 3 are currently only measured and temporarily free of charge.
-* **Data Transmission**: The billing unit for data transmission is **GB**, and billing is based on the actual amount of data transmitted. The following scenarios will incur data transmission fees: 1) Data queries through the public network, full download of query results; 2) Data transmission between Singdata Lakehouse and other data sources; 3) Network connectivity through the Internet, cross-VPC connections, dedicated lines, or other methods. For Internet network traffic, only the data transmission volume flowing out of Singdata Lakehouse is measured; uploading data to Singdata Lakehouse is free of charge.
+**Lakehouse**
-## Billing Methods
+Pay-as-you-go billing for compute clusters, storage, and network data transfer.
-### 1. Pay-as-you-go
+[View Lakehouse Pricing →](pricing-lakehouse.md)
-In Singdata Lakehouse, all types of resources are flexibly scalable and used on-demand. You only need to pay for the amount of resources actually used.
+</td>
+<td style="width:50%; vertical-align:top; padding:0 0 16px 16px; overflow-wrap:break-word;">
-| Resource Type       | Metering Method                     | Settlement Cycle |
-| ------------------- | ----------------------------------- | ---------------- |
-| Computing Resources | Metered by the second, in CRU       | Every hour       |
-| Storage Resources   | Sampled 24 hours a day, averaged    | Every day        |
-| Data Transmission   | Metered by actual traffic generated | Every hour       |
+**AI Gateway**
-This mode is primarily deducted through balance top-up via the Lakehouse console. Due to different prices of resources on different cloud platforms and in different regions, the unit prices of computing, storage, and data transmission may vary. Please refer to the pricing tables below for prices; the actual bill within the system shall prevail. You can view resource usage and cost details on the "Management Center" - "Billing Statement" page.
+Token-based billing for unified access to mainstream LLMs (Anthropic Claude, OpenAI GPT, Qwen, DeepSeek, GLM, Kimi, MiniMax, and more).
-### 2. Annual Prepaid
+[View AI Gateway Pricing →](pricing-ai-gateway.md)
-Singdata Lakehouse can also provide enterprise customers with specified resource specifications and annual prepaid billing methods. When using annual prepaid, the unit prices of computing and storage resources can offer corresponding discounts. For details, please contact Singdata sales personnel.
+</td>
+</tr>
+</table>
-## Billing Principles
+## FAQ
-### 1. Computing Resource Billing
+| Question | Documentation |
+|------|---------|
+| What are the trial account quotas | [Trial Account Quotas and Limits](trial-account-quotas-and-limits.md) |
+| How do I top up and check balance | [Account Funds](account-funds.md) |
+| How do I view bill details | [Billing](billing.md) |
+| How do I configure cost anomaly alerts | [Lakehouse Billing Anomaly Alert Configuration Guide](lakehouse_billing_anomaly_alert_configuration_guide.md) |
+| How do I manage usage and cost | [Cost Management](cost_management.md) |
-The billing items for [computing resources](https://www.singdata.com/documents/virtual-cluster) include: general-purpose computing clusters, analytical computing clusters, synchronous computing clusters, task scheduling, and serverless jobs. The billing cycle for computing resources **is measured in hours**.
+## Next Steps
-The billing principles for each computing resource item are as follows:
+<table style="width:100%; table-layout:auto;">
+<tr>
+<td style="width:33%; vertical-align:top; text-align:center; padding:12px; overflow-wrap:break-word;">
-#### General-purpose Computing Clusters
+**Try Before You Decide**
-When a general-purpose computing cluster starts and reaches the "running" state, it begins to generate corresponding CRU consumption based on the cluster's specification size and number of instances. When the computing cluster enters the "stopping" state, it stops generating CRU consumption.
+Sign up for a free trial account and evaluate the cost after experiencing core features.
-> 🗒️ **Billing Formula**:&#x20;
-> General-purpose Computing Cluster = Runtime (hours) × Cluster Specification (CRU) × CRU Unit Price (RMB/CRU\*hour)
+[Sign Up for Trial →](logging-in.md)
-The minimum specification for general-purpose computing resources is 1 CRU, the maximum is 256 CRU, with a step size of 1 CRU. The table below shows the specifications and corresponding hourly CRU consumption:
+</td>
+<td style="width:33%; vertical-align:top; text-align:center; padding:12px; overflow-wrap:break-word;">
-| Cluster Specification | Hourly CRU Consumption (CRU\*hour) |
-| --------------------- | ---------------------------------- |
-| 1                     | 1                                  |
-| 2                     | 2                                  |
-| 3                     | 3                                  |
-| 4                     | 4                                  |
-| 5                     | 5                                  |
-| ...                   | ...                                |
-| 256                   | 256                                |
+**On-Demand Subscription**
-#### Analytical Computing Clusters
+Top up balance, pay for actual consumption, stop anytime.
-The billing principle of analytical computing clusters is the same as that of general-purpose computing clusters, measured from the start time of the "running" state until entering the "stopping" state.
+[Open Service Instance →](logging-in.md)
-Analytical computing clusters support automatic instance scaling on top of the specifications. When query concurrency exceeds the maximum concurrency that all current instances can handle, the system will automatically scale out instances. Each additional instance increases the consumption of a computing cluster of the same specification. When reducing one instance still meets the current concurrency, the system will automatically scale in and reduce analytical computing resource consumption. Analytical clusters have elastic scaling enabled by default upon creation, with a default minimum of 1 instance and maximum of 2 instances. You can also manually set the minimum and maximum instance values for auto-scaling, with up to 25 instances.
+</td>
+<td style="width:33%; vertical-align:top; text-align:center; padding:12px; overflow-wrap:break-word;">
-> 🗒️ **Billing Formula**:&#x20;
-> Analytical Computing Cluster = Runtime (hours) × Number of Instances × Cluster Specification (CRU) × CRU Unit Price (RMB/CRU\*hour)
+**Annual Enterprise Procurement**
-The minimum specification for analytical computing resources is 1 CRU, the maximum is 256 CRU, with a step size of 2^n CRU. The table below shows the hourly CRU consumption for 1 to 5 instances:
+Annual prepayment with discounts; private deployment supported.
-| Cluster Specification | 1 Instance Hourly Consumption | 2 Instances Hourly Consumption | 3 Instances Hourly Consumption | 4 Instances Hourly Consumption | 5 Instances Hourly Consumption |
-| --------------------- | ----------------------------- | ------------------------------ | ------------------------------ | ------------------------------ | ------------------------------ |
-| 1                     | 1 CRU\*hour                   | 2 CRU\*hour                    | 3 CRU\*hour                    | 4 CRU\*hour                    | 5 CRU\*hour                    |
-| 2                     | 2 CRU\*hour                   | 4 CRU\*hour                    | 6 CRU\*hour                    | 8 CRU\*hour                    | 10 CRU\*hour                   |
-| 4                     | 4 CRU\*hour                   | 8 CRU\*hour                    | 12 CRU\*hour                   | 16 CRU\*hour                   | 20 CRU\*hour                   |
-| 8                     | 8 CRU\*hour                   | 16 CRU\*hour                   | 24 CRU\*hour                   | 32 CRU\*hour                   | 40 CRU\*hour                   |
-| 16                    | 16 CRU\*hour                  | 32 CRU\*hour                   | 48 CRU\*hour                   | 64 CRU\*hour                   | 80 CRU\*hour                   |
-| 32                    | 32 CRU\*hour                  | 64 CRU\*hour                   | 96 CRU\*hour                   | 128 CRU\*hour                  | 160 CRU\*hour                  |
-| 64                    | 64 CRU\*hour                  | 128 CRU\*hour                  | 192 CRU\*hour                  | 256 CRU\*hour                  | 320 CRU\*hour                  |
-| 128                   | 128 CRU\*hour                 | 256 CRU\*hour                  | 384 CRU\*hour                  | 512 CRU\*hour                  | 640 CRU\*hour                  |
-| 256                   | 256 CRU\*hour                 | 512 CRU\*hour                  | 768 CRU\*hour                  | 1024 CRU\*hour                 | 1280 CRU\*hour                 |
+[Contact Sales →](https://www.singdata.com/reservation)
-#### Synchronous Computing Clusters
-Synchronous computing clusters are used for running data integration tasks, including offline integration and real-time integration. Multiple integration tasks can be submitted to the same synchronous computing cluster to reuse resources. The billing principle of synchronous computing clusters is the same as that of general-purpose computing clusters, measured from the start time of the "running" state until entering the "stopping" state.
-> 🗒️ **Billing Formula**:&#x20;
-> Synchronous Computing Cluster = Runtime (hours) × Cluster Specification (CRU) × CRU Unit Price (RMB/CRU\*hour)
-Note: **The synchronous computing cluster is currently in trial operation**.During this period, to help you manage and account for offline and real-time business costs more precisely, the system will record billing details separately under the "Offline Integration" and "Real-time Integration" billing items on a per-job basis according to actual resource consumption. The CRU\*hour unit price remains unchanged under this billing model. When creating a synchronous cluster, you can use the "[Specification Estimation](https://www.singdata.com/documents/virtual-cluster)" feature to help determine the appropriate size.
-Offline integration tasks can automatically wake up the synchronous computing cluster and automatically stop it after the task is completed; real-time integration tasks require their synchronous computing cluster to remain in the "running" state.
-> 🗒️ **Billing Formulas during Trial Operation**:&#x20;
-> Offline Integration = Runtime (hours) × CRU consumed by offline integration (CRU) × CRU Unit Price (RMB/CRU\*hour)
->
-> Real-time Integration = Runtime (hours) × CRU consumed by real-time integration (CRU) × CRU Unit Price (RMB/CRU\*hour)
-After the trial operation ends, data integration fees will be merged into the "Synchronous Computing Cluster" billing item. When the new billing model changes, we will notify you one month in advance to ensure you have sufficient time for business evaluation.
-After official operation, the synchronous computing cluster will have specification restrictions: minimum specification of 0.25 CRU, maximum of 256 CRU, with no fixed step size restriction and support for any specification value. The hourly CRU consumption equals the cluster specification, for example:
-| Cluster Specification | Hourly CRU Consumption |
-| --------------------- | ---------------------- |
-| 0.25                  | 0.25 CRU\*hour         |
-| 0.26                  | 0.26 CRU\*hour         |
-| 0.27                  | 0.27 CRU\*hour         |
-| ...                   | ...                    |
-| 256                   | 256 CRU\*hour          |
-#### Task Scheduling
-Task scheduling billing mainly covers two types of scenarios: one is the scheduling computing resource consumption generated when Python, Shell, and other script tasks are executed; the other is the small amount of computing resource consumption generated during the job submission and scheduling management process of offline and real-time integration tasks.
-Task scheduling has no fixed minimum specification or step size restrictions. In all scenarios, the actual resource consumption from task scheduling will generate billing in CRU\*hour units.
-For Python, Shell, and other script tasks, the system will meter based on the computing resources allocated to the task and the actual runtime. The metering period starts when the task execution begins and ends when the task execution completes.
-For offline integration tasks, Singdata Lakehouse provides a small amount of computing resources for job submission and scheduling management. These resources begin metering after the offline integration task starts, do not consume during queue waiting, and persist throughout task execution.
-For real-time integration tasks, Singdata Lakehouse similarly provides a small amount of computing resources for job submission and scheduling management. These resources begin metering after the real-time integration task starts and end after the task is officially running. Computing resource consumption during this period will be metered.
-> 🗒️ **Billing Formula**:&#x20;
-> Task Scheduling = Runtime (hours) × Cluster Specification (CRU) × CRU Unit Price (RMB/CRU\*hour)
-#### Serverless Jobs
-Serverless jobs refer to jobs that do not require users to actively create computing cluster instances, but are handled by the public computing resources provided by Singdata Lakehouse. This includes query job scheduling, data compression, automatic materialized views, etc.
-The current CRU\*hour unit price for serverless jobs is the same as that of general-purpose computing clusters.
-> 🗒️ **Billing Formula**:&#x20;
-> Serverless Jobs = Runtime (hours) × Cluster Specification (CRU) × CRU Unit Price (RMB/CRU\*hour)
-### 2. Storage Capacity Billing
-Storage fees are calculated based on the actual storage capacity you use on the Lakehouse platform. The billing cycle for storage **is measured in days**.
-When you write data into the Lakehouse data warehouse, the written data and some of its metadata information will occupy storage capacity in Lakehouse. Lakehouse measures your actual data storage usage by sampling multiple times within a day and **uses the average value of the sampled storage capacity** as the storage capacity measurement value for that day for billing.
-When you use the [Time Travel ](https://www.singdata.com/documents/timetravel-summary)feature of Lakehouse, to ensure data multi-version and recoverability, Lakehouse will automatically back up your data in multiple versions. The multi-version backup data generated will incur corresponding storage fees, charged at the storage capacity unit price.
-When you perform SQL queries, to reduce the consumption of computing resources for repeated queries, the query results will be cached, exchanging storage costs for computing resource savings. This part of the storage usage will be included in "[Result Cache](https://www.singdata.com/documents/result_cache)" and charged at the storage capacity unit price.
-**Time Travel and Result Cache are currently free of charge**. You will be notified one month in advance when the billing status changes.
-> 🗒️ **Billing Formula**:&#x20;
-> Storage = Storage Duration (days) / 30 (days) × Daily Average Storage (GiB) × Storage Unit Price (RMB/GiB/month)
-### 3. Data Transmission Billing
-When you use Lakehouse as a data source for outbound network data transmission, such as downloading or exporting data through the public network, data transmission fees will be incurred. Data transmission is metered based on the actual amount of data transferred, with a billing cycle **measured in hours**.
-When you use other data sources to transfer data into Lakehouse through the Internet, the network transfer traffic used will not incur fees.
-When you use dedicated lines, Private Link, or other network products to achieve cross-cloud vendor, cross-region, or cross-VPC network connectivity, the network connectivity itself will incur data transmission fees. These fees may be charged by multiple parties due to different network connectivity methods. Data transmission fees generated on the Singdata Lakehouse side are charged by Singdata, while data transmission fees generated in your cloud platform account are charged directly by the cloud platform.
-> 🗒️ **Billing Formula**:&#x20;
-> Data Transmission = Data Transfer Volume (GB) × Data Transmission Unit Price (RMB/GB)
-### 4. Other Cloud Resource Billing
-When Singdata Lakehouse performs metadata management, parses SQL statements, generates query plans, schedules and allocates query tasks, and merges and cleans data files, it will consume cloud resources. Lakehouse will meter the consumption of these cloud resources, which are currently free for a limited time. You will be notified one month in advance when the billing status changes.
-## Pricing
-### 1. CRU Hour Price
-**Standard Edition**：
-| Cloud Provider | Region    | Version          | Unit Price          |
-| -------------- | --------- | ---------------- | ------------------- |
-| Alibaba Cloud  | Shanghai  | Standard Edition | 3.5 RMB/CRU\* hour  |
-|                | Beijing   | Standard Edition | 3.5 RMB/CRU\* hour  |
-|                | Hangzhou  | Standard Edition | 3.5 RMB/CRU\* hour  |
-|                | Singapore | Standard Edition | 0.8 USD/CRU\* hour  |
-| Tencent Cloud  | Beijing   | Standard Edition | 3.5 RMB/CRU\* hour  |
-|                | Shanghai  | Standard Edition | 3.5 RMB/CRU\* hour  |
-|                | Guangzhou | Standard Edition | 3.5 RMB/CRU\* hour  |
-| AWS            | Beijing   | Standard Edition | 9.95 RMB/CRU\* hour |
-|                | Singapore | Standard Edition | 1.24 USD/CRU\* hour |
-**Enterprise Edition**：
-| Cloud Provider | Region    | Version            | Unit Price          |
-| -------------- | --------- | ------------------ | ------------------- |
-| Alibaba Cloud  | Shanghai  | Enterprise Edition | 5.25 RMB/CRU\* hour |
-|                | Beijing   | Enterprise Edition | 5.25 RMB/CRU\* hour |
-|                | Hangzhou  | Enterprise Edition | 5.25 RMB/CRU\* hour |
-|                | Singapore | Enterprise Edition | 1.2 USD/CRU\* hour  |
-| Tencent Cloud  | Beijing   | Enterprise Edition | 5.25 RMB/CRU\* hour |
-|                | Shanghai  | Enterprise Edition | 5.25 RMB/CRU\* hour |
-|                | Guangzhou | Enterprise Edition | 5.25 RMB/CRU\* hour |
-| AWS            | Beijing   | Enterprise Edition | 15 RMB/CRU\* hour   |
-|                | Singapore | Enterprise Edition | 1.86 USD/CRU\* hour |
-Note: In addition to the Standard Edition, the platform also offers an Enterprise Edition with enhanced data governance and security capabilities. The CRU hour unit price for the Enterprise Edition is higher than that of the Standard Edition. For a detailed comparison of features between the two editions, please refer to the product documentation at [Editions Overview](editionsoverview.md).
-### 2.Storage Capacity Price
-| Cloud Provider | Region    | Version                               | Storage Capacity Price |
-| -------------- | --------- | ------------------------------------- | ---------------------- |
-| Alibaba Cloud  | Shanghai  | Enterprise Edition & Standard Edition | 0.12 RMB/GiB/month     |
-|                | Singapore | Enterprise Edition & Standard Edition | 0.017 USD/GiB/month    |
-| Tencent Cloud  | Beijing   | Enterprise Edition & Standard Edition | 0.12 RMB/GiB/month     |
-|                | Shanghai  | Enterprise Edition & Standard Edition | 0.12 RMB/GiB/month     |
-|                | Guangzhou | Enterprise Edition & Standard Edition | 0.12 RMB/GiB/month     |
-| AWS            | Beijing   | Enterprise Edition & Standard Edition | 0.195 RMB/GiB/month    |
-|                | Singapore | Enterprise Edition & Standard Edition | 0.025 USD/GiB/month    |
-Note: Since the billing cycle for storage is measured in days, the monthly unit price shown above is prorated on a 30-day basis for daily deductions.
-### 3. Data Transmission Pricing
-| Cloud Provider | Region    | Edition                               | Internet Data Transfer Price |
-| -------------- | --------- | ------------------------------------- | ---------------------------- |
-| Alibaba Cloud  | Shanghai  | Enterprise Edition & Standard Edition | 0.8 RMB/GB                   |
-|                | Singapore | Enterprise Edition & Standard Edition | 0.081 USD/GB                 |
-| Tencent Cloud  | Beijing   | Enterprise Edition & Standard Edition | 0.8 RMB/GB                   |
-|                | Shanghai  | Enterprise Edition & Standard Edition | 0.8 RMB/GB                   |
-|                | Guangzhou | Enterprise Edition & Standard Edition | 0.8 RMB/GB                   |
-| AWS            | Beijing   | Enterprise Edition & Standard Edition | 0.933 RMB/GB                 |
-|                | Singapore | Enterprise Edition & Standard Edition | 0.12 USD/GB                  |
-## Cost Examples in Common Scenarios
-### General-purpose Computing Cluster Cost Example
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A general-purpose computing cluster with a specification of 2 CRU, running for 1 hour, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * 1 hour × 2 CRU × 1.24 USD/CRU\*hour = **2.48 USD**
-* A general-purpose computing cluster with a specification of 1 CRU, running for 1 minute and 20 seconds (approximately 1.33 minutes), with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * 1.33/60 minutes × 1 CRU × 1.24 USD/CRU\*hour = **0.027 USD**
-* A general-purpose computing cluster with a specification of 1 CRU running from 10:00-10:02 for 2 minutes, and another general-purpose computing cluster with a specification of 2 CRU running from 10:00-10:10 for 10 minutes, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * (2/60 minutes × 1 CRU × 1.24 USD/CRU\*hour) + (10/60 minutes × 2 CRU × 1.24 USD/CRU\*hour) = 0.041 USD + 0.413 USD = **0.455 USD**
-### Analytical Computing Cluster Cost Example
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* An analytical cluster with a specification of 1 CRU, running for 30 minutes with 1 instance, and then running for 30 minutes with 2 instances, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * (30/60 minutes × 1 instance × 1 CRU × 1.24 USD/CRU\*hour) + (30/60 minutes × 2 instances × 1 CRU × 1.24 USD/CRU\*hour) = 0.62 USD + 1.24 USD = **1.86 USD**
-### Offline Integration Task Cost Example
-During the current trial operation period, offline integration tasks are not charged separately; only the running costs of the synchronous computing cluster to which the tasks are submitted are charged. Offline integration tasks can automatically wake up the synchronous computing cluster.
-An offline integration task requires computing resources for scheduling and concurrent execution. A single offline task typically requires at least approximately 0.05 CRU of scheduling resources, with a total consumption of at least approximately 0.1 CRU (0.05 CRU + 1 × 0.05 CRU). Based on this estimate, 5 single-concurrent offline integration tasks can fully utilize a synchronous computing cluster with a specification of 0.5 CRU.
-> 🗒️ **Estimation Formula**:&#x20;
-> Offline Integration Task Resource Consumption ≈ Scheduling Resource Specification (CRU) + Concurrency × Scheduling Resource Specification (CRU)
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A single-concurrent offline integration task running for 10 minutes, with actual hourly computing resource consumption of 0.1 CRU, and a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * 10/60 minutes × 0.1 CRU × 1.24 USD/CRU\*hour = **0.021 USD**
-* A single-concurrent offline integration task running from 10:00-10:10 for 10 minutes with actual hourly consumption of 0.1 CRU, and another 5-concurrent offline integration task running from 10:05-10:25 for 20 minutes with actual hourly consumption of 0.3 CRU, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * (5/60 minutes × 0.1 CRU × 1.24 USD/CRU\*hour) + (5/60 minutes × 0.4 CRU × 1.24 USD/CRU\*hour) + (15/60 minutes × 0.3 CRU × 1.24 USD/CRU\*hour) = 0.010 USD + 0.041 USD + 0.093 USD = **0.145 USD**
-### Real-time Integration Task Cost Example
-During the trial operation period, in addition to offline integration tasks, the computing resource consumption of real-time integration tasks in the synchronous computing cluster is also metered separately.
-Unlike offline integration tasks, real-time integration tasks run continuously after startup and perform real-time data caching and state management in memory. Therefore, the execution resource consumption of real-time tasks does not have a simple linear relationship with concurrency, but mainly depends on the complexity of data processing and the required state cache size. A single-concurrent real-time integration task will incur at least approximately 0.05 CRU of scheduling resource consumption and approximately 0.0625 CRU of execution consumption, totaling at least approximately 0.1125 CRU per hour.
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A single-concurrent real-time integration task running for 24 hours, with actual hourly resource consumption of 0.1125 CRU, requiring a minimum cluster specification of 0.25 CRU, and a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * 24 hours × 0.1125 CRU × 1.24 USD/CRU\*hour = **3.348 USD**
-* A multi-concurrent real-time integration task consuming 1 CRU per hour running from January 1-5 for 5 days, and another multi-concurrent real-time integration task consuming 2 CRU per hour running from January 3-10 for 8 days, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * (2 × 24 hours × 1 CRU × 1.24 USD/CRU\*hour) + (3 × 24 hours × 3 CRU × 1.24 USD/CRU\*hour) + (5 × 24 hours × 2 CRU × 1.24 USD/CRU\*hour) = 59.52 USD + 267.84 USD + 297.60 USD = **624.96 USD**
-### Synchronous Computing Cluster Cost Example
-After the trial operation ends, synchronous computing clusters will be billed according to this standard.
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A synchronous cluster with a specification of 2 CRU, running for 1 hour, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * 1 hour × 2 CRU × 1.24 USD/CRU\*hour = **2.48 USD**
-* A real-time integration task consuming 0.2 CRU per hour running from January 1-5 for 5 days, with an additional offline integration task consuming 0.1 CRU running for 1 hour on January 2 from 0:00-1:00, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * "**Fixed" mode** total cost: 5 × 24 hours × 0.5 CRU × 1.24 USD/CRU\*hour = **74.40 USD**
-  * "**Elastic Scaling" mode** total cost: (1 × 24 hours × 0.25 CRU × 1.24 USD/CRU\*hour) + (1 hour × 0.5 CRU × 1.24 USD/CRU\*hour) + ((23 + 3×24) hours × 0.25 CRU × 1.24 USD/CRU\*hour) = 7.44 USD + 0.62 USD + 29.45 USD = **37.51 USD**
-As shown in the examples above, to better save synchronous computing resource costs, it is recommended to reuse synchronous computing cluster resources as much as possible and avoid using overly large specifications.
-### Task Scheduling - Python Script Task Cost Example
-When executing Python script tasks, the cost is calculated based on the task execution time and the computing resources consumed. Generally, when a Python script runs for 1 hour, the computing resources used are 0.125 CRU.
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A Python script task with an execution time of 10 minutes, with a unit price of 1.24 USD per CRU\*hour, the cost is:
-  * 10/60 minutes × 0.125 CRU × 1.24 USD/CRU\*hour = **0.026 USD**
-### Storage Capacity Cost Example
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A workspace with a daily storage capacity low point of 910 GiB, high point of 1100 GiB, and daily average of 1000 GiB, with a monthly storage unit price of 0.025 USD/GiB/month (calculated on a 30-day basis), the storage cost for that day is:
-  * 1/30 month × 1000 GiB × 0.025 USD/GiB/month = **0.833 USD**
-### Data Transmission Cost Example
-Taking an AWS Singapore Standard Edition service instance in SaaS mode as an example:
-* A task generating 10 GB of outbound network data transmission traffic, with a data transmission unit price of 0.12 USD/GB, the data transmission cost is:
-  * 10 GB × 0.12 USD/GB = **1.20 USD**
-^
+</td>
+</tr>
+</table>

package/bin/skills/lakehouse-doc-en/references/private-link-general.md CHANGED Viewed

@@ -9,7 +9,6 @@ In the **Lakehouse** platform, the application scenarios of Private Link mainly
 **1. User VPC → Lakehouse (Inbound)**
 Within the same region and availability zone of the cloud vendor, access Lakehouse (JDBC gateway, IGS, etc.) services from the user's VPC through the cloud vendor's Private Link service.
-:-: ![](.topwrite/assets/Unnamed_Drawing.drawio.png)
 For example:
@@ -22,7 +21,6 @@ At this time, the Lakehouse Private Link feature is needed to establish an endpo
 **2. Lakehouse → User VPC (Outbound)**
 When it is necessary to connect from Lakehouse (located in Singdata VPC) to user-defined services (such as a self-built MySQL database within the user VPC), Private Link is also used for private network access.
-:-: ![](.topwrite/assets/private_link_access_customer.png)
 For example:
 A financial company chooses to use Lakehouse for unified data storage and analysis, but its core business database is stored within a private VPC and has strict security policies prohibiting the exposure of database ports to the public internet. Lakehouse needs to read data in real-time for subsequent analysis and risk control model training.

package/bin/skills/lakehouse-doc-en/references/pyspark-to-zettapark-migration-f1.md CHANGED Viewed

@@ -108,7 +108,7 @@ session = Session.builder.configs({
     "instance":  os.environ["CLICKZETTA_INSTANCE"],
     "workspace": os.environ["CLICKZETTA_WORKSPACE"],
     "schema":    "f1_processed",
-    "vcluster":  os.environ.get("CLICKZETTA_VCLUSTER", "default_ap"),
+    "vcluster":  os.environ.get("CLICKZETTA_VCLUSTER", "DEFAULT_AP"),
 }).create()
 df = session.read.option("header", "true").csv("vol://f1_raw.formula1_raw_vol/raw/circuits.csv")

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

@@ -1,3 +1,7 @@
+# Python SDK Real-time Write
+## Singdata Lakehouse Python SDK Real-time Write
 ## Installation
 1. **Uninstall Old Versions**
@@ -11,7 +15,7 @@
 2. **Install clickzetta connector**
-   Install the ingestion package, which requires Python version 3.7 or higher:
+   Install the ingestion package, which requires Python version 3.10 or higher:
    ```python
    pip install clickzetta-connector
@@ -232,7 +236,7 @@ with connect(username='your_username',
              instance='your_instance',
              workspace='your_workspace',
              schema='your_schema',
-             vcluster='default') as conn:
+             vcluster='DEFAULT') as conn:
     # Create a primary key table
     cursor = conn.cursor()
@@ -308,6 +312,6 @@ with connect(username='your_username',
 ## Summary
-The real-time write feature of the ClickZetta Python SDK provides an efficient and flexible way to write data, supporting various data types and operation modes. By configuring parameters appropriately, you can optimize write performance for different scenarios.
+The real-time write feature of the Singdata Python SDK provides an efficient and flexible way to write data, supporting various data types and operation modes. By configuring parameters appropriately, you can optimize write performance for different scenarios.
 For primary key tables and regular tables, different operation modes and row operation types are required. Primary key tables must use CDC mode and can only use UPSERT and DELETE_IGNORE operations; regular tables typically use APPEND_ONLY mode and INSERT operations.

package/bin/skills/lakehouse-doc-en/references/python-sample-put-github-rt-events.md CHANGED Viewed

@@ -67,7 +67,7 @@ def get_lakehouse_connect():
     schema='public',
-    vcluster='default')
+    vcluster='DEFAULT')
     return conn

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

@@ -1,6 +1,6 @@
 # Python Task
-> [Preview Release] This feature is currently in the invite-only preview release phase. To use it, please contact our technical support team for assistance.
+> \[Preview Release] This feature is currently in the invite-only preview release phase. To use it, please contact our technical support team for assistance.
 In many data analysis and processing scenarios, especially in BI+AI analysis scenarios, combining Python and SQL can greatly improve the efficiency of data analysis and processing. In Singdata Lakehouse, we provide a Python script task type for running Python code.

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

@@ -1,4 +1,4 @@
-# Singdata Connector Official Python SDK
+# ClickZetta Connector Python SDK
 `clickzetta-connector` is the official Python SDK for Singdata Lakehouse. It follows the PEP-249 specification and provides a SQL call interface compliant with the Python Database API style, supporting queries, writes, bulk inserts, and asynchronous execution.
@@ -18,7 +18,7 @@
 pip install clickzetta-connector
 ```
-Python version >= 3.7 is required.
+Python version >= 3.10 is required.
 If an older version is installed, uninstall it first to avoid conflicts:
@@ -40,7 +40,7 @@ conn = connect(
     instance='your_instance',                          # Instance name
     workspace='your_workspace',                        # Workspace name
     schema='public',                                   # Default schema
-    vcluster='default'                                 # Compute cluster name
+    vcluster='DEFAULT'                                 # Compute cluster name
 )
 ```

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

@@ -17,7 +17,7 @@ conn = connect(
     instance='your_instance',
     workspace='your_workspace',
     schema='public',
-    vcluster='default'
+    vcluster='DEFAULT'
 )
 cursor = conn.cursor()
 ```
@@ -195,7 +195,7 @@ conn = connect(
     instance='your_instance',
     workspace='your_workspace',
     schema='public',
-    vcluster='default'
+    vcluster='DEFAULT'
 )
 cursor = conn.cursor()

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

@@ -2,7 +2,7 @@
 This page provides complete, runnable examples of `clickzetta-connector` for common business scenarios.
-For connection configuration and basic usage, see [Singdata Connector Python SDK](connector.md).
+For connection configuration and basic usage, see [ClickZetta Connector Python SDK](connector.md).
 ---
@@ -21,7 +21,7 @@ conn = connect(
     instance='your_instance',
     workspace='your_workspace',
     schema='public',
-    vcluster='default'
+    vcluster='DEFAULT'
 )
 cursor = conn.cursor()
 ```

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

@@ -1,6 +1,6 @@
 # Python SDK
-`clickzetta-connector` is the official Python SDK for Singdata Lakehouse. It follows the PEP 249 specification and provides four integration methods: SQL queries, SQLAlchemy ORM, bulk writes (Bulkload), and real-time streaming writes. Python 3.7 and above is supported.
+`clickzetta-connector` is the official Python SDK for Singdata Lakehouse. It follows the PEP 249 specification and provides four integration methods: SQL queries, SQLAlchemy ORM, bulk writes (Bulkload), and real-time streaming writes. Python 3.10 and above is supported.
 ---

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

@@ -16,9 +16,9 @@ Currently supported data source types:
 In the configuration panel of a Python/Shell task, you can select one or more data sources to use (make sure the data source has already been created and connection-tested under Management → Data Sources). This configuration applies to both direct runs and scheduled runs of the task:
-![](.topwrite/assets/image_1742284598370.png =560)
+^
-*Note: The default Lakehouse data source for the current workspace is accessible in code without needing to be added here.*
+*Note: The default Lakehouse data source for the current workspace is accessible in code without needing to be added here*.
 ### Accessing a Data Source in Code
@@ -144,7 +144,7 @@ import pandas as pd
 from clickzetta_dbutils import get_active_lakehouse_engine
-engine = get_active_lakehouse_engine(vcluster="default",schema="brazilianecommerce")
+engine = get_active_lakehouse_engine(vcluster="DEFAULT",schema="brazilianecommerce")
 ```
 Connect and run a query:
@@ -176,7 +176,7 @@ Sets the schema for the connection.
 def use_schema(self, schema: str) -> 'DatabaseConnectionManager'
 ```
-*Note: Due to SQLAlchemy's design, for PostgreSQL, `use_schema` should be set to the database name.*
+*Note: Due to SQLAlchemy's design, for PostgreSQL*, \`\` *should be set to the database name*.
 #### use\_vcluster
@@ -194,7 +194,7 @@ Sets additional connection options.
 def use_options(self, options: dict) -> 'DatabaseConnectionManager'
 ```
-*Note: Due to SQLAlchemy's design, the PostgreSQL schema should be set to `undefined"})`*
+*Note: Due to SQLAlchemy's design, the PostgreSQL schema should be set to* `undefined"})`
 #### use\_query
@@ -306,21 +306,21 @@ from clickzetta_dbutils import get_active_engine
 ```
-Option 1: Using get_active_engine:
+Option 1: Using get\_active\_engine:
 ```py
 engine = get_active_engine("LAKEHOUSE_source_name",
-                          vcluster="default",
+                          vcluster="DEFAULT",
                           workspace="test-workspace",
                           schema="public")
 ```
-Option 2: Using get_active_lakehouse_engine:
+Option 2: Using get\_active\_lakehouse\_engine:
 ```py
 from clickzetta_dbutils import get_active_lakehouse_engine
-engine = get_active_lakehouse_engine(vcluster="default",
+engine = get_active_lakehouse_engine(vcluster="DEFAULT",
                                    workspace="test-workspace")
 with engine.connect() as conn:
     results = conn.execute(text("select 1"))
@@ -354,3 +354,5 @@ python /tmp/db_utils_demo.py
 3. When using a Lakehouse data source, the `vcluster` parameter is required. The Lakehouse data source uses the built-in Lakehouse data source visible under Management → Data Sources.
 4. Data source connection details are handled securely to prevent plaintext password exposure.
 5. Multiple data sources of different types can be used within the same node.
+^