Copilot commented on code in PR #3380: URL: https://github.com/apache/doris-website/pull/3380#discussion_r2790332601
########## versioned_docs/version-4.x/data-operate/delete/truncate-manual.md: ########## @@ -13,18 +13,15 @@ Use this statement to clear data from a specified table and its partitions. ## Syntax ```sql -TRUNCATE TABLE [db.]tbl [PARTITION(p1, p2, ...)]; +TRUNCATE TABLE [db.]tbl[ PARTITION(p1, p2, ...)] FORCE?; Review Comment: The TRUNCATE syntax line uses `FORCE?` and `tbl[ PARTITION...` formatting, which is inconsistent with the repo’s SQL syntax notation (optional keywords are shown in `[...]`, e.g. `DROP ... [FORCE]`). Consider updating to `TRUNCATE TABLE [db.]tbl [PARTITION(...)] [FORCE];` (and fix spacing around `tbl`/`[PARTITION]`) to avoid confusing users. ########## docs/data-operate/delete/truncate-manual.md: ########## @@ -13,18 +13,15 @@ Use this statement to clear data from a specified table and its partitions. ## Syntax ```sql -TRUNCATE TABLE [db.]tbl [PARTITION(p1, p2, ...)]; +TRUNCATE TABLE [db.]tbl[ PARTITION(p1, p2, ...)] FORCE?; ``` -- This statement clears the data but retains the table or partition structure. - -- Unlike DELETE, TRUNCATE only performs metadata operations, making it faster and not affecting query performance. - -- Data removed by this operation cannot be recovered. - -- The table status must be NORMAL, and there should be no ongoing SCHEMA CHANGE operations. - -- This command may cause ongoing import tasks to fail. +- This statement only clears the data within a table or partition but preserves the table or partition itself. +- Unlike DELETE, this statement can only clear the specified table or partition as a whole and cannot be added with filter conditions. +- Unlike DELETE, truncating data will not affect query performance. +- The data deleted by this operation can be recovered through the RECOVER statement (for a period of time). See [RECOVER](../../sql-manual/sql-statements/recycle/RECOVER) statement for details. If you execute command with FORCE, the data will be deleted directly and cannot be recovered, this operation is generally not recommended. Review Comment: The sentence about FORCE is grammatically awkward and reads like a run-on: “If you execute command with FORCE, ... cannot be recovered, this operation ...”. Consider adding the missing article (“the command”), and splitting into two sentences for clarity. ```suggestion - The data deleted by this operation can be recovered through the RECOVER statement (for a period of time). See [RECOVER](../../sql-manual/sql-statements/recycle/RECOVER) statement for details. If you execute the command with FORCE, the data will be deleted directly and cannot be recovered. This operation is generally not recommended. ``` ########## i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/truncate-manual.md: ########## @@ -11,17 +11,14 @@ ## 语法 ```sql -TRUNCATE TABLE [db.]tbl [PARTITION(p1, p2, ...)]; +TRUNCATE TABLE [db.]tbl[ PARTITION(p1, p2, ...)] FORCE?; Review Comment: 语法行里使用了 `FORCE?`，并且 `tbl[ PARTITION...` 的空格位置也不规范，容易让读者误以为 `?` 是 SQL 语法的一部分。仓库里通常用 `[...]` 表示可选关键字（例如 `DROP ... [FORCE]`）。建议改为 `TRUNCATE TABLE [db.]tbl [PARTITION(...)] [FORCE];` 并统一空格。 ########## i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/delete/truncate-manual.md: ########## @@ -11,17 +11,14 @@ ## 语法 ```sql -TRUNCATE TABLE [db.]tbl [PARTITION(p1, p2, ...)]; +TRUNCATE TABLE [db.]tbl[ PARTITION(p1, p2, ...)] FORCE?; Review Comment: 语法行里使用了 `FORCE?`，并且 `tbl[ PARTITION...` 的空格位置也不规范，容易让读者误以为 `?` 是 SQL 语法的一部分。仓库里通常用 `[...]` 表示可选关键字（例如 `DROP ... [FORCE]`）。建议改为 `TRUNCATE TABLE [db.]tbl [PARTITION(...)] [FORCE];` 并统一空格。 ########## versioned_docs/version-4.x/data-operate/delete/truncate-manual.md: ########## @@ -13,18 +13,15 @@ Use this statement to clear data from a specified table and its partitions. ## Syntax ```sql -TRUNCATE TABLE [db.]tbl [PARTITION(p1, p2, ...)]; +TRUNCATE TABLE [db.]tbl[ PARTITION(p1, p2, ...)] FORCE?; ``` -- This statement clears the data but retains the table or partition structure. - -- Unlike DELETE, TRUNCATE only performs metadata operations, making it faster and not affecting query performance. - -- Data removed by this operation cannot be recovered. - -- The table status must be NORMAL, and there should be no ongoing SCHEMA CHANGE operations. - -- This command may cause ongoing import tasks to fail. +- This statement only clears the data within a table or partition but preserves the table or partition itself. +- Unlike DELETE, this statement can only clear the specified table or partition as a whole and cannot be added with filter conditions. +- Unlike DELETE, truncating data will not affect query performance. +- The data deleted by this operation can be recovered through the RECOVER statement (for a period of time). See [RECOVER](../../sql-manual/sql-statements/recycle/RECOVER) statement for details. If you execute command with FORCE, the data will be deleted directly and cannot be recovered, this operation is generally not recommended. Review Comment: The sentence about FORCE is grammatically awkward and reads like a run-on: “If you execute command with FORCE, ... cannot be recovered, this operation ...”. Consider adding the missing article (“the command”), and splitting into two sentences for clarity. ```suggestion - The data deleted by this operation can be recovered through the RECOVER statement (for a period of time). See [RECOVER](../../sql-manual/sql-statements/recycle/RECOVER) statement for details. If you execute the command with FORCE, the data will be deleted directly and cannot be recovered. This operation is generally not recommended. ``` ########## docs/data-operate/delete/truncate-manual.md: ########## @@ -13,18 +13,15 @@ Use this statement to clear data from a specified table and its partitions. ## Syntax ```sql -TRUNCATE TABLE [db.]tbl [PARTITION(p1, p2, ...)]; +TRUNCATE TABLE [db.]tbl[ PARTITION(p1, p2, ...)] FORCE?; Review Comment: The TRUNCATE syntax line uses `FORCE?` and `tbl[ PARTITION...` formatting, which is inconsistent with the repo’s SQL syntax notation (optional keywords are shown in `[...]`, e.g. `DROP ... [FORCE]`). Consider updating to `TRUNCATE TABLE [db.]tbl [PARTITION(...)] [FORCE];` (and fix spacing around `tbl`/`[PARTITION]`) to avoid confusing users. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
