@clickzetta/cz-cli-darwin-arm64 0.3.94 → 0.3.96

package/bin/skills/lakehouse-doc-en/references/manage-accounts.md

@@ -0,0 +1,187 @@
+# Account Management Guide
+
+This guide provides detailed instructions on how to manage your Singdata Lakehouse account, including logging into the Management Center, managing account information, and managing users.
+
+## 1. Basic Concepts
+
+### Account Name
+
+In Singdata Lakehouse, each account has a unique identifier used to distinguish different accounts globally. The account name consists of an 8-character random string automatically generated when you complete registration. The account name also determines your login address and some access configurations.
+
+The account name is your unique identifier within Singdata Lakehouse and cannot be changed once generated. You can find your account name from the prompt shown after completing registration or on the Home page of the Management Center.
+
+:-: ![](.topwrite/assets/image_1739329828430.png =780)
+
+^
+
+:-: ![](.topwrite/assets/image_1739329908616.png =783)
+
+### Login Address
+
+In Singdata products, each account has its own dedicated login address. The format of the login address is \<your\_account\_name>.accounts.clickzetta.com.
+
+:-: ![](.topwrite/assets/image_1739329970639.png =799)
+
+### Service Instance Name
+
+Singdata Lakehouse is a multi-cloud big data platform that supports creating service instances across different regions of various cloud providers. Each service instance is created within a specific region, where a logical resource area is allocated from the infrastructure to provide Lakehouse services to you. The service instance name (instance_name) is the unique identifier of the service instance, automatically generated when you create the service instance, consisting of an 8-character random string. You can find your service instance name in the service instance URL or in the top-right corner of the service instance Home page.
+
+:-: ![](.topwrite/assets/image_1740540520113.png =807)
+
+### Account Registration Phone Number
+
+The account registration phone number is the mobile phone number you enter when creating your account and adding the first user. Initially, the account phone number is the same as the phone number of the first user under your account. An account administrator can change the registration phone number in the Management Center. Please keep your registration phone number safe, as in Singdata products, each registration phone number can only correspond to one account, and it is the sole credential for recovering your account.
+
+:-: ![](.topwrite/assets/image_1739330026163.png =806)
+
+^
+
+^
+
+## 2. Account Name and Identifier
+
+### Why an Account Name is Needed
+
+* **Global Uniqueness**: The account name uniquely identifies your account across the global Singdata Lakehouse service network.
+* **Security Control**: When enabling account security policies and integrating with third-party applications, the account name is required for access and interaction.
+
+### Common Scenarios for the Account Name
+
+The Lakehouse account name is primarily used in the following scenarios:
+
+**1. Logging into the Lakehouse Web Interface**
+
+When logging into the Lakehouse Management Center or web interface, you need to enter the correct account URL in your browser (\<your\_account\_name>.accounts.clickzetta.com).
+
+^
+
+### Why a Service Instance Name is Needed
+
+* **Global Uniqueness**: The instance name uniquely identifies your service instance across the global Singdata Lakehouse service network. The instance name includes region information and allows direct interaction with the Lakehouse service within that region, simplifying the access path.
+* **Security Control**: When enabling network security policies and using third-party clients to access Lakehouse, the instance name is required for access and interaction.
+* **Resource Linking**: When performing data sharing and similar features, you need to explicitly specify the target or source account's service instance name.
+
+### Common Scenarios for the Service Instance Name
+
+**1. Lakehouse CLI / Other Clients / Drivers**
+
+When using CLI, JDBC drivers, Python/R/Java clients, or third-party tools (such as BI tools) to connect to Lakehouse, you need to specify the service instance name in the connection configuration.
+
+**2. Third-Party Application and Service Integration**
+
+When external applications (such as data analytics platforms, ETL tools, or cloud storage services) interact with Lakehouse, you need to provide the service instance name to identify the target Lakehouse service.
+
+**3. Data Sharing Operations**
+
+In Lakehouse's "Data Sharing" feature, you need to use the service instance name to define the scope of operations.
+
+^
+
+## Lakehouse Account URL and Login
+
+### Login Address Format
+
+In Singdata Lakehouse, each account has its own dedicated login address (URL). The general format is as follows:
+
+[https://\<your\_account\_name>.accounts.clickzetta.com](https://\<your\_account\_name>.accounts.clickzetta.com)
+
+Example:
+
+If your account name is 41nprq1k, then the login address is:
+
+41nprq1k.accounts.clickzetta.com
+
+### Logging in with the Account Name
+
+You can directly enter `https://\<your\_account\_name>.accounts.clickzetta.com` in your browser to open the login page. On the login page, you need to enter or select the correct account name, along with your username and password. Your account may have one or more users, and you can log in as any user on the above page. You can also recover your username or reset your user password by entering the user's mobile phone number. When multiple users share the same phone number, you can recover all associated usernames through that phone number and choose the one you want to log in with.
+
+### Login Flow and Recovery Methods
+
+1. Visit `https://\<account\_identifier>.accounts.clickzetta.com` or the unified entry `https://accounts.clickzetta.com`.
+
+2. On the login page, enter or select the correct account name, and enter your **username** and **password**.
+
+3. If you forget your username or password, after entering the account name, you can recover them using the user's phone number.
+
+When multiple users share the same phone number, you can recover all associated usernames through that number and select the desired user to log in.
+
+4. If you forget your account name, you can recover it on the login page using the account's registration phone number. Each phone number corresponds to only one registered account.
+
+^
+
+## Using Account Identifiers in SQL / Configuration Files / Third-Party Tools
+
+To correctly specify the target Lakehouse account in various environments, you need to choose the appropriate account identifier format based on the specific scenario:
+
+### Using in SQL Statements
+
+When you need to reference other accounts in Lakehouse SQL (for example, for data sharing), use the service instance name (instance_name).
+
+For example:
+
+`-- Specify the sharing instance for data sharing`
+
+`ALTER SHARE share_demo ADD INSTANCE <instance_name>;`
+
+### Using in Configuration Files or Third-Party Tools
+
+* **SQL Clients, Drivers, or Library Configuration**
+
+In configuration files for certain SQL clients (such as DBeaver), JDBC drivers, or Python/Java libraries, you need to configure connection parameters. For example, when configuring a DBeaver driver:
+
+:-: ![](.topwrite/assets/image_1740549280083.png =361)
+
+In JDBC connection strings, you need to use the service instance name (instance_name), such as:
+
+`jdbc:clickzetta://<your_instance_name>.ap-southeast-1-alicloud.api.clickzetta.com/demo_workspace?username=demo_user&password=DemoPassword&schema=public&virtualCluster=DEFAULT`
+
+For example, when configuring the Python SDK, you need to use the service instance name (instance\_name):
+
+`from clickzetta import connect`
+
+`# Establish a connection`
+
+`conn = connect(username='username',`
+
+`               password='password',`
+
+`               service='<region\_id>.api.clickzetta.com',`
+
+`               instance='your_instance_name',`
+
+`               workspace='quickstart_ws',`
+
+`               schema='public',`
+
+`               vcluster='default')`
+
+^
+
+^
+
+## Maintaining Account Information
+
+### Viewing the Account Registration Phone Number
+
+When you log into Singdata with a user who has the account administrator role, you can manage your account in the Management Center. On the "Account Home" page, you can view the account's basic information and the account's login URL. You can also click the "Edit" button next to the registration phone number to change the account's registered phone number.
+Please note that on the "Account Center" page, you will see the "Registration Phone Number" under "Account Information" -- this is the phone number bound to the account and can be used to recover the account name; and the "Registration Phone Number" under "User Information" -- this is the phone number of the currently logged-in user, only bound to the current user's identity, and can be used for MFA verification, username recovery, password reset, etc. Please distinguish between the two.
+
+![](.topwrite/assets/image_1740550879753.png)
+
+### Changing the Account Registration Phone Number
+
+If you need to change the account registration phone number, log in with a user who has the account administrator (account_admin) role. After entering the "Account Center", click the Edit button next to "Registration Phone Number" in the "Account Information" section. After verifying the old phone number, you can enter and save a new phone number.
+
+:-: ![](.topwrite/assets/image_1740551806201.png =765)
+
+:-: ![](.topwrite/assets/image_1740551835302.png =438)
+
+### Changing the Account Name or Service Instance Name
+
+The account name (account\_name) and service instance name (instance\_name) are both globally unique names and cannot be modified once generated.
+
+^
+
+^
+
+For further management of users under your account, please refer to [Managing Users](account_user_management.md).

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

@@ -0,0 +1,181 @@
+# Account & Billing
+
+This guide covers how to manage your Singdata Lakehouse account, including logging into the Management Center, managing account information, and managing users.
+
+## Basic Concepts
+
+### Account Name
+
+In Singdata Lakehouse, every account has a unique identifier used to distinguish accounts globally. The account name consists of an 8-character random string that is automatically generated when you complete registration. The account name also determines your login URL and certain access configurations.
+
+The account name is your unique identifier within Singdata Lakehouse and cannot be changed once generated. You can find your account name in the prompt shown after registration or on the Management Center home page.
+
+:-: ![](.topwrite/assets/image\_1739329828430.png =780)
+
+^
+
+:-: ![](.topwrite/assets/image\_1739329908616.png =783)
+
+### Login URL
+
+In Singdata products, each account has its own dedicated login URL. The login URL follows the format: `<your_account_name>.accounts.singdata.com`.
+
+:-: ![](.topwrite/assets/image\_1739329970639.png =799)
+
+### Service Instance Name
+
+Singdata Lakehouse is a multi-cloud big data platform that supports creating service instances across different regions of multiple cloud providers. Each service instance provisioned generates a unique identifier within that region and carves out a logical area within the infrastructure resources to provide Lakehouse services. The service instance name (`instance_name`) is the unique identifier for a service instance. It is automatically generated when you provision the instance and consists of an 8-character random string. You can find your service instance name in the service instance URL or on the right side of the service instance home page.
+
+:-: ![](.topwrite/assets/image\_1740540520113.png =807)
+
+### Account Registration Phone Number
+
+The account registration phone number is the phone number you provided when creating the account and adding the first user. The initial account phone number is the same as the phone number of the first user under the account. Account administrators can change the registration phone number in the Management Center. Keep your registration phone number safe — in Singdata products, each registration phone number corresponds to only one account, and it is the sole credential for account recovery.
+
+:-: ![](.topwrite/assets/image\_1739330026163.png =806)
+
+^ ^
+
+## Account Name and Identifiers
+
+### Why You Need an Account Name
+
+* **Global uniqueness**: The account name uniquely identifies your account within the global service network of Singdata Lakehouse.
+* **Security control**: When enabling account security policies and third-party application integrations, the account name is required for access or interaction.
+
+### Common Use Cases for the Account Name
+
+The Lakehouse account name is primarily used in the following scenarios:
+
+**1. Logging into the Lakehouse Web Interface**
+
+When logging into the Lakehouse Management Center or web interface, you need to enter the correct account URL (`<your_account_name>.accounts.singdata.com`) in your browser.
+
+^
+
+### Why You Need a Service Instance Name
+
+* **Global uniqueness**: The instance name uniquely identifies your service instance within the global service network of Singdata Lakehouse. The service name includes region information, enabling direct interaction with the Lakehouse service in that region and simplifying the access path.
+* **Security control**: When enabling network security policies and using third-party clients to access Lakehouse, the service name is required for access or interaction.
+* **Resource linking**: When using features such as data sharing, you need to explicitly specify the service instance name of the target or source account.
+
+### Common Use Cases for the Service Instance Name
+
+**1. Lakehouse CLI / Other Clients / Drivers**
+
+When connecting to Lakehouse using the CLI, JDBC driver, Python/R/Java clients, or third-party tools (such as BI tools), you need to specify the service instance name in the connection configuration.
+
+**2. Third-Party Application and Service Integration**
+
+When external applications (such as data analytics platforms, ETL tools, or cloud storage services) interact with Lakehouse, you need to provide the service instance name to identify the target Lakehouse service.
+
+**3. Data Sharing Operations**
+
+In the Lakehouse "Data Sharing" feature, the service instance name is used to define the scope of operations.
+
+^
+
+## Lakehouse Account URL and Login
+
+### Login URL Format
+
+In Singdata Lakehouse, each account has its own dedicated login URL. The general format is:
+
+https://\<your_account_name\>.accounts.singdata.com
+
+Example:
+
+If your account name is `41nprq1k`, the login URL is:
+
+41nprq1k.accounts.singdata.com
+
+### Logging In with Your Account Name
+
+You can navigate directly to `https://<your_account_name>.accounts.singdata.com` in your browser to reach the login page. On the login page, you need to enter or select the correct account name, along with your username and password. Your account may have one or more users, and you can log in as any of them on this page. You can also retrieve a username or reset a password by entering the user's phone number. When multiple users share the same phone number, you can retrieve all associated usernames via that phone number and select the one you want to log in as.
+
+### Login Flow and Account Recovery
+
+1\. Go to `https://<account_identifier>.accounts.singdata.com` or the unified entry point `https://accounts.singdata.com`.
+
+2\. On the login page, enter or select the correct account name, then enter your **username** and **password**.
+
+3\. If you forget your username or password, you can retrieve them via the user's phone number after entering the account name.
+
+When multiple users share the same phone number, you can retrieve all associated usernames via that number and select the user you want to log in as.
+
+4\. If you forget your account name, you can retrieve it on the login page using the account's registration phone number. One phone number corresponds to only one registered account.
+
+^
+
+## Using Account Identifiers in SQL / Config Files / Third-Party Tools
+
+To accurately specify the target Lakehouse account across different environments, choose the appropriate identifier format based on your scenario:
+
+### Using Identifiers in SQL Statements
+
+When referencing another account in Lakehouse SQL (for example, for data sharing), use the service instance name (`instance_name`).
+
+Example:
+
+`--Specify the sharing instance for data sharing`
+
+`ALTER SHARE share_demo ADD INSTANCE <instance_name>;`
+
+### Using Identifiers in Config Files or Third-Party Tools
+
+* **SQL clients, drivers, or library configurations**
+
+In some SQL clients (such as DBeaver), JDBC drivers, or Python/Java library configuration files, you need to configure connection parameters. For example, when configuring the DBeaver driver:
+
+:-: ![](.topwrite/assets/image\_1740549280083.png =361)
+
+In the JDBC connection string, use the service instance name (`instance_name`), for example:
+
+`jdbc:clickzetta://<your_instance_name>.ap-southeast-1-alicloud.api.clickzetta.com/demo_workspace?username=demo_user&password=DemoPassword&schema=public&virtualCluster=DEFAULT`
+
+When configuring the Python SDK, use the service instance name (`instance_name`):
+
+`from clickzetta import connect`
+
+`# Establish connection`
+
+`conn = connect(username='username',`
+
+`password='password',`
+
+`service='<region\_id>.api.clickzetta.com',`
+
+`instance='your_instance_name',`
+
+`workspace='quickstart_ws',`
+
+`schema='public',`
+
+`vcluster='default')`
+
+^ ^
+
+## Maintaining Account Information
+
+### Viewing the Account Registration Phone Number
+
+When you log in to Singdata with a user that has the account administrator role, you can manage your account in the Management Center. On the "Account Home" page, you can view basic account information and the account login URL. You can also click the "Modify" button next to the registration phone number to change it. Note that on the "Account Center" page you will see two separate phone number fields: "Registration Phone" under "Account Info" — this is the phone number bound to the account and can be used to retrieve the account name; and "Registration Phone" under "User Info" — this is the phone number bound to the currently logged-in user and can be used for MFA verification, username recovery, and password recovery for that user. Be sure to distinguish between the two.
+
+![](.topwrite/assets/image\_1740550879753.png)
+
+
+### Changing the Account Registration Phone Number
+
+To change the account registration phone number, you must be logged in as a user with the account administrator (`account_admin`) role. In the "Account Center", click the modify button next to "Registration Phone" under "Account Info". After verifying the old phone number, you can enter and save the new phone number.
+
+:-: ![](.topwrite/assets/image\_1740551806201.png =765)
+
+:-: ![](.topwrite/assets/image\_1740551835302.png =438)
+
+### Changing the Account Name or Service Instance Name
+
+Both the account name (`account_name`) and the service instance name (`instance_name`) are globally unique identifiers and cannot be modified after they are generated.
+
+^ ^
+
+For further information on managing users under your account, see [Managing Users](account_user_management.md).

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

@@ -0,0 +1,115 @@
+# Account & Billing
+
+Account management covers four areas: users, permissions, funds, and billing. Most operations require the `account_admin` role — if you are just taking over account management, start here.
+
+---
+
+## Managing Basic Account Information
+
+The account name (`account_name`) and service instance name (`instance_name`) are two different identifiers. The former is used for login, and the latter is used for SQL and client connections. Both are automatically generated at registration and **cannot be modified**.
+
+> ⚠️ **Note:** Modifying the account registration phone number requires the account administrator (`account_admin`) role.
+
+| Scenario | Action | Reference |
+|------|------|---------|
+| View account name, login URL, and service instance name | Management Center -> Account Home | [Account & Billing](management.md) |
+| Modify the account registration phone number | Management Center -> Account Center -> Account Info -> Registration Phone -> Modify | [Account & Billing](management.md) |
+| Fill in connection parameters in JDBC / Python SDK | Use `instance_name` as the connection identifier | [Account & Billing](management.md) |
+| Forgot account name | Retrieve via the account registration phone number | [Account & Billing](management.md) |
+
+---
+
+## Managing Users and Permissions
+
+> ⚠️ **Note:** Creating, disabling, and deleting global users and service users, as well as granting or revoking the account administrator role, requires the account administrator (`account_admin`) role.
+>
+> Passwords and phone numbers can only be modified by the user themselves; the account administrator cannot modify them on behalf of others.
+
+| Scenario | Action | Reference |
+|------|------|---------|
+| Add a human user (for interactive login) | User Management -> Create User | [Managing Users](account_user_management.md) |
+| Add a service user (for programmatic access) | User Management -> Create Custom Service User | [Managing Users](account_user_management.md) |
+| Grant or revoke the account administrator role | User Management -> Edit User -> Set as Account Administrator | [Managing Users](account_user_management.md) |
+| Immediately stop all operations for a user | User Management -> Disable User | [Managing Users](account_user_management.md) |
+| Delete a departed employee's account | User Management -> Delete User (note: existing connections are not immediately terminated) | [Managing Users](account_user_management.md) |
+| Change your own password or phone number | Username in the bottom-left corner -> Change Password / User Info | [Managing Users](account_user_management.md) |
+
+---
+
+## Viewing and Topping Up Account Funds
+
+> ⚠️ **Note:** Accessing account funds features requires the account administrator (`account_admin`) role.
+
+Account funds are divided into two categories: **cash account** and **voucher account**, with unified settlement across all regions. When the cash balance reaches 0 and no vouchers are available, continued usage will generate an outstanding balance that must be settled promptly.
+
+| Scenario | Action | Reference |
+|------|------|---------|
+| View current balance and vouchers | Billing Center -> Account Funds | [Account Funds](account-funds.md) |
+| Online top-up (Alipay / WeChat Pay) | Account Funds -> Top Up -> Select Payment Method | [Account Funds](account-funds.md) |
+| Corporate bank transfer top-up | Account Funds -> Top Up -> Corporate Transfer; contact sales after remittance | [Account Funds](account-funds.md) |
+| View top-up and spending history | Account Funds -> Transaction Details | [Account Funds](account-funds.md) |
+| View voucher expiry and usage history | Account Funds -> Vouchers -> View Details | [Account Funds](account-funds.md) |
+
+Top-up method comparison:
+
+| Method | Arrival Time | Notes |
+|---------|---------|------|
+| Alipay / WeChat Pay | Instant | User agreement must be accepted on first top-up |
+| Corporate bank transfer | 3 business days | Contact sales to complete the credit |
+
+---
+
+## Viewing Billing Statements
+
+> ⚠️ **Note:** Accessing billing statement features requires the account administrator (`account_admin`) role.
+
+| Scenario | Action | Reference |
+|------|------|---------|
+| View today's / yesterday's / this month's spending summary | Billing Center -> Billing Statements -> Billing Overview | [Billing Statements](billing.md) |
+| Break down costs by workspace, instance, or time period | Billing Center -> Billing Statements -> Statement Overview -> Filter | [Billing Statements](billing.md) |
+| View daily details (list price, discount, discounted price) | Billing Center -> Billing Statements -> Statement Details | [Billing Statements](billing.md) |
+| Export billing data (XLSX) | Statement Details -> Export Details | [Billing Statements](billing.md) |
+| View historical annual statements | Billing Center -> Billing Statements -> Statement History | [Billing Statements](billing.md) |
+| Understand unit prices and calculation formulas for each billing item | — | [Pricing and Billing](pricing.md) |
+
+Billing update frequency: compute and network items update hourly; storage items update the previous day's data in the early hours of the following day.
+
+---
+
+## Controlling and Optimizing Costs
+
+Singdata Lakehouse charges across three categories: compute (CRU\*hours), storage (GiB/month), and network transfer (GB). The key to reducing costs is minimizing idle runtime of compute clusters and controlling storage and network traffic.
+
+| Scenario | Action | Reference |
+|------|------|---------|
+| Receive alert notifications when costs spike | Data quality rules + monitoring alerts, based on `sys.information_schema.instance_usage` | [Billing Anomaly Alert Configuration Guide](lakehouse_billing_anomaly_alert_configuration_guide.md) |
+| Stable costs with a budget cap | Fixed threshold monitoring approach | [Billing Anomaly Alert Configuration Guide](lakehouse_billing_anomaly_alert_configuration_guide.md) |
+| Fluctuating costs with focus on abnormal increases | Dynamic baseline monitoring approach (compared against historical median) | [Billing Anomaly Alert Configuration Guide](lakehouse_billing_anomaly_alert_configuration_guide.md) |
+| Understand billing principles and pricing for each resource type | — | [Pricing and Billing](pricing.md) |
+
+**Common cost-reduction measures**:
+- Stop compute clusters when not in use (general-purpose and analytical clusters are billed by runtime)
+- Reuse sync-type compute clusters for real-time sync tasks to avoid spinning up a separate cluster per task
+- Reduce public network data export volume (network transfer is only billed for outbound traffic; inbound is free)
+- Set a reasonable Time Travel retention period to avoid long-term storage consumption by multiple data versions
+
+---
+
+## Not Sure Where to Start?
+
+```
+What do you want to do?
+├── Manage basic account information (login URL, registration phone)
+│   └── Requires account_admin → Management Center -> Account Center
+├── Manage users
+│   ├── Add / disable / delete users → Requires account_admin → User Management
+│   └── Change your own password or phone number → No special permission required → Username in bottom-left corner
+├── Account funds
+│   ├── View balance / vouchers → Requires account_admin → Billing Center -> Account Funds
+│   └── Top up → Online (instant) or corporate bank transfer (3 business days)
+├── View billing statements
+│   └── Requires account_admin → Billing Center -> Billing Statements
+└── Control costs
+    ├── Set up alerts → Billing Anomaly Alert Configuration Guide
+    └── Understand billing rules → Pricing and Billing
+```

package/bin/skills/lakehouse-doc-en/references/managing-files-on-volume-with-zettapark.md

@@ -0,0 +1,165 @@
+# Managing Files on Lakehouse Volume with Zettapark
+
+## Overview
+
+Singdata Lakehouse provides unified management of data lake files and data warehouse tables through its abstract storage layer ([Volume](datalake_volume.md), [Schema](om-schema.md), and [Table](om-table.md)) and Python API. This guide demonstrates how to perform file management operations in the data lake, including uploading (PUT), downloading (GET), and listing (LIST) files.
+
+**Key Concepts**:
+
+* **Volume Storage Abstraction**: All data lake storage is mapped to Volume objects.
+  * [External Volume](external_volume.md): Managed by the customer, supporting integration with cloud storage such as Alibaba Cloud OSS, Tencent Cloud COS, AWS S3, and more.
+  * [Internal Volume](internal_volume.md): Managed by Singdata, divided into USER VOLUME and TABLE VOLUME.
+* [Zettapark](zettapark-quick-start.md) **Python API**: Provides a unified interface for file and table integration.
+
+You can get the [source code from the GitHub repository (Jupyter Notebook ipynb file)](https://github.com/yunqiqiliang/clickzetta_quickstart/blob/main/Zettapark/Managing%20Files%20on%20Datalake%20Volume%20with%20Zettapark.ipynb).
+
+## Environment Setup
+
+### Install Dependencies
+
+```bash
+pip install clickzetta_zettapark_python -U -i https://pypi.tuna.tsinghua.edu.cn/simple
+```
+
+### Import Libraries and Create a Session
+
+```python
+from clickzetta.zettapark.session import Session
+import json
+
+```
+
+Load connection parameters from configuration file:
+
+```python
+with open('config.json', 'r') as config_file:
+    config = json.load(config_file)
+
+```
+
+Create session:
+
+```python
+session = Session.builder.configs(config).create()
+print("Session created successfully!")
+```
+
+## File Operations
+
+### Clean Up USER VOLUME
+
+Before starting, clean up the USER VOLUME to ensure a clean environment:
+
+```python
+session.sql("REMOVE USER VOLUME SUBDIRECTORY '/'").show()
+```
+
+### List Files in USER VOLUME
+
+Confirm that the user volume is empty:
+
+```python
+session.sql("LIST USER VOLUME").show(10)
+```
+
+### Upload Files to USER VOLUME
+
+Upload local files to different directories in the user volume based on file type:
+
+```python
+import os
+
+```
+
+Iterate through the local directory and upload files:
+
+```python
+for filename in os.listdir("data/"):
+    if filename.endswith("csv.gz"):
+        file_path = os.path.join("data/", filename)
+        session.file.put(file_path, "volume:user://~/csvgz/")
+    elif filename.endswith(".csv"):
+        file_path = os.path.join("data/", filename)
+        session.file.put(file_path, "volume:user://~/csv/")
+    elif filename.endswith(".json"):
+        file_path = os.path.join("data/", filename)
+        session.file.put(file_path, "volume:user://~/json/")
+    elif filename.endswith(".png"):
+        file_path = os.path.join("data/", filename)
+        session.file.put(file_path, "volume:user://~/png/")
+    elif filename.endswith(".jpg"):
+        file_path = os.path.join("data/", filename)
+        session.file.put(file_path, "volume:user://~/jpg/")
+    elif filename.endswith(".pdf"):
+        file_path = os.path.join("data/", filename)
+        session.file.put(file_path, "volume:user://~/pdf/")
+```
+
+### Verify Upload Results
+
+Confirm that the files were uploaded successfully:
+
+```python
+session.sql("LIST USER VOLUME").show(100)
+```
+
+## View and Download Files
+
+### Download Image Files
+
+Download images from the user volume and display them:
+
+```python
+from PIL import Image
+
+```
+
+Download image to local directory:
+
+```python
+source_path = "volume:user://~/png/unstructured_tables.png"
+dest_path = "tmp/png/"
+session.file.get(source_path, dest_path)
+
+```
+
+Open and display the image:
+
+```python
+try:
+    img = Image.open(dest_path + "unstructured_tables.png")
+    img.show()  # Display the image
+except FileNotFoundError:
+    print(f"Error: File {dest_path} does not exist. Please check the path.")
+except Exception as e:
+    print(f"Unable to open image: {str(e)}")
+```
+
+## Close the Session
+
+After completing operations, close the session to release resources:
+
+```python
+session.close()
+print("Session closed.")
+```
+
+## Summary
+
+Through this guide, you have learned how to:
+
+1. Manage files in the user volume using the Python API.
+2. Upload, download, and list files in the data lake.
+3. View image files and verify operation results.
+
+**Next Steps**:
+
+* Explore Volume usage to achieve seamless integration of files and tables.
+* Try running federated queries on files and tables to experience the advantages of a unified Lakehouse.
+
+## Appendix
+
+* [Get the source code from the GitHub repository](https://github.com/yunqiqiliang/clickzetta_quickstart/blob/main/Zettapark/Managing%20Files%20on%20Datalake%20Volume%20with%20Zettapark.ipynb)
+* [Get more Zettapark Python API examples](https://github.com/yunqiqiliang/clickzetta_quickstart/tree/main/Zettapark-examples/Notebook)
+
+^