@clickzetta/cz-cli-darwin-arm64 0.3.95 → 0.3.100

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

@@ -0,0 +1,268 @@
+# Task Development and Scheduling Configuration
+
+## Overview
+
+"Development" refers to the big data integrated development environment (IDE), providing developers with an efficient, intelligent online working environment. It supports users in task writing, debugging, scheduling configuration, submission and publishing, completing the key processes of big data processing and analysis.
+
+Click "Development" in the left navigation menu to enter the main interface.
+
+## Interface Overview
+
+![](.topwrite/assets/image_1735640592511.png)
+
+| No. | Function                                                        |
+| -- | --------------------------------------------------------- |
+| 1  | Function switch                                                      |
+| 2  | Switch workspace: This section displays the name of the current data development project space and the region you are in. You can click the dropdown icon to switch to other project spaces. |
+| 3  | Development directory tree: The directory tree is used to manage task code in an orderly manner. You can create directory trees according to business needs to manage tasks by category and hierarchy.        |
+| 4  | SQL editing area: The main operation interface for development. Different types of editing areas have different operation interfaces.                         |
+| 5  | Run results: Presents the results after running operations in the SQL editing area.                            |
+
+## Directory Tree
+
+The data development module displays all tasks under the current project in a directory tree format, making it easy to add, delete, modify, and query tasks.
+
+Supported operations on the directory tree:
+
+* **Switch tab**: Switch the type of directory tree below by clicking the tab, i.e., task directory tree or data directory tree.
+
+* **Task directory tree**: Displays all tasks in the current space.
+
+* **Data directory tree**: Displays all data directory trees in the user's region, presented in the workspace-schema-table/view hierarchy.
+
+* **Create**: Create folders and various development tasks by clicking the + button on the directory tree.
+
+* **Development task types**: Real-time sync, offline sync, SQL script, Python script, shell script
+
+* **Filter tasks**: Supports filtering tasks by development task type, submission status, and responsible person.
+
+* **Refresh**: Refresh the current directory tree information.
+
+* **Search tasks**: Search and locate specific tasks by task name or path.
+
+* **Task name**: Fuzzy match keywords with "task name" to return matching file directories or tasks.
+
+* **Path**: Fuzzy match keywords with the task's path to return matching file directories or tasks.
+
+* **Create subdirectory & create subtask**: When hovering over a subdirectory, more icons appear. Click to perform the following operations:
+
+* **Current directory is a folder**: Create any task type, new folder, delete, rename at the current level.
+
+* **Current directory is a task**: Open task, create copy, copy name, rename, move, delete at the current level.
+
+**Operation notes**:
+
+* Create copy: Copy the current task, including its scheduling configuration.
+* Copy name: Copy the current directory name.
+* Rename: Rename the directory name.
+* Move: Move the directory to another directory within the project. If the directory contains subdirectories or tasks, they will be moved together.
+* Delete: Delete the directory.
+* **Task directory tree**: Icons distinguish task types, and colors distinguish online status.
+
+![](.topwrite/assets/43961fb877/97e53c195a68bc32dc20f8d05406a65814f50ebf.png =283)
+
+| Status Legend                                                                              | Description                       |
+| --------------------------------------------------------------------------------- | ------------------------ |
+| ![](.topwrite/assets/43961fb877/cf868103bc526077f03e907734acc40282147b16.png =54) | After task submission, the saved version differs from the submitted version.   |
+| ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =52) | After task submission, the server-side saved version matches the submitted version. |
+| ![](.topwrite/assets/43961fb877/3c8f88221d1cb5096a50fe2f871717264c355624.png =50) | After task submission, click the offline operation.            |
+| ![](.topwrite/assets/43961fb877/4ffcc5e1d5ceda6d460b753cce8e713d4cd1eb58.png =45) | Other status types.                  |
+
+| Icon Legend                                                                              | Description       |
+| --------------------------------------------------------------------------------- | -------- |
+| ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =45) | Real-time sync     |
+| ![](.topwrite/assets/43961fb877/c7a4258cc7c3fffb428b3393d189d5b56d1352b8.png =40) | Offline sync     |
+| ![](.topwrite/assets/43961fb877/b0a4f31a60e860ec4168f2a6aa6c75bd349882ff.png =46) | SQL script    |
+| ![](.topwrite/assets/43961fb877/a34b52a1a518262075162653a0e7bd5efdf8373d.png =43) | Shell script  |
+| ![](.topwrite/assets/43961fb877/9a58c3506c9ddc8c176f67d1224b55de6a08ebb0.png =40) | Python script |
+
+## Task Development Process
+
+The data development module leverages Lakehouse's underlying engine capabilities to provide multiple development types. Users can choose the task type for interactive data development work.
+
+### Create a New Task
+
+Currently, two types of task nodes are supported: data integration and data development.
+
+Click "New" and select the specific development type. A popup will appear. Enter the task name, select the specific directory level where the task should be saved, and then enter the development interface.
+
+![](.topwrite/assets/image_1690523560494.png =210)
+
+### Operation Bar Description
+
+#### Task Tab
+
+![](.topwrite/assets/43961fb877/904d8da4a2bade280ba2901837430ed51d2f5fdd.png)
+
+After clicking the task directory tree on the left or creating a new task node, the task tab will open (or be brought into focus). In the task tab bar, users can perform the following operations:
+
+**New**: Click the "+" button in the tab status bar to quickly create a new task, which is saved by default under the root node of the current space.
+
+**Close tab**: Hover over a tab, and a downward button will appear, allowing batch closing of task tabs.
+
+Tab color status mapping:
+
+| Status Icon | Description   |
+| ---- | ---- |
+| Green   | Run successful |
+| Red   | Run failed |
+| Blue   | Running |
+| Gray   | No run |
+
+#### SQL Function Area
+
+![](.topwrite/assets/43961fb877/d87ab875a66382a674db74e3afeeeb3b722100d6.png)
+
+| No. | Function Name   | Description                                                                                                     |
+| -- | ------ | ------------------------------------------------------------------------------------------------------ |
+| 1  | Save     | Save the task, including the current node code and related configurations.                                                                               |
+| 2  | Format    | Format the written code to make the syntax structure look clean and concise.                                                                                 |
+| 3  | Parameters     | Not yet online.                                                                                                  |
+| 4  | Versions     | Click Versions to view the submitted and saved versions of the current task. Supports code viewing and code rollback between versions.                                                             |
+| 5  | Scheduling     | Click to open a sidebar panel for scheduling configuration. See Scheduling Settings for details.                                                                          |
+| 6  | Submit     | The "Submit" function is only needed for tasks that require scheduled dispatch. After "Submit", the task is published to the Operations Center and runs according to the configured schedule. Before submission, scheduling configuration is required. See Scheduling Settings for details.                  |
+| 7  | Operations     | Click to enter the "Operations" center.                                                                                             |
+| 8  | Task flow tips | Hover over the task flow tips to display the online flowchart for the development task.                                                                       |
+| 9  | Cluster filter   | The "default" shown in the figure indicates the Virtual Cluster used for task execution. Click to switch to another Virtual Cluster. To add a new Virtual Cluster, go to "Compute". |
+| 10 | Run/Stop  | Run/Stop the current node's code. When running SQL code, you can select and run a portion of the code.                                                                   |
+
+#### SQL Editing Area
+
+![](.topwrite/assets/43961fb877/daf1fe91a75052ac12b25b198449827de8d56ff5.png)
+
+* Schema switching: Click the dropdown to switch schemas in the current workspace. The default is "public".
+* Shortcuts: Various capabilities supported in the Studio development editing area. See Others: Common Shortcut Operations for details.
+* SQL editing area: The SQL editor in Studio provides the following features to improve data development and analysis efficiency.
+
+| Feature       | Description                                        |
+| -------- | ------------------------------------------- |
+| Code folding     | Collapse code blocks to reduce reading distractions.                             |
+| Real-time syntax error prompts | Prompt users of syntax errors found during code writing to help avoid mistakes.             |
+| Syntax highlighting     | Use different colors or fonts to highlight keywords and syntax structures in the editor or IDE to enhance readability. |
+| Intelligent completion     | Automatically complete keywords, function names, variable names, etc., in code based on context and known information to improve coding efficiency and precision.   |
+| Partial code execution   | Run only a portion of the code instead of the entire program for quick testing of small code segments or debugging.             |
+
+### Scheduling Settings
+
+After the task has been tested and everything works correctly, if you want to run the task on a scheduled basis, you need to configure the task's scheduling properties. Click the "Scheduling" button in the SQL function area.
+
+#### Basic Information
+
+| Parameter     | Description                                                                                                                                         |
+| ------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| Owner    | Required. Only one member allowed, defaults to the task creator. Can be changed to another workspace member as needed.                                                                                                  |
+| Description     | Optional. Provides a detailed description of the task for future reference and management.                                                                                                                  |
+| Run attributes   | Required. Normal scheduling: Runs according to the user's scheduling rules. Dry-run scheduling: When a task's logic does not need to run temporarily but you don't want to disrupt the data pipeline, set it to dry-run; the task will be marked as successful. Paused: After setting the task to "Paused" and publishing to the Operations Center, the task status is "Paused" and no task instances are generated, but backfill operations are still possible. |
+| Cluster     | Required. Defines the scheduling resource group used when the task is published to production.                                                                                                            |
+| Schema | Required. Defines the prefix schema used when the task runs in production.                                                                                                            |
+| Task priority  | Optional. Sets the scheduling priority for Lakehouse SQL tasks, supporting 10 levels (0-9), where higher numbers mean higher priority.                                                                                          |
+| Parameter configuration   | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: more system built-in parameters will be supported in future versions.                                |
+
+#### Scheduling Time
+
+![](.topwrite/assets/image_1756191463019.png =379)
+
+| Parameter       | Description                                                                                |
+| -------- | --------------------------------------------------------------------------------- |
+| Scheduling cycle     | Daily: Runs every day. Monthly specified day: User selects specific days each month. Weekly specified day: User selects specific days each week.           |
+| Scheduling frequency     | Execute once: Only the start scheduling time needs to be configured. Execute multiple times: Also requires scheduling interval, start time, end time, and exclusion time settings. |
+| Scheduling interval | When executing multiple times, users can customize the interval between each execution, from 1 minute to 12 hours.                                     |
+| Start scheduling time   | The time when daily instances begin executing.                                                                       |
+| End scheduling time   | The time when daily instances stop executing.                                                                       |
+| Exclusion time settings   | No instances will be generated during the specified exclusion time ranges.                                              |
+| Effective time     | The date from which the task takes effect.                                                                        |
+| Expiry time     | The date from which the task expires.                                                                        |
+| Preview scheduling time   | Click to preview the actual run times after configuration.                                                         |
+
+#### Instance Information
+
+Studio supports two instance generation modes: **Effective next day** and **Effective after publishing**.
+
+| Parameter         | Description                                                                                                          |
+| ---------- | ----------------------------------------------------------------------------------------------------------- |
+| Instance generation mode     | Effective after publishing: Instances are generated immediately after publishing and run according to the configured schedule. Effective next day: Instances run on the following day.                                               |
+| Instance retry on error     | Defines whether a task instance can be retried, considering data idempotency. Set as needed. Can retry after success or failure. Cannot retry after success, can retry after failure. Cannot retry after success or failure.                        |
+| Auto retry count     | Custom number of retries.                                                                                                     |
+| Instance timeout duration     | Not enabled / Custom. If a task instance runs longer than the set duration, it will be marked as failed. Changes only apply to new instances after the task is submitted.                                           |
+| Preview scheduling time     | Click to preview the actual run times after configuration.                                                                                   |
+| Parameter configuration       | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: More system built-in parameters will be supported in future versions. |
+| Scheduling wait duration     | If a task instance reaches its scheduled time and waits longer than this setting (still waiting for upstream tasks to finish), the system will mark it as failed to prevent scheduling backlogs.              |
+| Delayed run skip duration | Based on the difference between the task instance's actual start time and the configured scheduled time. If the difference exceeds this setting, the instance is skipped as a dry run and marked as successful.                                        |
+
+#### Scheduling Dependencies
+
+Complex production tasks typically have upstream and downstream dependencies. For example, DWD processing tasks depend on ODS layer tasks. In "Scheduling Dependencies", you can add upstream tasks that the current task depends on. Two methods are supported: parent node's file name, and table name produced by the parent node.
+
+Dependency strategy: Currently supports default strategy, forward dependency, and forward nearest dependency. For specific instance generation methods for each strategy, see [Task Scheduling Dependencies](task_scheduling_dependency.md).
+
+![](.topwrite/assets/image_1756191826292.png =660)
+
+#### Task Output
+
+There are two ways to configure task output information:
+
+Method 1: Automatically generate output table names through code auto-parsing mentioned above.
+
+Method 2: Manually add by searching table names.
+
+![](.topwrite/assets/image_1690523641208.png =437)
+
+For more information about task scheduling, refer to: [Task Scheduling Dependencies](task_scheduling_dependency.md), [Task Scheduling and Instance Execution](f6fc6447ee.md).
+
+### Submit for Publishing
+
+Click the **Submit for Publishing** button in the editor's toolbar to submit the task.
+
+### Operations View
+
+Click to jump to the "Operations" center to view task operations.
+
+## Run Results
+
+### Run History
+
+Run history provides up to 20 recent run result records for the current task tab within 7 days.
+
+![](.topwrite/assets/43961fb877/5356056744906f50b383683a6665b649efc6178d.png)
+
+### Run Results
+
+#### Logs
+
+SQL jobs can be diagnosed based on logs. For details, see [JOB PROFILE](web-job-history.md).
+After clicking to run the task, you can view detailed log information in the log area at the bottom of the page.
+
+Use the expand and collapse buttons to adjust the log display area.
+
+Use the refresh button to force refresh the logs.
+
+![](.topwrite/assets/43961fb877/e3e8ee2c80e29d7dc8bcc52df9c14e68564c9cc3.png)
+
+#### Data
+
+After the task completes, results (such as from SELECT statements) are displayed in the "Data" tab:
+
+![](.topwrite/assets/43961fb877/2b76b47e9714fd6d8ae4276a935f173a971296e1.png)
+
+## Others: Common Shortcut Operations
+
+The following shortcuts are supported in the code editor to improve editing efficiency:
+
+* **Save**
+  * MAC: CMD + s
+  * Windows: Ctrl + s
+* **Comment/Uncomment the current line or code block**
+  * MAC: CMD + /
+  * Windows: Ctrl + /
+* **Cut the current line or code block**
+  * MAC: CMD + x
+  * Windows: Ctrl + x
+* **Copy the current line or code block**
+  * MAC: CMD + c
+  * Windows: Ctrl + c
+* **Paste**
+  * MAC: CMD + v
+  * Windows: Ctrl + v
+* **Batch line operations**
+  * Mac: Shift + Option
+  * Windows: Hold Shift + Alt

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

@@ -0,0 +1,29 @@
+# Obtain Tencent Cloud ARN and ExternalID
+
+When configuring Private Link to access the Lakehouse network, to ensure that the Lakehouse can normally read the endpoint status within your cloud platform account and enhance the security of this access method, please create an independent access control role in the cloud service platform and authorize and add an external ID. The specific operations are as follows.
+
+^
+
+## Tencent Cloud
+
+**How to obtain ARN**:
+
+You need to click "Create Role" on the Tencent Cloud Access Control page (<https://console.cloud.tencent.com/cam/role>) and select the role carrier as: Tencent Cloud Account:
+
+:-: ![](.topwrite/assets/image_1733066596983.png =383)
+
+Select "Other Main Account" for "Account Type";
+
+Fill in the UID displayed on the Lakehouse page in the "Account ID";
+
+Check "Enable Verification" in the "External ID" option, and customize a string of characters for subsequent verification use.
+
+:-: ![](.topwrite/assets/image_1733066790847.png =813)
+
+In the "Configure Role Policy", find and check the "Private Network (VPC) Read-Only Access" policy (Lakehouse needs to call the DescribeVpcEndPoint and DescribeVpcEndPointService interfaces through this role);
+
+:-: ![](.topwrite/assets/image_1733067463964.png =753)
+
+Define the role name and click the "Complete" button to complete the role creation.
+
+:-: ![](.topwrite/assets/image_1733067522805.png =747)

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

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

package/bin/skills/lakehouse-doc-en/references/time-function.md

@@ -0,0 +1,67 @@
+### Date and Time Format Description
+
+#### Overview
+
+When handling and displaying date and time information, we usually need to organize and format this information according to a certain format. This document provides a set of commonly used date and time format symbols, along with their meanings, formats, and examples, to help you better understand and use these symbols.
+
+#### Detailed Explanation of Format Symbols
+
+| Symbol | Description   | Format Example  | Example Value  |
+|--------|---------------|-----------------|----------------|
+| G      | Era           | AD; Anno Domini | AD            |
+| y      | Year          | year            | 2020; 20       |
+| D      | Day of the year | number(3)     | 189            |
+| M      | Month         | month           | 7; 07; Jul; July |
+| d      | Day of the month | number(2)    | 28             |
+| Q      | Quarter       | number/text     | 3; 03; Q3; 3rd quarter |
+| E      | Day of the week | text          | Tue; Tuesday   |
+| a      | AM/PM         | am-pm           | PM             |
+| h      | Hour (12-hour clock) | number(2) | 12             |
+| K      | Hour in AM/PM (0-11) | number(2) | 0              |
+| k      | Hour (24-hour clock) | number(2) | 0              |
+| H      | Hour (24-hour clock) | number(2) | 0              |
+| m      | Minute        | number(2)       | 30             |
+| s      | Second        | number(2)       | 55             |
+| S      | Millisecond/Microsecond | fraction | 978         |
+| V      | Time zone ID  | zone-id         | America/Los_Angeles; Z; -08:30 |
+| z      | Time zone name | zone-name      | Pacific Standard Time; PST |
+| O      | Localized time zone offset | offset-O | GMT+8; GMT+08:00; UTC-08:00; |
+| X      | Time zone offset | offset-X     | Z; -08; -0830; -08:30; -083015; -08:30:15; |
+| Z      | Time zone offset | offset-Z     | +0000; -0800; -08:00; |
+| ‘‘     | Single quote  | literal         | ’              |
+
+#### Examples of Symbol Usage
+
+- Year:
+  - `yyyy`: Four-digit year representation, e.g., 2022.
+  - `yy`: Two-digit year representation, e.g., 22.
+
+- Month:
+  - `M`: Single-digit month representation, e.g., 3, 12.
+  - `MM`: Two-digit month representation, e.g., 03, 12.
+
+- Day of the month:
+  - `d`: Single-digit day of the month representation, e.g., 5, 20.
+  - `dd`: Two-digit day of the month representation, e.g., 05, 20.
+
+- Hour, 24-hour clock:
+  - `H`: Single-digit hour in 24-hour clock representation, e.g., 1, 23.
+  - `HH`: Two-digit hour in 24-hour clock representation, e.g., 01, 23.
+
+- Minute:
+  - `m`: Single-digit minute representation, e.g., 4, 59.
+  - `mm`: Two-digit minute representation, e.g., 04, 59.
+
+- Second:
+  - `s`: Single-digit second representation, e.g., 8, 59.
+  - `ss`: Two-digit second representation, e.g., 08, 59.
+
+- Millisecond/Microsecond:
+  - `S`: Supports 1-9 digits, representing milliseconds (first 3 digits), microseconds (middle 3 digits), and nanoseconds (last 3 digits). Singdata currently only supports microsecond precision, so nanoseconds will be discarded when parsing time strings, and the nanosecond part will be set to zero when generating time strings. If less than 9 digits, precision decreases from right to left.
+
+#### Examples
+
+Here are some examples of date and time formats using the above symbols:
+
+- `yyyy-MM-dd HH:mm:ss.SSSS`: 2022-01-10 10:05:02.1232
+- `yyyy/MM/dd HH:mm:ss.SSSS`: 2022/01/10 10:05:0

package/bin/skills/lakehouse-doc-en/references/time-travel-concept.md

@@ -0,0 +1,175 @@
+# Time Travel Principles
+
+Time Travel is Singdata Lakehouse's historical data access feature, allowing users to query data states at any point in time or recover deleted/modified data.
+
+## What is Time Travel
+
+Time Travel is implemented based on the MVCC (Multi-Version Concurrency Control) mechanism. Every table in Lakehouse maintains multiple historical versions. Each data change (INSERT/UPDATE/DELETE/TRUNCATE) generates a new version, while older versions remain accessible.
+
+```
+Timeline ----------------------------------------------------------->
+
+Version 1: [A, B, C]          <-- Initial create
+             |
+Version 2: [A, B, C, D]       <-- Insert D
+             |
+Version 3: [A, X, C, D]       <-- Update B to X
+             |
+Version 4: [A, X, C]          <-- Delete D
+             |
+     Query any point-in-time snapshot
+```
+
+## How MVCC Works
+
+### Version Generation
+
+Each time a transaction commits, Lakehouse generates a new table version:
+
+| Operation | Version Change |
+|---|---|
+| `INSERT` | New rows added, version number increments |
+| `UPDATE` | Old version marks rows as deleted, new version inserts them |
+| `DELETE` | Rows marked as deleted |
+| `TRUNCATE` | Entire table marked as a new version (empty) |
+
+### Version Query
+
+Use the `TIMESTAMP AS OF` clause to query data at a specified point in time:
+
+```sql
+-- Query data from 1 hour ago
+SELECT * FROM orders TIMESTAMP AS OF CURRENT_TIMESTAMP() - INTERVAL 1 HOUR;
+
+-- Query data at a specific point in time
+SELECT * FROM orders TIMESTAMP AS OF '2024-01-15 10:00:00';
+```
+
+The system finds the most recent version before that point in time and returns a snapshot of that version's data.
+
+## Three Core Capabilities of Time Travel
+
+### 1. Historical Data Query
+
+Query data states at any past point in time, used for:
+- Data comparison analysis (comparing changes at different points in time)
+- Auditing and compliance (tracing historical data states)
+- Troubleshooting (viewing data states before modification)
+
+### 2. Data Recovery (UNDROP)
+
+Recover deleted tables:
+
+```sql
+-- View deletion history
+SHOW TABLES HISTORY;
+
+-- Recover a deleted table
+UNDROP TABLE orders;
+```
+
+**Scope**: Regular tables, dynamic tables, materialized views, table streams
+
+### 3. Data Rollback (RESTORE)
+
+Roll back a table to a specified point in time:
+
+```sql
+-- View version history
+DESC HISTORY orders;
+
+-- Roll back to a specified point in time
+RESTORE TABLE orders TO TIMESTAMP AS OF '2024-01-15 10:00:00';
+```
+
+**Difference from UNDROP**:
+- `UNDROP`: Recovers a dropped table (the table no longer exists)
+- `RESTORE`: Rolls back data in an existing table (the table still exists, but data was modified/deleted by mistake)
+
+## Retention Period
+
+The Time Travel retention period (`data_retention_days`) determines how long historical data remains accessible:
+
+| Configuration | Description |
+|---|---|
+| Default value | 1 day (24 hours) |
+| Value range | 0-90 days |
+| Set to 0 | No historical versions are retained; Time Travel cannot be used |
+| Beyond the period | Historical versions are physically deleted and cannot be recovered |
+
+```sql
+-- Change the retention period to 7 days
+ALTER TABLE orders SET PROPERTIES ('data_retention_days'='7');
+```
+
+## Storage Cost
+
+Time Travel consumes additional storage space to preserve historical versions:
+
+- Storage cost is proportional to data change frequency and retention period
+- Tables that are frequently updated consume more storage under long retention periods
+- It is recommended to set the retention period appropriately based on business needs
+
+## Usage Limitations
+
+| Limitation | Description |
+|---|---|
+| Views not supported | Regular views do not store data and do not support Time Travel |
+| External schemas not supported | Historical versions of external data sources are not managed by Lakehouse |
+| Uncommitted real-time write data | Data written by RealtimeStream that has not been committed does not support Time Travel |
+| Beyond retention period | Historical versions cannot be queried or recovered after physical deletion |
+
+## Typical Scenarios
+
+### Scenario 1: Recovering Accidentally Deleted Data
+
+```sql
+-- Accidentally executed DELETE
+DELETE FROM orders WHERE date < '2024-01-01';
+
+-- View data before deletion
+SELECT COUNT(*) FROM orders TIMESTAMP AS OF '2024-01-15 09:59:00';
+
+-- Recover data
+RESTORE TABLE orders TO TIMESTAMP AS OF '2024-01-15 09:59:00';
+```
+
+### Scenario 2: Recovering an Accidentally Dropped Table
+
+```sql
+-- Accidentally executed DROP TABLE
+DROP TABLE important_data;
+
+-- View deletion record
+SHOW TABLES HISTORY LIKE 'important_data%';
+
+-- Recover the table
+UNDROP TABLE important_data;
+```
+
+### Scenario 3: Tracing Data Changes
+
+```sql
+-- View the version history of a table
+DESC HISTORY orders;
++---------+-------------------------+------------+-------------+----------+-----------+
+| version | time                    | total_rows | total_bytes | user     | operation |
++---------+-------------------------+------------+-------------+----------+-----------+
+| 5       | 2024-01-15 11:00:00.000 | 1000       | 50000       | analyst  | INSERT    |
+| 4       | 2024-01-15 10:30:00.000 | 950        | 47500       | etl_job  | UPDATE    |
+| 3       | 2024-01-15 10:00:00.000 | 900        | 45000       | etl_job  | INSERT    |
++---------+-------------------------+------------+-------------+----------+-----------+
+
+-- Compare data differences between version 3 and version 5
+SELECT * FROM orders TIMESTAMP AS OF '2024-01-15 10:00:00'
+EXCEPT
+SELECT * FROM orders TIMESTAMP AS OF '2024-01-15 11:00:00';
+```
+
+## Related Documentation
+
+- [Time Travel Queries](timetravel.md)
+- [UNDROP TABLE](undrop-table.md)
+- [RESTORE TABLE](restore.md)
+- [DESC HISTORY](desc-history.md)
+- [Data Lifecycle](data-lifecycle.md)

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

@@ -0,0 +1,47 @@
+# Date/Time Types
+
+Singdata Lakehouse supports four time-related types: DATE, TIMESTAMP, TIMESTAMP_NTZ, and INTERVAL.
+
+## Type Comparison
+
+| Type | Precision | Timezone | Use Case |
+|------|-----------|----------|---------|
+| `DATE` | Day | No timezone | Birthdays, date dimensions, fields that only need year/month/day |
+| `TIMESTAMP` | Microsecond | With timezone (stored as UTC, displayed in local time) | Cross-timezone event times, log timestamps |
+| `TIMESTAMP_NTZ` | Microsecond | No timezone (local time stored as-is) | Local business time, scenarios without timezone conversion |
+| `INTERVAL` | Variable | — | Represents a time difference; used for date arithmetic |
+
+Key difference between TIMESTAMP and TIMESTAMP_NTZ (measured):
+
+```SQL
+-- TIMESTAMP: stored as UTC; input 10:30 Beijing time is stored as 02:30 UTC
+SELECT TIMESTAMP '2024-01-15 10:30:00';      -- 2024-01-15T02:30:00.000Z
+
+-- TIMESTAMP_NTZ: stored as-is, no timezone conversion
+SELECT TIMESTAMP_NTZ '2024-01-15 10:30:00'; -- 2024-01-15T10:30:00.000Z
+```
+
+## Common Operation Examples
+
+```SQL
+-- DATE arithmetic
+SELECT DATE_ADD(DATE '2024-01-15', 10);                        -- 2024-01-25
+SELECT DATEDIFF(DATE '2024-02-01', DATE '2024-01-15');         -- 17
+
+-- INTERVAL arithmetic
+SELECT DATE '2024-01-15' + INTERVAL '10' DAY;                 -- 2024-01-25
+SELECT DATE '2024-01-15' + INTERVAL '2' MONTH;                -- 2024-03-15
+
+-- Get current time
+SELECT CURRENT_DATE();       -- current date
+SELECT CURRENT_TIMESTAMP();  -- current timestamp (with timezone)
+```
+
+## Related Documentation
+
+- [DATE](date.md)
+- [TIMESTAMP](timestamp.md)
+- [TIMESTAMP_NTZ](data-types-timestamp-ntz.md)
+- [INTERVAL](interval.md)
+- [Data Types](data-type.md)
+- [Data Type Conversion](datatype-conversion.md)

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

@@ -0,0 +1,73 @@
+# Data Governance
+
+Data governance features help you manage historical versions, lifecycle, and change tracking for your data. The core capability is Time Travel — based on the MVCC mechanism, every data change retains historical versions, allowing you to query the data state at any point in time, recover accidentally deleted data, or roll back unintended operations.
+
+![](/.topwrite/assets/19-time-travel.png)
+
+---
+
+## This Section
+
+| Page | Description |
+|------|------|
+| [Time Travel Overview](timetravel-summary.md) | Time Travel feature introduction, retention period configuration, supported operations |
+| [Time Travel](om-time-travel.md) | Quick examples: query historical data, roll back a table, recover a dropped table |
+| [Time Travel Concept](time-travel-concept.md) | MVCC working mechanism, three core capabilities (query/recover/rollback), typical scenarios |
+| [Data Lifecycle Management](data-lifecycle.md) | Automatically reclaim expired data to control storage costs |
+
+---
+
+## Quick Reference
+
+| What I want to do | Method | Reference |
+|-----------|------|------|
+| Query historical data at a specific point in time | SELECT ... TIMESTAMP AS OF '...' | [TIME TRAVEL](timetravel.md) |
+| View the version history of a table | `DESC HISTORY table_name` | [DESC HISTORY](desc-history.md) |
+| Recover an accidentally dropped table | `UNDROP TABLE table_name` | [UNDROP TABLE](undrop-table.md) |
+| Roll back table data to a historical version | RESTORE TABLE ... TO TIMESTAMP AS OF '...' | [RESTORE TABLE](restore.md) |
+| Set the number of days to retain historical data | ALTER TABLE ... SET PROPERTIES ('data_retention_days'='7') | [Time Travel Overview](timetravel-summary.md) |
+| Automatically clean up expired data | ALTER TABLE ... SET PROPERTIES ('data_lifecycle'='30') | [Data Lifecycle Management](data-lifecycle.md) |
+
+---
+
+## Two Easily Confused Concepts
+
+| Concept | Purpose | Parameter | Default |
+|------|------|------|--------|
+| `data_retention_days` | Controls how long Time Travel can access historical versions; versions older than this are physically deleted | 0–90 days | 1 day |
+| `data_lifecycle` | Controls how long table data survives from its last modification time; data is automatically reclaimed after expiry | Positive integer (days) | Disabled (-1) |
+
+> The two settings work independently: `data_retention_days` governs historical versions; `data_lifecycle` governs the survival time of current data.
+
+---
+
+## Common Scenarios
+
+**Recovering after accidental data deletion**
+
+```sql
+-- Check the row count before the accidental deletion
+SELECT COUNT(*) FROM orders TIMESTAMP AS OF '2024-01-15 09:59:00';
+
+-- Roll the table back to before the deletion
+RESTORE TABLE orders TO TIMESTAMP AS OF '2024-01-15 09:59:00';
+```
+
+**Recovering after an accidental DROP TABLE**
+
+```sql
+-- View deleted tables
+SHOW TABLES HISTORY LIKE 'orders%';
+
+-- Recover the table
+UNDROP TABLE orders;
+```
+
+**Tracing data change history**
+
+```sql
+-- View the version history of a table (operator, time, row count)
+DESC HISTORY orders;
+```
+
+> ⚠️ `TIMESTAMP AS OF` only accepts literal constants; expressions like `NOW() - INTERVAL 1 DAY` are not supported.