@clickzetta/cz-cli-darwin-x64 0.3.89 → 0.3.91

package/bin/skills/clickzetta-dynamic-table/dynamic-table-alter/SKILL.md

@@ -1,160 +1,161 @@
 ---
 name: dynamic-table-alter
 description: |
-  修改 ClickZetta 动态表（Dynamic Table）的结构和属性。支持直接 ALTER 操作（suspend、resume、
-  rename_column、set_comment、set_column_comment、set/unset properties）以及 CREATE OR REPLACE
-  重建操作（修改调度周期、计算集群、加列、减列、改列类型、改 SQL 定义）。当用户说"修改动态表"、
-  "动态表加列"、"改刷新间隔"、"暂停动态表"时触发。
+  Modify the structure and properties of ClickZetta Dynamic Tables. Supports direct ALTER operations
+  (suspend, resume, rename_column, set_comment, set_column_comment, set/unset properties) as well as
+  CREATE OR REPLACE rebuild operations (modify refresh interval, compute cluster, add column, drop column,
+  change column type, change SQL definition). Triggers when the user says "modify dynamic table",
+  "add column to dynamic table", "change refresh interval", or "suspend dynamic table".
 ---
 
-# 动态表修改工作流
+# Dynamic Table Modification Workflow
 
-## 指令
+## Instructions
 
-### 步骤 1：确认动态表存在并获取当前定义
-执行 `SHOW CREATE TABLE schema_name.table_name` 获取动态表当前定义。
-如果不确定是否为动态表，先用 `SHOW TABLES WHERE is_dynamic` 查看列表。
+### Step 1: Confirm the Dynamic Table Exists and Retrieve Its Current Definition
+Execute `SHOW CREATE TABLE schema_name.table_name` to get the current definition of the Dynamic Table.
+If unsure whether it is a Dynamic Table, first use `SHOW TABLES WHERE is_dynamic` to view the list.
 
-### 步骤 2：判断操作类型并选择执行方式
+### Step 2: Determine the Operation Type and Choose the Execution Method
 
-ClickZetta 动态表的修改操作分为两类：
+Dynamic Table modification operations fall into two categories:
 
-**A. 直接 ALTER 操作**（6种，可直接执行）：
+**A. Direct ALTER operations** (6 types, can be executed directly):
 
-1. **suspend** — 暂停调度任务：
+1. **suspend** — Pause the scheduled refresh:
 ```sql
 ALTER DYNAMIC TABLE dt_name SUSPEND;
 ```
 
-2. **resume** — 启动调度任务：
+2. **resume** — Start the scheduled refresh:
 ```sql
 ALTER DYNAMIC TABLE dt_name RESUME;
 ```
 
-3. **set_comment** — 修改表注释：
+3. **set_comment** — Modify the table comment:
 ```sql
 ALTER DYNAMIC TABLE dt_name SET COMMENT 'comment';
 ```
 
-4. **rename_column** — 修改列名：
+4. **rename_column** — Rename a column:
 ```sql
 ALTER DYNAMIC TABLE dt_name RENAME COLUMN old_name TO new_name;
 ```
 
-5. **set_column_comment** — 修改列注释（注意用 CHANGE COLUMN）：
+5. **set_column_comment** — Modify a column comment (note: use CHANGE COLUMN):
 ```sql
 ALTER DYNAMIC TABLE dt_name CHANGE COLUMN column_name COMMENT 'comment';
 ```
 
-6. **set/unset properties** — 修改表属性（目前为保留参数）：
+6. **set/unset properties** — Modify table properties (currently reserved parameters):
 ```sql
--- 设置属性
+-- Set a property
 ALTER DYNAMIC TABLE dt_name SET PROPERTIES('key' = 'value');
--- 删除属性
+-- Remove a property
 ALTER DYNAMIC TABLE dt_name UNSET PROPERTIES('key');
 ```
 
-**B. CREATE OR REPLACE 操作**（6种，需要重建动态表）：
+**B. CREATE OR REPLACE operations** (6 types, require rebuilding the Dynamic Table):
 
-> ⚠️ **以下操作不支持 ALTER 语法**。`ALTER DYNAMIC TABLE ... SET REFRESH INTERVAL` 等语法不存在，会报语法错误。必须使用 `CREATE OR REPLACE DYNAMIC TABLE` 重建。
+> ⚠️ **The following operations do not support ALTER syntax.** Syntax like `ALTER DYNAMIC TABLE ... SET REFRESH INTERVAL` does not exist and will cause a syntax error. You must use `CREATE OR REPLACE DYNAMIC TABLE` to rebuild.
 
-这些操作涉及 SQL 查询逻辑变化，无法通过 ALTER 直接完成：
+These operations involve changes to SQL query logic and cannot be completed via ALTER directly:
 
-7. **修改调度周期** — ❌ 不支持 `ALTER ... SET REFRESH INTERVAL`
-8. **修改计算集群** — ❌ 不支持 `ALTER ... SET VCLUSTER`
-9. **增加列**
-10. **减列**
-11. **修改列类型**
-12. **修改 SQL 定义**
+7. **Modify refresh interval** — ❌ `ALTER ... SET REFRESH INTERVAL` is not supported
+8. **Modify compute cluster** — ❌ `ALTER ... SET VCLUSTER` is not supported
+9. **Add column**
+10. **Drop column**
+11. **Modify column type**
+12. **Modify SQL definition**
 
-### 步骤 3：执行 CREATE OR REPLACE 重建（仅 B 类操作）
+### Step 3: Execute CREATE OR REPLACE Rebuild (Type B operations only)
 
-1. 执行 `SHOW CREATE TABLE schema_name.table_name` 获取原始 DDL
-   > ⚠️ `SHOW CREATE TABLE` 不支持 LIMIT/WHERE 子句，直接执行即可
-2. 解析出：列定义、REFRESH 子句、AS SELECT 子句、COMMENT 等
-3. 根据操作修改对应部分
-4. 执行重建 SQL
+1. Execute `SHOW CREATE TABLE schema_name.table_name` to get the original DDL
+   > ⚠️ `SHOW CREATE TABLE` does not support LIMIT/WHERE clauses; execute it directly
+2. Parse out: column definitions, REFRESH clause, AS SELECT clause, COMMENT, etc.
+3. Modify the relevant parts according to the operation
+4. Execute the rebuild SQL
 
-**关于全量刷新的触发**：
-- 简单的删除列 / 添加列（添加的列只是从源表 SELECT 透传，不参与 JOIN key、GROUP key 等计算）→ **增量刷新**
-- 涉及计算逻辑变化（修改 WHERE 条件、修改聚合逻辑、新增列参与计算等）→ **全量刷新**
-- 兼容类型变更（如 INT → BIGINT）→ **增量刷新**
+**About full refresh triggers:**
+- Simple drop column / add column (where the added column is simply passed through from the source table without participating in JOIN keys, GROUP keys, or other computations) → **incremental refresh**
+- Changes involving computation logic (modifying WHERE conditions, modifying aggregation logic, new column participates in computation, etc.) → **full refresh**
+- Compatible type changes (e.g., INT → BIGINT) → **incremental refresh**
 
-### 步骤 4：验证修改结果
-使用 `DESC TABLE dt_name` 确认修改生效。
+### Step 4: Verify the Modification
+Use `DESC TABLE dt_name` to confirm the modification took effect.
 
 ---
 
-## 示例
+## Examples
 
-### 示例 1：修改调度周期
+### Example 1: Modify Refresh Interval
 
 ```sql
--- 原表
+-- Original table
 CREATE DYNAMIC TABLE dt_name
 REFRESH INTERVAL 10 MINUTE vcluster DEFAULT
 AS SELECT * FROM student02;
 
--- 修改后（改为 20 分钟）
+-- After modification (changed to 20 minutes)
 CREATE OR REPLACE DYNAMIC TABLE dt_name
 REFRESH INTERVAL 20 MINUTE vcluster DEFAULT
 AS SELECT * FROM student02;
 ```
 
-### 示例 2：修改计算集群
+### Example 2: Modify Compute Cluster
 
 ```sql
--- 原表
+-- Original table
 CREATE DYNAMIC TABLE dt_name
 REFRESH INTERVAL 10 MINUTE vcluster DEFAULT
 AS SELECT * FROM student02;
 
--- 修改后（改为 alter_vc 集群）
+-- After modification (changed to alter_vc cluster)
 CREATE OR REPLACE DYNAMIC TABLE dt_name
 REFRESH INTERVAL 10 MINUTE vcluster alter_vc
 AS SELECT * FROM student02;
 ```
 
-### 示例 3：增加列
+### Example 3: Add Column
 
 ```sql
--- 原表
+-- Original table
 CREATE DYNAMIC TABLE change_table (i, j)
 AS SELECT * FROM dy_base_a;
 
--- 添加一列 col（涉及计算逻辑，下次刷新会全量刷新）
+-- Add column col (involves computation logic; next refresh will be a full refresh)
 CREATE OR REPLACE DYNAMIC TABLE change_table (i, j, col)
 AS SELECT i, j, j * 1 FROM dy_base_a;
 
 REFRESH DYNAMIC TABLE change_table;
 ```
 
-### 示例 4：减列
+### Example 4: Drop Column
 
 ```sql
--- 原表有 i, j 两列
+-- Original table has columns i, j
 CREATE DYNAMIC TABLE change_table (i, j)
 AS SELECT * FROM dy_base_a;
 
--- 减列（简单透传，增量刷新）
+-- Drop column (simple pass-through; incremental refresh)
 CREATE OR REPLACE DYNAMIC TABLE change_table (i)
 AS SELECT i FROM dy_base_a;
 ```
 
-### 示例 5：修改 SQL 定义
+### Example 5: Modify SQL Definition
 
 ```sql
--- 修改 WHERE 过滤条件（全量刷新）
+-- Modify WHERE filter condition (full refresh)
 CREATE OR REPLACE DYNAMIC TABLE change_table (i, j)
 AS SELECT * FROM dy_base_a WHERE i > 3;
 
 REFRESH DYNAMIC TABLE change_table;
 ```
 
-### 示例 6：修改列类型
+### Example 6: Modify Column Type
 
 ```sql
--- INT → BIGINT（兼容类型，增量刷新）
+-- INT → BIGINT (compatible type; incremental refresh)
 CREATE OR REPLACE DYNAMIC TABLE change_table (i, j)
 AS SELECT CAST(i AS BIGINT), j FROM dy_base_a;
 
@@ -163,28 +164,28 @@ REFRESH DYNAMIC TABLE change_table;
 
 ---
 
-## 平台特有知识
+## Platform-Specific Knowledge
 
-- **CHANGE COLUMN 语法**：设置列注释用 `CHANGE COLUMN col COMMENT 'xxx'`，不是 `ALTER COLUMN`
-- **RENAME COLUMN 语法**：`RENAME COLUMN old TO new`
-- **DML 限制**：动态表默认不支持 UPDATE/DELETE/MERGE（因隐藏列 MV__KEY），如需 DML 须先执行 `SET cz.sql.dt.allow.dml = true;`
-- **REFRESH 格式**：`REFRESH INTERVAL <N> MINUTE vcluster <name>`，支持 SECOND/MINUTE/HOUR/DAY
-- **CREATE OR REPLACE 风险**：涉及计算逻辑变化时会触发全量刷新，大表可能耗时较长
-- **schema 前缀**：所有 ALTER/CREATE 语句中表名应包含 schema 前缀
-- **列定义可省略类型**：`CREATE DYNAMIC TABLE dt (i, j) AS SELECT ...` 类型由 SELECT 推断
-- **DROP 语法**：必须用 `DROP DYNAMIC TABLE dt_name`，不能用 `DROP TABLE dt_name`（会报错）
-- **UNDROP 语法**：必须用 `UNDROP TABLE dt_name`，不能用 `UNDROP DYNAMIC TABLE dt_name`
-- **DESC 语法**：动态表用 `DESC TABLE dt_name`，不要写 `DESC DYNAMIC TABLE dt_name EXTENDED`（EXTENDED 不支持）
+- **CHANGE COLUMN syntax**: set a column comment with `CHANGE COLUMN col COMMENT 'xxx'`, not `ALTER COLUMN`
+- **RENAME COLUMN syntax**: `RENAME COLUMN old TO new`
+- **DML restrictions**: Dynamic Tables do not support UPDATE/DELETE/MERGE by default (due to hidden column MV__KEY); to use DML, first execute `SET cz.sql.dt.allow.dml = true;`
+- **REFRESH format**: `REFRESH INTERVAL <N> MINUTE vcluster <name>`, supports SECOND/MINUTE/HOUR/DAY
+- **CREATE OR REPLACE risk**: changes involving computation logic will trigger a full refresh, which may take a long time for large tables
+- **Schema prefix**: all ALTER/CREATE statements should include the schema prefix in the table name
+- **Column definitions can omit types**: `CREATE DYNAMIC TABLE dt (i, j) AS SELECT ...` — types are inferred from SELECT
+- **DROP syntax**: must use `DROP DYNAMIC TABLE dt_name`; `DROP TABLE dt_name` will cause an error
+- **UNDROP syntax**: must use `UNDROP TABLE dt_name`; `UNDROP DYNAMIC TABLE dt_name` is not supported
+- **DESC syntax**: use `DESC TABLE dt_name` for Dynamic Tables; do not write `DESC DYNAMIC TABLE dt_name EXTENDED` (EXTENDED is not supported)
 
-## 故障排除
+## Troubleshooting
 
-| 错误 | 原因 | 解决方案 |
+| Error | Cause | Solution |
 |---|---|---|
-| ALTER 报 "Syntax error at or near 'REFRESH'" | `ALTER ... SET REFRESH INTERVAL` 语法不存在 | 使用 `CREATE OR REPLACE DYNAMIC TABLE ... REFRESH INTERVAL ...` 重建 |
-| ALTER 报 "unsupported operation" | 尝试对动态表执行 B 类操作的 ALTER 语法 | 使用 CREATE OR REPLACE 重建 |
-| `DROP TABLE dt_name` 报错 | 动态表必须用 `DROP DYNAMIC TABLE` | 改为 `DROP DYNAMIC TABLE dt_name` |
-| `UNDROP DYNAMIC TABLE` 报错 | UNDROP 不支持 DYNAMIC TABLE 关键字 | 改为 `UNDROP TABLE dt_name` |
-| `DESC DYNAMIC TABLE ... EXTENDED` 报错 | 不支持 EXTENDED 参数 | 改为 `DESC TABLE dt_name`（不加 EXTENDED） |
-| UPDATE/DELETE 报 "MV__KEY" 相关错误 | 动态表有隐藏列 MV__KEY，默认禁止 DML | 先执行 `SET cz.sql.dt.allow.dml = true;` |
-| CREATE OR REPLACE 后数据为空 | AS SELECT 子句引用的源表或列不正确 | 先验证 SELECT 子句是否返回数据 |
-| CREATE OR REPLACE 后全量刷新 | 新增列参与了计算逻辑（JOIN key、GROUP key 等） | 预期行为，等待全量刷新完成 |
+| ALTER reports "Syntax error at or near 'REFRESH'" | `ALTER ... SET REFRESH INTERVAL` syntax does not exist | Use `CREATE OR REPLACE DYNAMIC TABLE ... REFRESH INTERVAL ...` to rebuild |
+| ALTER reports "unsupported operation" | Attempted a Type B ALTER operation on a Dynamic Table | Use CREATE OR REPLACE to rebuild |
+| `DROP TABLE dt_name` fails | Dynamic Tables must use `DROP DYNAMIC TABLE` | Change to `DROP DYNAMIC TABLE dt_name` |
+| `UNDROP DYNAMIC TABLE` fails | UNDROP does not support the DYNAMIC TABLE keyword | Change to `UNDROP TABLE dt_name` |
+| `DESC DYNAMIC TABLE ... EXTENDED` fails | EXTENDED parameter is not supported | Change to `DESC TABLE dt_name` (without EXTENDED) |
+| UPDATE/DELETE reports "MV__KEY" related error | Dynamic Tables have a hidden column MV__KEY; DML is disabled by default | First execute `SET cz.sql.dt.allow.dml = true;` |
+| Data is empty after CREATE OR REPLACE | The AS SELECT clause references an incorrect source table or column | Verify that the SELECT clause returns data first |
+| Full refresh triggered after CREATE OR REPLACE | The new column participates in computation logic (JOIN key, GROUP key, etc.) | Expected behavior; wait for the full refresh to complete |

package/bin/skills/clickzetta-dynamic-table/sql-to-dt/SKILL.md

@@ -1,27 +1,27 @@
 ---
 name: sql-to-dt
-description: 将 Hive/Spark 等任意批处理系统的 CREATE TABLE DDL + INSERT OVERWRITE SQL 自动转换为 Dynamic Table DDL 及配套文件（refresh、prev_refresh、backfill）。当用户提供 DDL 和 INSERT OVERWRITE 要求转换为 DT 时触发，或用户说"创建动态表"时主动引导提供输入。Triggers on: "转换DT", "sql to dt", "convert to dynamic table", "INSERT OVERWRITE 转 DT", "DDL 转换", "创建动态表"
+description: Automatically converts CREATE TABLE DDL + INSERT OVERWRITE SQL from Hive/Spark or any batch processing system into Dynamic Table DDL and companion files (refresh, prev_refresh, backfill). Triggers when the user provides a DDL and INSERT OVERWRITE and requests conversion to DT, or when the user says "create dynamic table" and should be proactively guided to provide input. Triggers on: "convert to DT", "sql to dt", "convert to dynamic table", "INSERT OVERWRITE to DT", "DDL conversion", "create dynamic table"
 ---
 
-# SQL → Dynamic Table 自动转换
+# SQL → Dynamic Table Automatic Conversion
 
-将 Hive/Spark 等任意批处理系统的 ETL SQL（CREATE TABLE + INSERT OVERWRITE）转换为 Dynamic Table DDL 及配套运维文件。
+Converts ETL SQL (CREATE TABLE + INSERT OVERWRITE) from Hive/Spark or any batch processing system into Dynamic Table DDL and companion operation files.
 
-## 使用方式
+## Usage
 
-提供以下输入：
-1. CREATE TABLE DDL（表结构定义）
-2. INSERT OVERWRITE SQL（ETL 查询逻辑）
+Provide the following inputs:
+1. CREATE TABLE DDL (table structure definition)
+2. INSERT OVERWRITE SQL (ETL query logic)
 
-转换工具会自动完成：占位符替换、自引用检测、核心转换、列校验、配套文件生成、转换后改进建议。
+The conversion tool will automatically handle: placeholder replacement, self-reference detection, core conversion, column validation, companion file generation, and post-conversion improvement suggestions.
 
-详细工作流参见 #[[file:references/sql2dt-workflow.md]]
+For the detailed workflow, see #[[file:references/sql2dt-workflow.md]]
 
 ## references/
 
-- **sql2dt-workflow.md** — 完整转换工作流（6 步：预处理、占位符替换、自引用检测、核心转换、列校验、配套文件生成）
-- **sql2dt-conversion-rules.md** — 核心 DDL 转换规则（解析 DDL、解析 INSERT、组装 DT DDL、静态分区注入）
-- **sql2dt-placeholder-rules.md** — 占位符替换规则（${var} → SESSION_CONFIGS()）
-- **sql2dt-self-reference-rules.md** — 自引用表转换规则
-- **sql2dt-column-validation-rules.md** — 列校验规则（schema 列数 = SELECT 列数）
-- **sql2dt-refresh-rules.md** — Refresh 与调度文件生成规则
+- **sql2dt-workflow.md** — Complete conversion workflow (6 steps: pre-processing, placeholder replacement, self-reference detection, core conversion, column validation, companion file generation)
+- **sql2dt-conversion-rules.md** — Core DDL conversion rules (parse DDL, parse INSERT, assemble DT DDL, static partition injection)
+- **sql2dt-placeholder-rules.md** — Placeholder replacement rules (${var} → SESSION_CONFIGS())
+- **sql2dt-self-reference-rules.md** — Self-referencing table conversion rules
+- **sql2dt-column-validation-rules.md** — Column validation rules (schema column count = SELECT column count)
+- **sql2dt-refresh-rules.md** — Refresh and scheduling file generation rules

package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-column-validation-rules.md

@@ -1,118 +1,118 @@
-# Dynamic Table 列校验与一致性规则
+# Dynamic Table Column Validation and Consistency Rules
 
-你是一个 SQL 转换专家。在生成 Dynamic Table DDL 后，需要校验 schema 定义的列与 SELECT 查询产出的列是否一致。
+You are a SQL conversion expert. After generating the Dynamic Table DDL, you need to validate whether the columns defined in the schema match the columns produced by the SELECT query.
 
-## 列数校验（必须通过）
+## Column Count Validation (Must Pass)
 
-### 规则
+### Rule
 
-生成的 DDL 中，括号内定义的列数必须等于 AS 后面 SELECT 查询产出的列数。
+The number of columns defined in the parentheses of the generated DDL must equal the number of columns produced by the SELECT query after AS.
 
 ```sql
 CREATE OR REPLACE DYNAMIC TABLE t (
     col1 BIGINT,    -- 1
     col2 STRING,    -- 2
-    dt STRING       -- 3  → schema 列数 = 3
+    dt STRING       -- 3  → schema column count = 3
 )
 AS
-SELECT col1, col2, '2024-01-01' AS dt  -- → SELECT 列数 = 3 ✓
+SELECT col1, col2, '2024-01-01' AS dt  -- → SELECT column count = 3 ✓
 FROM source;
 ```
 
-### SELECT 列数计算
+### Counting SELECT Columns
 
-1. 找到 AS 后面的 SELECT 子句
-2. 找到顶层 FROM（不在子查询/括号内的 FROM）
-3. 计算 SELECT 和 FROM 之间的顶层逗号数 + 1 = 列数
-4. 顶层逗号：不在括号 `()`、方括号 `[]`、引号 `''`/`""` 内的逗号
+1. Find the SELECT clause after AS
+2. Find the top-level FROM (not inside a subquery/parentheses)
+3. Count top-level commas between SELECT and FROM + 1 = column count
+4. Top-level commas: commas not inside parentheses `()`, square brackets `[]`, or quotes `''`/`""`
 
-### UNION ALL 的列数
+### Column Count for UNION ALL
 
-取第一个分支的列数（所有分支列数应一致）。
+Use the column count of the first branch (all branches should have the same column count).
 
-### 校验失败
+### Validation Failure
 
-如果 schema 列数 ≠ SELECT 列数，转换失败，报错：
+If schema column count ≠ SELECT column count, conversion fails with error:
 ```
-Schema列数(N) != SELECT列数(M)
+Schema column count (N) != SELECT column count (M)
 ```
 
-## 列名校验（可选）
+## Column Name Validation (Optional)
 
-### 规则
+### Rule
 
-逐位对比 schema 中的列名与 SELECT 中推断出的别名。建议在列数校验通过后，如果 SELECT 中大部分列都有明确别名（AS 或裸标识符），开启列名校验做二次确认。
+Compare schema column names against inferred aliases from SELECT, position by position. Recommended to enable after column count validation passes, if most columns in SELECT have explicit aliases (AS or bare identifiers).
 
-### SELECT 列别名推断
+### Inferring SELECT Column Aliases
 
-按优先级从高到低：
+In order of priority from high to low:
 
-1. **AS 别名**：`expression AS alias` → 别名为 `alias`
-2. **末尾标识符**：`table.column` → 别名为 `column`
-3. **裸标识符**：`column_name` → 别名为 `column_name`
-4. **无法推断**：`func(a, b)` 没有 AS → 标记为 `<expr>`，跳过校验
+1. **AS alias**: `expression AS alias` → alias is `alias`
+2. **Trailing identifier**: `table.column` → alias is `column`
+3. **Bare identifier**: `column_name` → alias is `column_name`
+4. **Cannot infer**: `func(a, b)` without AS → mark as `<expr>`, skip validation
 
-### 对比规则
+### Comparison Rules
 
-- 逐位对比（第1列对第1列，第2列对第2列...）
-- 如果某位是 `<expr>`（无法推断），跳过该位
-- 对比不区分大小写
-- 不匹配时报错并列出具体不对齐的列
+- Compare position by position (1st column vs 1st column, 2nd vs 2nd, ...)
+- If a position is `<expr>` (cannot infer), skip that position
+- Comparison is case-insensitive
+- On mismatch, report error and list the specific misaligned columns
 
-## 静态分区注入后的列数
+## Column Count After Static Partition Injection
 
-注入静态分区列后，SELECT 列数会增加。校验应在注入后进行。
+After injecting static partition columns, the SELECT column count increases. Validation should be performed after injection.
 
-### 避免重复注入
+### Avoid Duplicate Injection
 
-在注入前检查 SELECT 中是否已包含该分区列：
+Before injection, check whether SELECT already contains the partition column:
 
-1. 解析 SELECT 中每个表达式的最终别名
-2. 如果别名（不区分大小写）与分区列名匹配 → 该列已存在，跳过注入
-3. 只注入 SELECT 中不存在的分区列
+1. Parse the final alias of each expression in SELECT
+2. If the alias (case-insensitive) matches the partition column name → the column already exists; skip injection
+3. Only inject partition columns not already present in SELECT
 
-## UNION ALL 一致性
+## UNION ALL Consistency
 
-### 分支列数一致性
+### Branch Column Count Consistency
 
-所有 UNION ALL 分支的列数必须相同。如果不一致，记录警告：
+All UNION ALL branches must have the same column count. If inconsistent, record a warning:
 ```
-UNION分支列数不一致: [12, 13, 12]
+UNION branch column counts are inconsistent: [12, 13, 12]
 ```
 
-### 注入后复核
+### Post-injection Recheck
 
-静态分区注入后，再次检查各分支列数是否一致：
+After static partition injection, recheck whether all branch column counts are consistent:
 ```
-注入后UNION各分支列数: [13, 13, 13]
+UNION branch column counts after injection: [13, 13, 13]
 ```
 
-## 重复别名检测
+## Duplicate Alias Detection
 
-如果 SELECT 中有重复的列别名，记录警告：
+If SELECT contains duplicate column aliases, record a warning:
 ```
-检测到重复列别名: ['dt']
+Duplicate column aliases detected: ['dt']
 ```
 
-重复别名可能导致：
-- 列数看起来正确但实际语义错误
-- 下游查询引用歧义
+Duplicate aliases may cause:
+- Column count appears correct but actual semantics are wrong
+- Ambiguous references in downstream queries
 
-## 缺失分区列检测
+## Missing Partition Column Detection
 
-如果 SELECT 中缺少某些分区列（注入前），记录信息：
+If SELECT is missing some partition columns (before injection), record information:
 ```
-检测到缺失分区列: ['dt', 'ds']
+Missing partition columns detected: ['dt', 'ds']
 ```
 
-这些列会在注入步骤中被自动添加。
+These columns will be automatically added in the injection step.
 
-## 完整校验流程
+## Complete Validation Flow
 
 ```
-1. 生成 DDL（含静态分区注入）
-2. 提取 schema 列数
-3. 提取 SELECT 列数
-4. 比较列数 → 不等则失败
-5. （可选）逐位对比列名 → 不匹配则失败
+1. Generate DDL (including static partition injection)
+2. Extract schema column count
+3. Extract SELECT column count
+4. Compare column counts → fail if unequal
+5. (Optional) Compare column names position by position → fail if mismatched
 ```