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

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

@@ -0,0 +1,328 @@
+# Data Sharing
+
+## What is Data Sharing
+
+Data sharing is a no-copy data sharing feature provided by Singdata Lakehouse, used for data authorization across accounts or service instances within the same service region. In Singdata Lakehouse, users can share specified tables or views with other accounts in the same service region through the share object, without actually copying the data to other accounts.
+
+Based on the data sharing feature, accounts can conveniently and securely share data and associate it with their own data for computation, fully exploring the value of the data.
+
+The data shared through the share object is secured through permission control, and the data provider can cancel the sharing of specified data at any time through permission control of the share.
+
+The data consumer does not need to pay for the storage resources occupied by the shared data but needs to use their own computing resources to process the shared data. When the shared data changes, the data consumer can immediately obtain the latest data without data synchronization.
+
+:-: ![](.topwrite/assets/image_1704779759719.png =752)
+
+## Typical Application Scenarios
+
+Company A needs to provide its data to its customer, Company B, for use, requiring real-time data updates and avoiding the establishment of high-cost real-time data synchronization links. At this time, Company A can create a share object, authorize the data to be provided to the share object, and designate the share to Company B's service instance in Singdata Lakehouse. Company B can immediately use the data shared by Company A.
+
+## Notes
+
+* Shared data is "read-only," and the consumer is not allowed to modify or delete the data.
+* The workspace that creates the share object determines the range of data objects that can be added to the share object. Adding data objects across workspaces is not supported.
+* A share object can share up to 1000 table or view objects.
+* If you need to share part of the data in a table, it is recommended to create a corresponding view based on the data to be shared and then share the view.
+* The shared data is prohibited from being re-shared by the data consumer to protect the rights of the data provider.
+* Currently, it is not possible to prevent the data consumer from copying the shared data, so the data provider needs to carefully select the range of data to be shared.
+
+## DDL Commands for Data Sharing
+
+[CREATE SHARE](create-share.md)
+
+[ALTER SHARE](alter-share.md)
+
+[GRANT TO SHARE](grant-to-share.md)
+
+[REVOKE FROM SHARE](revoke-from-share.md)
+
+[SHOW SHARES](show-shares.md)
+
+[DESC SHARE](desc-share.md)
+
+[DROP SHARE](drop-share.md)
+
+## Supported Share Data Objects
+
+Currently, the supported share data objects are: table and view objects.
+
+It is supported to use all tables in schema \<schema\_name> and all views in schema \<schema\_name> to add all table and view objects under the specified schema to the share object. This operation includes all table and view objects created in the specified schema in the "future," so please operate with caution.
+
+## Providing Data Sharing Operations
+
+### Web Interface
+
+**1. Create a Share Object**
+
+To ensure data security, the data sharing (share) object must be created by a user with the "instance administrator" (instance\_admin) role. Click "Data Management" - "Data Sharing" in the left menu to enter the data sharing list page.
+
+Click "+ Add Share" to open the new data sharing window:
+
+:-: ![](.topwrite/assets/image_1740742973168.png =563)
+
+1. Fill in the "Share Name" of the data sharing.
+
+2. Select the "Workspace," which is the workspace where the table or view to be shared is located. A data sharing (share) object can only contain data from one workspace.
+
+3. In the data object row, click "Add." Select the table or view to be included in the data sharing, multiple selections are allowed. But please note that tables and views from other data shares cannot be selected, as re-sharing of data is not allowed in the data sharing authorization. Data sharing created using the web interface only supports existing tables and views, and does not support specifying tables or views created in the entire schema in the "future."
+
+4. In the receiving instance row, click "Add." Enter the name of the service instance that needs to receive the data. The service instance name is globally unique in the Lakehouse service. The service consumer user can find their service instance name on the right side of the homepage or in the URL of the service instance and provide it to the sharer for configuration.
+
+:-: ![](.topwrite/assets/image_1740743048351.png =771)
+
+^
+
+*Note*:
+
+1. *To ensure data security with the workspace as the isolation domain, only users with the workspace administrator role can add data objects within their managed workspace to the data sharing (share*).
+2. *The "Create" and "Add Data" operations in the Create Data Share (share) Object dialog are two separate actions. Even if all or some of the data to be shared fails to be added, it will not affect the creation of the share object. If any operation fails, an error message will be returned. You can click on the created data share in the data share list to continue adding data objects or service instances to receive the data*.
+
+**2. Query Created Data Share (share) Objects**
+
+All data share (share) objects created within the current service instance are displayed on the "Data Share" list page. Users with the service instance administrator role (instance\_admin) or workspace administrator role (workspace\_admin) can view the data share (share) object list.
+
+:-: ![](.topwrite/assets/image_1740743171507.png =800)
+
+^
+
+**3. Query Data Share (share) Details**
+
+Click on the specific data share name displayed on the "Data Share" list page to query the detailed information of the data share, including basic information, the service instance receiving the share, and the shared data objects. Users with the service instance administrator role (instance\_admin) or workspace administrator role (workspace\_admin) can view the details of the data share (share) object.
+
+:-: ![](.topwrite/assets/image_1740743139795.png =783)
+
+^
+
+**4. Add/Delete Shared Data Objects**
+
+Users with the workspace administrator role of the space to which the data share belongs can add or delete data objects (table or view) in the data share.
+
+On the data share list page, click the name of the share object to which you want to add data objects to enter the share object details page. Click the "Edit" button, and select the data objects to add or delete in the popup window. Click "OK" to complete the update of the shared data objects. Data from other share objects cannot be added.
+
+The added data objects will immediately be visible to the consumers of the share object and will appear in their data extraction schema.
+
+:-: ![](.topwrite/assets/image_1740743227652.png =813)
+
+**5. Configure Share Targets**
+
+The share object needs to be configured with the name of the service instance (instance\_name) to be shared in order to complete the data sharing. The service instance name needs to be provided by the data consumer.
+
+:-: ![](.topwrite/assets/image_1740743268339.png =797)
+
+^
+
+**6. Delete Share Objects**
+
+Users with the service instance administrator role (instance\_admin) or the workspace administrator role (workspace\_admin) of the space to which the data share belongs can delete data share objects.
+
+In the data share list page or data share details, click the "Delete" button in the "Actions" to complete the deletion of the data share object. Once deleted, the share object cannot be recovered. The data consumer will immediately lose access to the shared data.
+
+### Using SQL Operations
+
+**1. Create Share Objects**
+
+To ensure data security, share objects must be created by users with the "instance administrator" (instance\_admin) role. When creating a share object, the following statement needs to be executed in the workspace where the data is planned to be shared:
+
+```SQL
+CREATE SHARE <share_name>;
+```
+
+***
+
+**2. Add Data Objects to the Share Object**
+
+The created share object initially does not contain any data objects. You need to add the data objects to be shared using the Grant statement. The syntax is:
+
+```SQL
+GRANT select, read metadata ON {TABLE <table_name> | VIEW <view_name>} TO SHARE <share_name>;
+```
+
+Sure, please provide the document chunk you would like to translate.
+
+```SQL
+GRANT select, read metadata ON TABLE share_demo_table TO SHARE share_demo;
+```
+
+You can use the method `all tables in schema` or `all views in schema` to add all current and future table or view objects under the specified schema to the share, for example:
+
+```SQL
+Grant select, read metadata on ALL tables in SCHEMA share_demo_schema TO SHARE share_demo;
+Grant select, read metadata on ALL views in SCHEMA share_demo_schema TO SHARE share_demo;
+```
+
+When adding data objects to be shared to a share object, the user performing the operation must have select (query) and read metadata permissions on the table or view objects involved in the share, and must be able to grant these permissions to others (with grant option). The workspace administrator role (workspace\_admin) naturally has these permissions.
+
+To remove data objects from a share object, you can use the revoke statement:
+
+```SQL
+REVOKE select, read metadata on {TABLE <name> | VIEW <name>} FROM SHARE <share_name>;
+```
+
+Note: When sharing table or view objects, since table or view objects must exist under a schema object, the metadata permissions (read metadata) of that schema will also be automatically added to the share object. When removing table or view objects from the share, the metadata permissions of their respective schema will also be automatically removed.
+
+***
+
+**3. Configure the Share Target**
+
+To complete data sharing, you need to configure the instance name (instance\_name) of the service being shared to the share object. The instance name needs to be provided by the data consumer.
+
+The instance name is globally unique in the Lakehouse service. Data consumer users can find their instance name on the right side of the homepage or in the URL of the service instance and provide it to the sharer for configuration.
+
+:-: ![](.topwrite/assets/image_1740743048351.png =731)
+
+^
+
+The syntax for the data sharer to configure the share target is as follows:
+
+```SQL
+ALTER SHARE <share_name> [ADD | REMOVE] INSTANCE <instance_name>; 
+```
+
+ADD refers to adding, and REMOVE refers to removing. This operation takes effect immediately, allowing you to add or remove target instances for sharing at any time. A share object can be shared with multiple service instances.
+
+After completing the above three steps, the data is successfully shared with the specified service instance.
+
+^
+
+**4. Query Created Share Objects**
+
+You can query the created share objects by executing the `show` command. The syntax is as follows:
+
+```SQL
+SHOW SHARES;
+```
+
+Example of the returned result is as follows:
+
+:-: ![](.topwrite/assets/share_img_showshares.png =803)
+
+Among them:
+
+* provider is the tenant name of the share provider;
+* provider\_instance is the service instance name of the share provider;
+* provider\_workspace is the workspace to which the share belongs;
+* scope is the sharing scope of the share, currently only supports PRIVATE - specifying instance sharing;
+* to\_instance is the name of the service instance to which the share object is specified to be shared, multiple service instance names are separated by commas (,);
+* kind is the type of share, OUTBOUND is the data shared out by the current service instance, INBOUND is the data shared to the current service instance by other service instances.
+
+^
+
+**5. Query the data objects shared by the specified share**
+
+You can execute the following statement to query the data objects granted in the share:
+
+```SQL
+DESC SHARE <share_name>;
+```
+
+Example of return result is as follows:
+
+:-: ![](.topwrite/assets/share_img_descshare.png =798)
+
+^
+
+**6. Delete share object**
+
+You can execute the following command to delete the share object created by the current service instance:
+
+```SQL
+DROP SHARE <share_name>;
+```
+
+share objects cannot be recovered once deleted. Data consumers will immediately lose access to the shared data.
+
+## Operations Using Shared Data
+
+### Web Interface
+
+**1. Query Shared Data**
+
+Users with the service instance administrator (instance\_admin) role or workspace administrator (workspace\_admin) role can view all data share objects shared with the current service instance in the "Shared with Me" tab under the "Data Sharing" menu.
+
+Click on the name of the data share object to view the source, reception time, and the data (table or view) currently included in the data share.
+
+:-: ![](.topwrite/assets/image_1740743502071.png =768)
+
+^
+
+**2. Extract Shared Data to Create Schema**
+
+In the "Shared with Me" list page or the details page of the data share object, click the "Extract" button to extract the data from the share.
+
+:-: ![](.topwrite/assets/image_1740743548069.png =579)
+
+^
+
+When extracting data, it can only be extracted by schema, and extracting individual tables or views is not supported at this time.
+
+:-: ![](.topwrite/assets/image_1740743576678.png =449)
+
+First, you need to select the "source schema," which is the schema data you need to extract from the share. If the data share contains multiple schemas, you need to perform multiple extractions.
+
+Then select the target workspace for data extraction and enter the schema name where the data will be stored. The data extraction operation will create a new schema in the workspace and store the data from the source schema. Note that the schema created will be a "read-only" schema, and no other data objects can be created in this schema.
+
+After completing the above selections and inputs, click "OK" to complete the data extraction.
+
+**3. Use Shared Data**
+
+After completing the data extraction operation, you can see all the table and view objects shared under the schema in the specified created schema. You can perform select queries on these table and view objects or join queries with other tables and views.
+
+Shared data is marked with a special icon in the "Data" column for easy identification.
+
+:-: ![](.topwrite/assets/image_1734493884869.png =279)
+
+### Using SQL Operations
+
+**1. Query Shared Data**
+
+Data consumers can query the shared share objects using the show shares command. The usage and return results are consistent with step 3 of providing data sharing.
+
+Furthermore, you can query which schemas and table objects are included in the shared share using the desc shares command.
+
+^
+
+**2. Use Shared Data to Create Schema**
+
+Data shared through a share needs to create a corresponding schema on the consumer side to be queried and used. The operation statement is as follows:
+
+```SQL
+CREATE SCHEMA <schema_name> FROM SHARE <provider_instance>.<share_name>.<schema_name>;
+```
+
+The `<provider_instance>` and `<share_name>` can be obtained from the query results of the `show shares` command, while `<schema_name>` can be retrieved by specifying the share name using the `desc share <share_name>` command.
+
+The schema name in `Create schema <schema_name>` can be defined freely and does not need to match the schema name in the share.
+
+To execute the above command, the operator must have the permission to create a schema in the workspace where the operation is performed. The workspace administrator role (`workspace_admin`) has this permission by default.
+
+^
+
+**3. Use the Shared Data**
+
+After completing the execution of create schema from share, you can see all the table and view objects shared under the schema in the specified created schema. You can perform select queries on these table and view objects or join queries with other tables and views.
+
+## Permissions of the Share Object
+
+**1. Provider Permissions**
+
+Only users with the service instance administrator (instance\_admin) role can create data sharing (share) objects. The permission points for creating share objects are as follows, and it is not currently supported to use the grant statement to grant share object permissions to other roles or users.
+
+| **Permission Point**                                                 | **Description**                                                                                                                           |
+| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| Create share                                                         | Permission to create share objects.                                                                                                       |
+| Alter share                                                          | Modify share objects, add or remove shared instance names.                                                                                |
+| Drop share                                                           | Delete share instances.                                                                                                                   |
+| Read metadata                                                        | Permissions for show shares and desc share. The desc share can return the objects contained in the share and the granted objectPrivilege. |
+| Grant objectprivilege to share&#xA;Revoke objectprivilege from share | Add or remove data objects to/from the share: &#xA;Grant objectPrivilege to; &#xA;Revoke objectPrivilege from.                            |
+
+^
+
+**2. Consumer Permissions**
+
+Members in the workspace have the use and read metadata permissions for the share object. However, they must have the create schema permission in the workspace to use the data shared in the share to create a schema.
+
+| **Permission Point** | **Description**                                                                       |
+| -------------------- | ------------------------------------------------------------------------------------- |
+| Use                  | Permission to use the share.                                                          |
+| Read metadata        | Permission to query share metadata, allowing execution of Show shares and desc share. |
+
+^

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

@@ -0,0 +1 @@
+^

package/bin/skills/lakehouse-doc-en/references/datasource-config-guide.md

@@ -0,0 +1 @@
+# Data Source Configuration Guide

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

@@ -0,0 +1,93 @@
+# Data Source IP Whitelist Configuration Guide
+
+## Application Scenarios
+
+When the data source is deployed in an intranet environment or has strict security control requirements, it is necessary to configure IP whitelists on the **source database/server**:
+
+1. Allow only the IP segments of the data synchronization service to access the source data.
+2. Prevent unauthorized network access.
+3. Meet the enterprise's network security audit requirements.
+
+## Prerequisites
+
+* Confirm that the target data source supports the IP whitelist mechanism.
+* Obtain the public IP address of the server where the data synchronization service is located.
+* Ensure that you have the necessary permissions to manage the data source.
+
+## Configuration Process
+
+If you encounter errors due to whitelist restrictions while testing data source connectivity or running synchronization tasks, follow the steps outlined in this document.
+
+### Step 1: Obtain the Data Synchronization Service Export IP Address
+
+Based on the cloud service and region where your service is located, obtain the corresponding IP address:
+
+| Service Region          | IP Address                                   |
+| ----------------------- | -------------------------------------------- |
+| Alibaba Cloud·Shanghai  | 47.100.176.72                                |
+| Alibaba Cloud·Singapore | 47.237.31.114                                |
+| Tencent Cloud·Shanghai  | 110.40.220.6, 124.220.91.8, 101.34.216.184   |
+| Tencent Cloud·Beijing   | 101.42.151.242, 101.42.224.202, 43.138.11.31 |
+| Tencent Cloud·Guangzhou | 43.138.226.127, 1.14.203.242, 175.178.164.94 |
+| AWS·Beijing             | 54.223.225.56, 52.80.208.69                  |
+| AWS·Singapore           | 54.251.190.22, 13.250.195.227                |
+
+### Step 2: Configure Whitelist on the Source Database
+
+1. **Log in to the Source Database Management Console**
+   * MySQL: Through security groups or database parameter settings
+   * Oracle: Through the SQLNET.ORA file configuration
+   * SQL Server: Through server firewall settings
+
+2. **Add IP Whitelist Rules**
+   Taking Alibaba Cloud RDS MySQL as an example, here are the detailed steps based on the **Alibaba Cloud Console** interface:
+
+   **Step 1: Log in to the Alibaba Cloud Console**
+   Open your browser and visit the Alibaba Cloud website. Log in with your Alibaba Cloud account.
+
+   **Step 2: Navigate to the RDS Management Console**
+   After logging in, click on the top menu item “**Products & Services**,” then select “**Databases**” > “**Relational Database RDS**.”
+
+   **Step 3: Select the Target RDS Instance**
+   On the RDS console page, locate the RDS instance you want to operate on. Click the instance name to enter the instance details page.
+
+   **Step 4: Access “Whitelist Settings**”
+   On the instance details page, find the “**Security Settings**” in the left menu. Click on the “**Whitelist Settings**” option.
+
+   **Step 5: Add a Whitelist**
+   On the “Whitelist Settings” page, you will see the current whitelist configuration. Click the “**Add Whitelist Group**” button, or directly add the IP address to an existing whitelist group.
+
+   **Step 6: Configure the Whitelist**
+   In the pop-up dialog box, enter a whitelist group name (optional). In the “**Whitelist Content**” field, input the allowed IP addresses or IP segments. You can enter multiple IP addresses or segments, separated by commas. For example: `47.100.176.72`. Then click “**OK**” to complete the addition.
+
+   **Step 7: Save the Whitelist Settings**
+   After adding, click the “**Save**” button at the bottom of the page to save the whitelist settings.
+
+### Step 3: Data Synchronization Validation
+
+1. In the data source configuration, click on the connectivity test. If successful, this usually indicates that the configuration is normal.
+2. As a precaution, create a test synchronization task and run it manually.
+3. Observe whether the task log shows a successful connection.
+4. In case of failure, check the synchronization task logs and database audit logs.
+
+## Notes
+
+The specific configuration methods may vary depending on the data source type (MySQL/Oracle, etc.), so refer to the official documentation of the corresponding data source. If you need to access cloud products, visit the help centers of each cloud product to view the precautions for adding whitelists. Whitelist settings usually take effect immediately, but may also take a few minutes.
+
+## FAQs
+
+### Q1: Still Cannot Connect After Adding IP Whitelist
+
+* Verify the IP address for accuracy (it is recommended to use `curl ifconfig.me` to check the outbound IP).
+* Ensure that the data source firewall has opened the corresponding port.
+* Check whether the whitelist configuration has taken effect (some databases require a restart to take effect).
+
+### Q2: Best Practices for Whitelist Maintenance
+
+1. Create a dedicated access account for the data synchronization service.
+2. Configure access scope based on the principle of least privilege.
+3. Regularly audit the IP addresses in the whitelist.
+4. It is recommended to enhance security by using VPN/dedicated lines.
+5. Do not add `0.0.0.0/0` (allowing access from all IP addresses) to the production environment whitelist unless absolutely necessary.
+
+^

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

@@ -0,0 +1,62 @@
+# Data Source Support Scope
+
+Before using the data synchronization service, to ensure your synchronization needs are met, first confirm whether the data synchronization service covers your required data sources and select the appropriate task type. Currently, the data synchronization service supports the following three sync task types:
+
+1. Single-table offline sync: Applicable to supported data sources, providing offline sync for single-table reads and writes.
+2. Single-table real-time sync: For supported data sources, implementing real-time sync for single-table reads and writes.
+3. Multi-table real-time sync: For supported data sources, providing multi-table functionality with one-time full sync and real-time incremental sync.
+
+The data source types and versions currently supported by each task type are as follows (including but not limited to the following types; please refer to the actual support within the product):
+
+### Offline Sync
+
+| Data Source | Release Level | Offline Single-Table Read | Offline Single-Table Write | Supported Versions |
+| --------------------- | ------- | ---- | ---- | --------------------- |
+| Singdata Lakehouse | GA | Y | Y | - |
+| ADB MySQL              | GA (Beta) | Y     | Y     | 3.x                    |
+| ADB PostgreSQL         | GA (Beta) | Y     | Y     | 6.x                    |
+| AMQP                   | GA (Beta) | Y     | N     | -                      |
+| AutoMQ                 | GA       | Y     | Y     | -                      |
+| ClickHouse | GA | Y | Y | 19.x and above |
+| COS                    | GA       | Y     | Y     | -                      |
+| Databricks             | GA       | Y     | Y     | -                      |
+| DB2                    | GA (Beta) | Y     | Y     | 11.x                   |
+| DM                     | GA (Beta) | Y     | Y     | 8.x                    |
+| Doris                  | GA (Beta) | Y     | Y     | 1.x                    |
+| DynamoDB               | GA       | Y     | Y     | -                      |
+| Elasticsearch          | GA       | Y     | Y     | 7.x                    |
+| Greenplum | GA (Beta) | Y | Y | 5.x and above |
+| HBase | GA | N | Y | 1.4+ |
+| Hive                   | GA       | Y     | Y     | 2.x                    |
+| Hologres               | GA (Beta) | Y     | Y     | -                      |
+| Kafka | GA | Y | Y | 0.8.x, 0.9.x, 0.10.x, 2.x |
+| MaxCompute             | GA       | Y     | N     | -                      |
+| MariaDB                | GA (Beta) | Y     | Y     | -                      |
+| MongoDB | GA | Y | N | 3.4 and above |
+| MySQL                  | GA       | Y     | Y     | 5.x, 8.x                |
+| Oracle                 | GA (Beta) | Y     | Y     | -                      |
+| OSS                    | GA       | Y     | Y     | -                      |
+| PolarDB for MySQL      | GA       | Y     | Y     | -                      |
+| PolarDB for PostgreSQL | GA       | Y     | Y     | -                      |
+| PostgreSQL | GA | Y | Y | 9.4 and above |
+| Redis                  | GA       | N     | Y     | -                      |
+| Redshift               | GA (Beta) | Y     | Y     | -                      |
+| RestApi                | GA       | Y     | N     | -                      |
+| SLS (LogHub)            | GA       | Y     | N     | -                      |
+| SQL Server | GA | Y | Y | 2012 and above |
+| StarRocks              | GA (Beta) | Y     | Y     | 2.5                    |
+| TiDB                   | GA (Beta) | Y     | Y     | -                      |
+
+### Real-Time Sync
+
+| Data Source | Release Level | Real-Time Single-Table Read | Real-Time Multi-Table Read | Real-Time Write | Supported Versions |
+| --------------- | --- | ---- | ---- | ---- | ---- |
+| Singdata Lakehouse | GA | N | N | Y | - |
+| AutoMQ                 | GA   | Y     | N     | N   | -             |
+| Kafka | GA | Y | N | Y | 0.8.x, 0.9.x, 0.10.x, 2.x |
+| MySQL | GA | Y | Y | N | 5.x, 8.x |
+| PolarDB for MySQL      | GA   | Y     | Y     | N   | -         |
+| PolarDB for PostgreSQL | GA   | Y     | Y     | N   | -       |
+| SQL Server | GA | Y | Y | N | SQL Server 2016 Service Pack 1 (SP1) and above |
+
+^

package/bin/skills/lakehouse-doc-en/references/datatype-cast.md

@@ -0,0 +1,89 @@
+# Data Type Conversion
+
+In SQL statements, data type conversion is a common operation. This article will introduce how to perform data type conversion in SQL, as well as related functions and syntax.
+
+## Data Type Conversion Functions
+
+### CAST Function
+
+The CAST function is used to convert a value of one data type to another data type. If the conversion exceeds the range of the target data type, an overflow exception will be raised.
+
+#### Syntax
+```
+CAST(expression AS type)
+```
+Parameter Description:
+
+- expression: Required. The data source to be converted.
+- type: Required. The target data type. Usage is as follows:
+  - `CAST(double AS bigint)`: Converts a DOUBLE data type value to a BIGINT data type.
+  - `CAST(string AS bigint)`: Converts a string to a BIGINT data type. If the string contains a number expressed as an integer, it is directly converted to the BIGINT type. If the string contains a number expressed as a floating point or exponential form, it is first converted to the DOUBLE data type, and then to the BIGINT data type.
+  - `CAST(string AS timestamp)` or `CAST(timestamp AS string)`: Uses the default date format `yyyy-MM-dd HH:mm:ss`.
+
+#### Example
+```
+SELECT CAST(rand() AS INT);
++---------------------+
+| CAST(rand() AS int) |
++---------------------+
+| 0                   |
++---------------------+
+```
+### TRY_CAST Function
+
+The TRY_CAST function is used to convert a value from one data type to another. If the conversion is successful, it returns the converted value; if the conversion fails, it returns NULL.
+
+#### Syntax
+```
+TRY_CAST(expression AS type)
+```
+Parameter Description:
+
+- expression: Required. The expression to be converted.
+- type: Required. The target data type.
+
+#### Example
+```
+SELECT TRY_CAST('123' AS INT);
++------------------------+
+| TRY_CAST('123' AS int) |
++------------------------+
+| 123                    |
++------------------------+
+```
+```
+SELECT TRY_CAST('abc' AS INT);
++------------------------+
+| TRY_CAST('abc' AS int) |
++------------------------+
+| NULL                   |
++------------------------+
+```
+## Conversion Operators
+
+In addition to using functions for data type conversion, you can also use conversion operators.
+
+### Syntax
+```
+expression::type
+```
+- expression: Required. The expression to be converted.
+- type: Required. The target data type.
+
+### Example
+```
+SELECT 123.45::INT;
++------------------+
+| 123.45::int       |
++------------------+
+| 123              |
++------------------+
+```
+```
+SELECT '2021-08-15'::DATE;
++------------------+
+| '2021-08-15'::date |
++------------------+
+| 2021-08-15       |
++------------------+
+```