diff --git a/src/.vuepress/sidebar/V2.0.x/en-Table.ts b/src/.vuepress/sidebar/V2.0.x/en-Table.ts index 24eafca51..2de43f1b0 100644 --- a/src/.vuepress/sidebar/V2.0.x/en-Table.ts +++ b/src/.vuepress/sidebar/V2.0.x/en-Table.ts @@ -75,9 +75,8 @@ export const enSidebar = { text: 'AI Deployment', collapsible: true, children: [ - { text: 'AINode Deployment', link: 'AINode_Deployment_apache' },/* { text: 'AINode Deployment(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode Deployment(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, */ + { text: 'AINode Deployment(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -134,9 +133,9 @@ export const enSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, { text: 'TimeSeries Large Model(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: 'TimeSeries Large Model(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: 'TimeSeries Large Model(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, ], }, { diff --git a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts index 358a9213f..b67724b0d 100644 --- a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts +++ b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts @@ -82,9 +82,8 @@ export const enSidebar = { text: 'AI Deployment', collapsible: true, children: [ - { text: 'AINode Deployment', link: 'AINode_Deployment_apache' },/* { text: 'AINode Deployment(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode Deployment(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, */ + { text: 'AINode Deployment(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -150,9 +149,9 @@ export const enSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, { text: 'TimeSeries Large Model(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: 'TimeSeries Large Model(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: 'TimeSeries Large Model(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, ], }, { diff --git a/src/.vuepress/sidebar/V2.0.x/zh-Table.ts b/src/.vuepress/sidebar/V2.0.x/zh-Table.ts index 1b4e1076f..69c2879c5 100644 --- a/src/.vuepress/sidebar/V2.0.x/zh-Table.ts +++ b/src/.vuepress/sidebar/V2.0.x/zh-Table.ts @@ -75,9 +75,8 @@ export const zhSidebar = { text: 'AI 部署', collapsible: true, children: [ - { text: 'AINode 部署', link: 'AINode_Deployment_apache' },/* { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode 部署(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, */ + { text: 'AINode 部署(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -132,9 +131,9 @@ export const zhSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, { text: '时序大模型(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: '时序大模型(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: '时序大模型(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, ], }, { diff --git a/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts b/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts index a0f2ca023..3e16287af 100644 --- a/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts +++ b/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts @@ -76,9 +76,8 @@ export const zhSidebar = { text: 'AI 部署', collapsible: true, children: [ - { text: 'AINode 部署', link: 'AINode_Deployment_apache' },/* { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode 部署(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, */ + { text: 'AINode 部署(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -141,9 +140,9 @@ export const zhSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, { text: '时序大模型(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: '时序大模型(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: '时序大模型(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, ], }, { diff --git a/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts b/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts index 23f059306..e951a3e6b 100644 --- a/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts +++ b/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts @@ -82,9 +82,8 @@ export const enSidebar = { text: 'AI Deployment', collapsible: true, children: [ - { text: 'AINode Deployment', link: 'AINode_Deployment_timecho' },/* { text: 'AINode Deployment(V2.0.5/6)', link: 'AINode_Deployment_timecho' }, - { text: 'AINode Deployment(V2.0.8)', link: 'AINode_Deployment_Upgrade_timecho' }, */ + { text: 'AINode Deployment(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_timecho' }, ], }, { @@ -162,9 +161,9 @@ export const enSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_timecho' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_timecho' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_timecho' }, { text: 'TimeSeries Large Model(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: 'TimeSeries Large Model(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, + { text: 'TimeSeries Large Model(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, ], }, { diff --git a/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts b/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts index 3f15798a5..c75f266e1 100644 --- a/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts +++ b/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts @@ -89,9 +89,8 @@ export const enSidebar = { text: 'AI Deployment', collapsible: true, children: [ - { text: 'AINode Deployment', link: 'AINode_Deployment_timecho' }, /* { text: 'AINode Deployment(V2.0.5/6)', link: 'AINode_Deployment_timecho' }, - { text: 'AINode Deployment(V2.0.8)', link: 'AINode_Deployment_Upgrade_timecho' }, */ + { text: 'AINode Deployment(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_timecho' }, ], }, { @@ -174,9 +173,9 @@ export const enSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_timecho' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_timecho' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_timecho' }, { text: 'TimeSeries Large Model(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: 'TimeSeries Large Model(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, + { text: 'TimeSeries Large Model(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, ], }, { diff --git a/src/.vuepress/sidebar_timecho/V2.0.x/zh-Table.ts b/src/.vuepress/sidebar_timecho/V2.0.x/zh-Table.ts index 05fbf9c18..3cd633c1e 100644 --- a/src/.vuepress/sidebar_timecho/V2.0.x/zh-Table.ts +++ b/src/.vuepress/sidebar_timecho/V2.0.x/zh-Table.ts @@ -76,9 +76,8 @@ export const zhSidebar = { text: 'AI 部署', collapsible: true, children: [ - { text: 'AINode 部署', link: 'AINode_Deployment_timecho' },/* { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_timecho' }, - { text: 'AINode 部署(V2.0.8)', link: 'AINode_Deployment_Upgrade_timecho' }, */ + { text: 'AINode 部署(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_timecho' }, ], }, { @@ -153,9 +152,9 @@ export const zhSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_timecho' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_timecho' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_timecho' }, { text: '时序大模型(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: '时序大模型(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, + { text: '时序大模型(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, ], }, { diff --git a/src/.vuepress/sidebar_timecho/V2.0.x/zh-Tree.ts b/src/.vuepress/sidebar_timecho/V2.0.x/zh-Tree.ts index 5a75b6c87..92310f783 100644 --- a/src/.vuepress/sidebar_timecho/V2.0.x/zh-Tree.ts +++ b/src/.vuepress/sidebar_timecho/V2.0.x/zh-Tree.ts @@ -77,9 +77,8 @@ export const zhSidebar = { text: 'AI 部署', collapsible: true, children: [ - { text: 'AINode 部署', link: 'AINode_Deployment_timecho' }, - /* { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_timecho' }, - { text: 'AINode 部署(V2.0.8)', link: 'AINode_Deployment_Upgrade_timecho' }, */ + { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_timecho' }, + { text: 'AINode 部署(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_timecho' }, ], }, { @@ -156,9 +155,9 @@ export const zhSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_timecho' }, - { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_timecho' }, + { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_timecho' }, { text: '时序大模型(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: '时序大模型(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, + { text: '时序大模型(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_timecho' }, ], }, { diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 137a44225..e11e3f9a5 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -85,7 +85,7 @@ To ensure the AINode installation package you obtained is complete and correct, ### 2.3 Environment Requirements - Recommended operating environment: Linux, macOS. -- IoTDB Version: >= V2.0.8. +- IoTDB Version: >= V2.0.8-beta. ## 3. Installation, Deployment, and Usage diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md index 41dcd291e..769c49f0a 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md @@ -89,7 +89,7 @@ sha512sum timechodb-2.0.6.1-ainode-bin.zip ### 2.3 Environment Requirements - Recommended operating environment: Linux, macOS. -- TimechoDB Version: >= V2.0.8. +- TimechoDB Version: >= V2.0.8-beta. ## 3. Installation, Deployment, and Usage diff --git a/src/UserGuide/latest-Table/Reference/System-Tables_apache.md b/src/UserGuide/latest-Table/Reference/System-Tables_apache.md index 2aa05d9fd..a67792b56 100644 --- a/src/UserGuide/latest-Table/Reference/System-Tables_apache.md +++ b/src/UserGuide/latest-Table/Reference/System-Tables_apache.md @@ -371,7 +371,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS Table -> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8. +> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8-beta. * Contains information about all models in the database. * The table structure is as follows: @@ -596,7 +596,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS Table -> This system table is available starting from version V 2.0.8 +> This system table is available starting from version V 2.0.8-beta * Contains all connections in the cluster. * The table structure is as follows: @@ -623,7 +623,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT_QUERIES Table -> This system table is available starting from version V 2.0.8 +> This system table is available starting from version V 2.0.8-beta * Contains all queries whose execution end time falls within the range `[now() - query_cost_stat_window, now())`, including currently executing queries. The `query_cost_stat_window` parameter represents the query cost statistics window. Its default value is 0 and can be configured via the `iotdb-system.properties` configuration file. * The table structure is as follows: @@ -654,7 +654,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES_COSTS_HISTOGRAM Table -> This system table is available starting from version V 2.0.8 +> This system table is available starting from version V 2.0.8-beta * Contains a histogram of query execution times within the past `query_cost_stat_window` period (only statistics for completed SQL queries). The `query_cost_stat_window` parameter represents the query cost statistics window. Its default value is 0 and can be configured via the `iotdb-system.properties` configuration file. * The table structure is as follows: diff --git a/src/UserGuide/latest-Table/Reference/System-Tables_timecho.md b/src/UserGuide/latest-Table/Reference/System-Tables_timecho.md index 7bb37e58c..e7b43683a 100644 --- a/src/UserGuide/latest-Table/Reference/System-Tables_timecho.md +++ b/src/UserGuide/latest-Table/Reference/System-Tables_timecho.md @@ -371,7 +371,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS Table -> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8. +> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8-beta. * Contains information about all models in the database. * The table structure is as follows: @@ -596,7 +596,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS Table -> This system table is available starting from version V 2.0.8 +> This system table is available starting from version V 2.0.8-beta * Contains all connections in the cluster. * The table structure is as follows: @@ -623,7 +623,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT_QUERIES Table -> This system table is available starting from version V 2.0.8 +> This system table is available starting from version V 2.0.8-beta * Contains all queries whose execution end time falls within the range `[now() - query_cost_stat_window, now())`, including currently executing queries. The `query_cost_stat_window` parameter represents the query cost statistics window. Its default value is 0 and can be configured via the `iotdb-system.properties` configuration file. * The table structure is as follows: @@ -654,7 +654,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES_COSTS_HISTOGRAM Table -> This system table is available starting from version V 2.0.8 +> This system table is available starting from version V 2.0.8-beta * Contains a histogram of query execution times within the past `query_cost_stat_window` period (only statistics for completed SQL queries). The `query_cost_stat_window` parameter represents the query cost statistics window. Its default value is 0 and can be configured via the `iotdb-system.properties` configuration file. * The table structure is as follows: diff --git a/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md b/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md index 0500f17f0..12ccafa2d 100644 --- a/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md +++ b/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md @@ -229,7 +229,7 @@ IoTDB> SHOW REGIONS **Description**: Returns the RPC addresses and ports of all available DataNodes in the current cluster. Note: A DataNode is considered "available" if it is not in the REMOVING state. -> This feature is supported starting from v2.0.8. +> This feature is supported starting from v2.0.8-beta. **Syntax**: diff --git a/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md b/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md index 00474ffb7..770bcc688 100644 --- a/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md +++ b/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md @@ -43,8 +43,8 @@ The data export tool `export-data.sh/bat` is located in the `tools` directory an |`-end_time` |`--end_time` | The end time of the data to be exported only takes effect when `-sql_dialect` is set to the table type. If `-q` is specified, this parameter will not take effect.| No | - | | `-t` | `--target` | Target directory for the output files. If the path does not exist, it will be created. | ​**Yes** | - | | `-pfn` | `--prefix_file_name` | Prefix for the exported file names. For example, `abc` will generate files like `abc_0.tsfile`, `abc_1.tsfile`. | No | `dump_0.tsfile` | -| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | -| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8)
`Long.MAX_VALUE` (v2.0.8 and later)
(Range: `-1~Long.MAX_VALUE`) | +| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8-beta, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | +| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8-beta)
`Long.MAX_VALUE` (v2.0.8-beta and later)
(Range: `-1~Long.MAX_VALUE`) | | `-help` | `--help` | Display help information. | No | - | ### 2.2 CSV Format diff --git a/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md b/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md index f2c8a7d2a..9e5645b07 100644 --- a/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md +++ b/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md @@ -43,8 +43,8 @@ The data export tool `export-data.sh/bat` is located in the `tools` directory an |`-end_time` |`--end_time` | The end time of the data to be exported only takes effect when `-sql_dialect` is set to the table type. If `-q` is specified, this parameter will not take effect.| No | - | | `-t` | `--target` | Target directory for the output files. If the path does not exist, it will be created. | ​**Yes** | - | | `-pfn` | `--prefix_file_name` | Prefix for the exported file names. For example, `abc` will generate files like `abc_0.tsfile`, `abc_1.tsfile`. | No | `dump_0.tsfile` | -| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | -| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8)
`Long.MAX_VALUE` (v2.0.8 and later)
(Range: `-1~Long.MAX_VALUE`) | +| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8-beta, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | +| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8-beta)
`Long.MAX_VALUE` (v2.0.8-beta and later)
(Range: `-1~Long.MAX_VALUE`) | | `-help` | `--help` | Display help information. | No | - | ### 2.2 CSV Format diff --git a/src/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md b/src/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md index f29a1fa78..00f790aff 100644 --- a/src/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md +++ b/src/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md @@ -31,7 +31,7 @@ Audit logs provide a documented record of database activities. Through the audit * Configurable audit log retention periods using TTL (time-based rolling) and SpaceTL (space-based rolling) * Default encryption storage for audit logs -> Note: This feature is available from version V2.0.8 onwards. +> Note: This feature is available from version V2.0.8-beta onwards. ## 2. Configuration Parameters diff --git a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md index 659e7a5d1..4351cf4fa 100644 --- a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md @@ -341,7 +341,7 @@ IoTDB> SHOW REGIONS **Description**: Returns the RPC addresses and ports of all available DataNodes in the current cluster. Note: A DataNode is considered "available" if it is not in the REMOVING state. -> This feature is supported starting from v2.0.8. +> This feature is supported starting from v2.0.8-beta. **Syntax**: diff --git a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md index 02185325c..27a0b101a 100644 --- a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md +++ b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md @@ -341,7 +341,7 @@ IoTDB> SHOW REGIONS **Description**: Returns the RPC addresses and ports of all available DataNodes in the current cluster. Note: A DataNode is considered "available" if it is not in the REMOVING state. -> This feature is supported starting from v2.0.8. +> This feature is supported starting from v2.0.8-beta. **Syntax**: diff --git a/src/UserGuide/latest/API/Programming-OPC-UA_timecho.md b/src/UserGuide/latest/API/Programming-OPC-UA_timecho.md index 80b5446b9..1af814e5d 100644 --- a/src/UserGuide/latest/API/Programming-OPC-UA_timecho.md +++ b/src/UserGuide/latest/API/Programming-OPC-UA_timecho.md @@ -27,7 +27,7 @@ This document describes two independent operational modes for IoTDB's integratio * **Mode 1: Data Subscription Service (IoTDB as OPC UA Server)**: IoTDB starts an embedded OPC UA server to passively allow external clients (e.g., UAExpert) to connect and subscribe to its internal data. This is the traditional usage. * **Mode 2: Data Push (IoTDB as OPC UA Client)**: IoTDB acts as a client to actively synchronize data and metadata to one or more independently deployed external OPC UA servers. - > Note: This mode is supported starting from V2.0.8. + > Note: This mode is supported starting from V2.0.8-beta. **Note: Modes are mutually exclusive** When the Pipe configuration specifies the `node-urls` parameter (Mode 2), IoTDB will **not** start the embedded OPC UA server (Mode 1). These two modes **cannot be used simultaneously** within the same Pipe. @@ -68,15 +68,15 @@ CREATE PIPE p1 | sink.opcua.tcp.port | OPC UA TCP port | Integer: [0, 65536] | Optional | 12686 | | sink.opcua.https.port | OPC UA HTTPS port | Integer: [0, 65536] | Optional | 8443 | | sink.opcua.security.dir | OPC UA key and certificate directory | String: Path (supports absolute/relative paths) | Optional | 1. `opc_security` folder under IoTDB's DataNode conf directory `/`. 2. User home directory's `iotdb_opc_security` folder `/` if no IoTDB conf directory exists (e.g., when starting DataNode in IDEA) | -| opcua.security-policy | Security policy used for OPC UA connections (case-insensitive). Multiple policies can be configured and separated by commas. After configuring one policy, clients can only connect using that policy. Default implementation supports `None` and `Basic256Sha256`. Should be set to a non-`None` policy by default. `None` policy is only for debugging (convenient but insecure; not recommended for production). Note: Supported since V2.0.8, only for client-server mode. | String (security level increases):`None`,`Basic128Rsa15`,`Basic256`,`Basic256Sha256`,`Aes128_Sha256_RsaOaep`,`Aes256_Sha256_RsaPss` | Optional | `Basic256Sha256,Aes128_Sha256_RsaOaep,Aes256_Sha256_RsaPss` | +| opcua.security-policy | Security policy used for OPC UA connections (case-insensitive). Multiple policies can be configured and separated by commas. After configuring one policy, clients can only connect using that policy. Default implementation supports `None` and `Basic256Sha256`. Should be set to a non-`None` policy by default. `None` policy is only for debugging (convenient but insecure; not recommended for production). Note: Supported since V2.0.8-beta, only for client-server mode. | String (security level increases):`None`,`Basic128Rsa15`,`Basic256`,`Basic256Sha256`,`Aes128_Sha256_RsaOaep`,`Aes256_Sha256_RsaPss` | Optional | `Basic256Sha256,Aes128_Sha256_RsaOaep,Aes256_Sha256_RsaPss` | | sink.opcua.enable-anonymous-access | Whether OPC UA allows anonymous access | Boolean | Optional | true | | sink.user | User (OPC UA allowed user) | String | Optional | root | | sink.password | Password (OPC UA allowed password) | String | Optional | TimechoDB@2021 (Default was 'root' before V2.0.6.x) | -| opcua.with-quality | Whether OPC UA publishes data in value + quality mode. When enabled, system processes data as follows:1. Both value and quality present → Push directly to OPC UA Server.2. Only value present → Quality automatically filled as UNCERTAIN (default, configurable).3. Only quality present → Ignore write (no processing).4. Non-value/quality fields present → Ignore data and log warning (configurable log frequency to avoid high-frequency interference).5. Quality type restriction: Only boolean type supported (true = GOOD, false = BAD).**Note**: Supported since V2.0.8, only for client-server mode | Boolean | Optional | false | -| opcua.value-name | Effective when `with-quality` = true, specifies the name of the value point. **Note**: Supported since V2.0.8, only for client-server mode | String | Optional | value | -| opcua.quality-name | Effective when `with-quality` = true, specifies the name of the quality point. **Note**: Supported since V2.0.8, only for client-server mode | String | Optional | quality | -| opcua.default-quality | When no quality is provided, specify `GOOD`/`UNCERTAIN`/`BAD` via SQL parameter. **Note**: Supported since V2.0.8, only for client-server mode | String: `GOOD`/`UNCERTAIN`/`BAD` | Optional | `UNCERTAIN` | -| opcua.timeout-seconds | Client connection timeout in seconds (effective only when IoTDB acts as client). **Note**: Supported since V2.0.8, only for client-server mode | Long | Optional | 10L | +| opcua.with-quality | Whether OPC UA publishes data in value + quality mode. When enabled, system processes data as follows:1. Both value and quality present → Push directly to OPC UA Server.2. Only value present → Quality automatically filled as UNCERTAIN (default, configurable).3. Only quality present → Ignore write (no processing).4. Non-value/quality fields present → Ignore data and log warning (configurable log frequency to avoid high-frequency interference).5. Quality type restriction: Only boolean type supported (true = GOOD, false = BAD).**Note**: Supported since V2.0.8-beta, only for client-server mode | Boolean | Optional | false | +| opcua.value-name | Effective when `with-quality` = true, specifies the name of the value point. **Note**: Supported since V2.0.8-beta, only for client-server mode | String | Optional | value | +| opcua.quality-name | Effective when `with-quality` = true, specifies the name of the quality point. **Note**: Supported since V2.0.8-beta, only for client-server mode | String | Optional | quality | +| opcua.default-quality | When no quality is provided, specify `GOOD`/`UNCERTAIN`/`BAD` via SQL parameter. **Note**: Supported since V2.0.8-beta, only for client-server mode | String: `GOOD`/`UNCERTAIN`/`BAD` | Optional | `UNCERTAIN` | +| opcua.timeout-seconds | Client connection timeout in seconds (effective only when IoTDB acts as client). **Note**: Supported since V2.0.8-beta, only for client-server mode | Long | Optional | 10L | #### 2.1.3 Example @@ -229,7 +229,7 @@ CREATE PIPE p1 > **Parameter Naming Note**: All parameters support omitting `opcua.` prefix (e.g., `node-urls` and `opcua.node-urls` are equivalent). > -> **Support Note**: All `opcua.` parameters are supported starting from V2.0.8, and only for `client-server` mode. +> **Support Note**: All `opcua.` parameters are supported starting from V2.0.8-beta, and only for `client-server` mode. #### 3.1.3 Example diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 137a44225..e11e3f9a5 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -85,7 +85,7 @@ To ensure the AINode installation package you obtained is complete and correct, ### 2.3 Environment Requirements - Recommended operating environment: Linux, macOS. -- IoTDB Version: >= V2.0.8. +- IoTDB Version: >= V2.0.8-beta. ## 3. Installation, Deployment, and Usage diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md index 41dcd291e..769c49f0a 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md @@ -89,7 +89,7 @@ sha512sum timechodb-2.0.6.1-ainode-bin.zip ### 2.3 Environment Requirements - Recommended operating environment: Linux, macOS. -- TimechoDB Version: >= V2.0.8. +- TimechoDB Version: >= V2.0.8-beta. ## 3. Installation, Deployment, and Usage diff --git a/src/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md b/src/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md index 8e1f0cdfc..932c08135 100644 --- a/src/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md +++ b/src/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md @@ -37,8 +37,8 @@ The data export tool, export-data.sh (Unix/OS X) or export-data.bat (Windows), l | `-pw` | `--password` | Password for authentication. | No | `root` | | `-t` | `--target` | Target directory for the output files. If the path does not exist, it will be created. | ​**Yes** | - | | `-pfn` | `--prefix_file_name` | Prefix for the exported file names. For example, `abc` will generate files like `abc_0.tsfile`, `abc_1.tsfile`. | No | `dump_0.tsfile` | -| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | -| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8)
`Long.MAX_VALUE` (v2.0.8 and later)
(Range: `-1~Long.MAX_VALUE`) | +| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8-beta, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | +| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8-beta)
`Long.MAX_VALUE` (v2.0.8-beta and later)
(Range: `-1~Long.MAX_VALUE`) | | `-help` | `--help` | Display help information. | No | - | ### 2.2 CSV Format diff --git a/src/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md b/src/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md index dd0191367..46b154282 100644 --- a/src/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md +++ b/src/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md @@ -37,8 +37,8 @@ The data export tool, export-data.sh (Unix/OS X) or export-data.bat (Windows), l | `-pw` | `--password` | Password for authentication. | No | `TimechoDB@2021`(Before V2.0.6 it is `root` ) | | `-t` | `--target` | Target directory for the output files. If the path does not exist, it will be created. | ​**Yes** | - | | `-pfn` | `--prefix_file_name` | Prefix for the exported file names. For example, `abc` will generate files like `abc_0.tsfile`, `abc_1.tsfile`. | No | `dump_0.tsfile` | -| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | -| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8)
`Long.MAX_VALUE` (v2.0.8 and later)
(Range: `-1~Long.MAX_VALUE`) | +| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8-beta, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - | +| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8-beta)
`Long.MAX_VALUE` (v2.0.8-beta and later)
(Range: `-1~Long.MAX_VALUE`) | | `-help` | `--help` | Display help information. | No | - | ### 2.2 CSV Format diff --git a/src/UserGuide/latest/User-Manual/Audit-Log_timecho.md b/src/UserGuide/latest/User-Manual/Audit-Log_timecho.md index 89b599690..1a0b7d933 100644 --- a/src/UserGuide/latest/User-Manual/Audit-Log_timecho.md +++ b/src/UserGuide/latest/User-Manual/Audit-Log_timecho.md @@ -30,7 +30,7 @@ Audit logs provide a documented record of database activities. Through the audit * Ability to configure audit log file retention periods using TTL (time-based rolling) and SpaceTL (space-based rolling) * Audit logs are encrypted by default -> Note: This feature is available from version V2.0.8 onwards. +> Note: This feature is available from version V2.0.8-beta onwards. ## 2. Configuration Parameters diff --git a/src/UserGuide/latest/User-Manual/Maintenance-commands.md b/src/UserGuide/latest/User-Manual/Maintenance-commands.md index b6d0988bd..ed58ddf2b 100644 --- a/src/UserGuide/latest/User-Manual/Maintenance-commands.md +++ b/src/UserGuide/latest/User-Manual/Maintenance-commands.md @@ -247,7 +247,7 @@ IoTDB> SHOW REGIONS **Description**: Returns the RPC addresses and ports of all available DataNodes in the current cluster. Note: A DataNode is considered "available" if it is not in the REMOVING state. -> This feature is supported starting from v2.0.8. +> This feature is supported starting from v2.0.8-beta. **Syntax**: diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 7bf4d6d23..67c0278cb 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -87,7 +87,7 @@ b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4 ### 2.3 环境要求 * 建议操作环境: Linux, MacOS； -* IoTDB 版本：>= V 2.0.8； +* IoTDB 版本：>= V 2.0.8-beta； ## 3. 安装部署及使用 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md index cee303d62..167973563 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md @@ -85,7 +85,7 @@ sha512sum timechodb-2.0.6.1-ainode-bin.zip ### 2.3 环境要求 * 建议操作环境: Linux, MacOS； -* TimechoDB 版本：>= V 2.0.8； +* TimechoDB 版本：>= V 2.0.8-beta； ## 3. 安装部署及使用 diff --git a/src/zh/UserGuide/latest-Table/Reference/System-Tables_apache.md b/src/zh/UserGuide/latest-Table/Reference/System-Tables_apache.md index 418b08f66..0b8f5de6b 100644 --- a/src/zh/UserGuide/latest-Table/Reference/System-Tables_apache.md +++ b/src/zh/UserGuide/latest-Table/Reference/System-Tables_apache.md @@ -369,7 +369,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS 表 -> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8 版本开始不再提供 +> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8-beta 版本开始不再提供 * 包含数据库内所有的模型信息 * 表结构如下表所示： @@ -589,7 +589,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS 表 -> 该系统表从 V 2.0.8 版本开始提供 +> 该系统表从 V 2.0.8-beta 版本开始提供 * 包含集群中所有连接。 * 表结构如下表所示： @@ -616,7 +616,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT\_QUERIES 表 -> 该系统表从 V 2.0.8 版本开始提供 +> 该系统表从 V 2.0.8-beta 版本开始提供 * 包含所有执行结束时间在 `[now() - query_cost_stat_window, now())` 范围内的所有查询，也包括当前正在执行的查询。其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： @@ -647,7 +647,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES\_COSTS\_HISTOGRAM 表 -> 该系统表从 V 2.0.8 版本开始提供 +> 该系统表从 V 2.0.8-beta 版本开始提供 * 包含过去 `query_cost_stat_window` 时间内的查询耗时的直方图（仅统计已经执行结束的 SQL），其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： diff --git a/src/zh/UserGuide/latest-Table/Reference/System-Tables_timecho.md b/src/zh/UserGuide/latest-Table/Reference/System-Tables_timecho.md index e13fa2c59..45b71a510 100644 --- a/src/zh/UserGuide/latest-Table/Reference/System-Tables_timecho.md +++ b/src/zh/UserGuide/latest-Table/Reference/System-Tables_timecho.md @@ -369,7 +369,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS 表 -> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8 版本开始不再提供 +> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8-beta 版本开始不再提供 * 包含数据库内所有的模型信息 * 表结构如下表所示： @@ -589,7 +589,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS 表 -> 该系统表从 V 2.0.8 版本开始提供 +> 该系统表从 V 2.0.8-beta 版本开始提供 * 包含集群中所有连接。 * 表结构如下表所示： @@ -616,7 +616,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT\_QUERIES 表 -> 该系统表从 V 2.0.8 版本开始提供 +> 该系统表从 V 2.0.8-beta 版本开始提供 * 包含所有执行结束时间在 `[now() - query_cost_stat_window, now())` 范围内的所有查询，也包括当前正在执行的查询。其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： @@ -647,7 +647,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES\_COSTS\_HISTOGRAM 表 -> 该系统表从 V 2.0.8 版本开始提供 +> 该系统表从 V 2.0.8-beta 版本开始提供 * 包含过去 `query_cost_stat_window` 时间内的查询耗时的直方图（仅统计已经执行结束的 SQL），其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md b/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md index 4793ddd1f..00efaff14 100644 --- a/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md +++ b/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements.md @@ -228,7 +228,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8 起支持该功能 +> V2.0.8-beta 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md index 569da9951..36e4119fc 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md @@ -46,8 +46,8 @@ |-end_time |--end_time | 将要导出的数据的终止时间，只有`-sql_dialect`为 table 类型时生效。如果填写了`-q`，则此参数不生效。| 否 | - | | -t | --target | 指定输出文件的目标文件夹，如果路径不存在新建文件夹 | √ | | | -pfn | --prefix\_file\_name | 指定导出文件的名称。例如：abc,生成的文件是abc\_0.tsfile、abc\_1.tsfile | 否 | dump\_0.tsfile | -| -q | --query | 要执行的查询语句。自 V2.0.8 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | -| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8 之前)
`Long.MAX_VALUE`(V2.0.8 及之后)
范围：`-1~Long.MAX_VALUE` | +| -q | --query | 要执行的查询语句。自 V2.0.8-beta 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | +| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8-beta 之前)
`Long.MAX_VALUE`(V2.0.8-beta 及之后)
范围：`-1~Long.MAX_VALUE` | | -help | --help | 显示帮助信息 | 否 | | ### 2.2 CSV 格式 diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md index e6b5aae19..4c964c0d7 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md @@ -46,8 +46,8 @@ |-end_time |--end_time | 将要导出的数据的终止时间，只有`-sql_dialect`为 table 类型时生效。如果填写了`-q`，则此参数不生效。| 否 | - | | -t | --target | 指定输出文件的目标文件夹，如果路径不存在新建文件夹 | √ | | | -pfn | --prefix\_file\_name | 指定导出文件的名称。例如：abc,生成的文件是abc\_0.tsfile、abc\_1.tsfile | 否 | dump\_0.tsfile | -| -q | --query | 要执行的查询语句。自 V2.0.8 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | -| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8 之前)
`Long.MAX_VALUE`(V2.0.8 及之后)
范围：`-1~Long.MAX_VALUE` | +| -q | --query | 要执行的查询语句。自 V2.0.8-beta 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | +| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8-beta 之前)
`Long.MAX_VALUE`(V2.0.8-beta 及之后)
范围：`-1~Long.MAX_VALUE` | | -help | --help | 显示帮助信息 | 否 | | ### 2.2 CSV 格式 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md b/src/zh/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md index 89d214405..299107e84 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Audit-Log_timecho.md @@ -31,7 +31,7 @@ * 可通过参数设置审计日志文件的存储周期，包括基于 TTL 实现时间滚动和基于 SpaceTL 实现空间滚动。 * 审计日志文件默认加密存储 -> 注意：该功能从 V2.0.8 版本开始提供。 +> 注意：该功能从 V2.0.8-beta 版本开始提供。 ## 2. 配置参数 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md index 8c74bea38..15da30a0c 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md @@ -340,7 +340,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8 起支持该功能 +> V2.0.8-beta 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md index aadcb8b29..41eda769e 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md @@ -340,7 +340,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8 起支持该功能 +> V2.0.8-beta 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/latest/API/Programming-OPC-UA_timecho.md b/src/zh/UserGuide/latest/API/Programming-OPC-UA_timecho.md index cb545a4d1..83f2debae 100644 --- a/src/zh/UserGuide/latest/API/Programming-OPC-UA_timecho.md +++ b/src/zh/UserGuide/latest/API/Programming-OPC-UA_timecho.md @@ -27,7 +27,7 @@ * **模式一：数据订阅服务 (IoTDB 作为 OPC UA 服务器)**：IoTDB 启动内置的 OPC UA 服务器，被动地允许外部客户端（如 UAExpert）连接并订阅其内部数据。这是传统用法。 * **模式二：数据主动推送 (IoTDB 作为 OPC UA 客户端)**：IoTDB 作为客户端，主动将数据和元数据同步到一个或多个独立部署的外部 OPC UA 服务器。 - > 注意：该模式从 V2.0.8 起支持。 + > 注意：该模式从 V2.0.8-beta 起支持。 **注意：模式互斥** @@ -61,22 +61,22 @@ create pipe p1 #### 2.1.2 参数 -| **参数** | **描述** | **取值范围** | **是否必填** | **默认值** | -| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |------------------------------------------------------------------------------------------------------------------------------------------| -------------------- |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| sink | OPC UA SINK | String: opc-ua-sink | 必填 | | -| sink.opcua.model | OPC UA 使用的模式 | String: client-server / pub-sub | 选填 | client-server | -| sink.opcua.tcp.port | OPC UA 的 TCP 端口 | Integer: [0, 65536] | 选填 | 12686 | -| sink.opcua.https.port | OPC UA 的 HTTPS 端口 | Integer: [0, 65536] | 选填 | 8443 | -| sink.opcua.security.dir | OPC UA 的密钥及证书目录 | String: Path，支持绝对及相对目录 | 选填 | 1. iotdb 相关 DataNode 的 conf 目录下的 `opc_security` 文件夹 `/`。2. 如无 iotdb 的 conf 目录（例如 IDEA 中启动 DataNode），则为用户主目录下的 `iotdb_opc_security` 文件夹 `/` | -| opcua.security-policy | OPC UA 连接使用的安全策略，不区分大小写。可以配置多个，用`,`连接。配置一个安全策略后，client 才能用对应的策略连接。当前实现默认支持`None`和`Basic256Sha256`策略，应该默认改为任意的非`None`策略，`None`策略在调试环境中单独配置，因为`None`策略虽然不需移动证书，操作方便，但是不安全，生产环境的 server 不建议支持该策略。注意：V2.0.8 起支持该参数，且仅支持 client-server 模式 | String（安全性依次递增）:
`None`
`Basic128Rsa15`
`Basic256`
`Basic256Sha256`
`Aes128_Sha256_RsaOaep`
`Aes256_Sha256_RsaPss` | 选填| `Basic256Sha256`,`Aes128_Sha256_RsaOaep`,`lAes256_Sha256_RsaPss` | -| sink.opcua.enable-anonymous-access | OPC UA 是否允许匿名访问 | Boolean | 选填 | true | -| sink.user | 用户，这里指 OPC UA 的允许用户 | String | 选填 | root | -| sink.password | 密码，这里指 OPC UA 的允许密码 | String | 选填 | TimechoDB@2021（V2.0.6.x 之前默认密码为root） | -| opcua.with-quality | OPC UA 的测点发布是否为 value + quality 模式。启用配置后，系统将按以下规则处理写入数据：
1. 同时包含 value 和 quality，则直接推送至 OPC UA Server。
2. 仅包含 value，则 quality 自动填充为 UNCERTAIN（默认值，支持自定义配置）。
3. 仅包含 quality，则该写入被忽略，不进行任何处理。
4. 包含非 value/quality 字段，则忽略该数据，并记录警告日志（日志频率可配置，避免高频干扰）。
5. quality 类型限制：目前仅支持布尔类型（true 表示 GOOD，false 表示 BAD）； 注意：V2.0.8 起支持该参数，且仅支持 client-server 模式 | Boolean | 选填 | false | -| opcua.value-name | With-quality 为 true 时生效，表示 value 测点的名字。 注意：V2.0.8 起支持该参数，且仅支持 client-server 模式 | String | 选填 | value | -| opcua.quality-name | With-quality 为 true 时生效，表示 quality 测点的名字。 注意：V2.0.8 起支持该参数，且仅支持 client-server 模式 | String | 选填 | quality | -| opcua.default-quality | 没有 quality 时，可以通过 SQL 参数指定`GOOD`/`UNCERTAIN`/`BAD`。 注意：V2.0.8 起支持该参数，且仅支持 client-server 模式 | String:`GOOD`/`UNCERTAIN`/`BAD` | 选填 | `UNCERTAIN` | -| opcua.timeout-seconds | Client 连接 server 的超时秒数，仅在 IoTDB 为 client 时生效 注意：V2.0.8 起支持该参数，且仅支持 client-server 模式 | Long | 选填 | 10L | +| **参数** | **描述** | **取值范围** | **是否必填** | **默认值** | +| ------------------------------------ |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| -------------------- |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sink | OPC UA SINK | String: opc-ua-sink | 必填 | | +| sink.opcua.model | OPC UA 使用的模式 | String: client-server / pub-sub | 选填 | client-server | +| sink.opcua.tcp.port | OPC UA 的 TCP 端口 | Integer: [0, 65536] | 选填 | 12686 | +| sink.opcua.https.port | OPC UA 的 HTTPS 端口 | Integer: [0, 65536] | 选填 | 8443 | +| sink.opcua.security.dir | OPC UA 的密钥及证书目录 | String: Path，支持绝对及相对目录 | 选填 | 1. iotdb 相关 DataNode 的 conf 目录下的 `opc_security` 文件夹 `/`。2. 如无 iotdb 的 conf 目录（例如 IDEA 中启动 DataNode），则为用户主目录下的 `iotdb_opc_security` 文件夹 `/` | +| opcua.security-policy | OPC UA 连接使用的安全策略，不区分大小写。可以配置多个，用`,`连接。配置一个安全策略后，client 才能用对应的策略连接。当前实现默认支持`None`和`Basic256Sha256`策略，应该默认改为任意的非`None`策略，`None`策略在调试环境中单独配置，因为`None`策略虽然不需移动证书，操作方便，但是不安全，生产环境的 server 不建议支持该策略。注意：V2.0.8-beta 起支持该参数，且仅支持 client-server 模式 | String（安全性依次递增）:
`None`
`Basic128Rsa15`
`Basic256`
`Basic256Sha256`
`Aes128_Sha256_RsaOaep`
`Aes256_Sha256_RsaPss` | 选填| `Basic256Sha256`,`Aes128_Sha256_RsaOaep`,`lAes256_Sha256_RsaPss` | +| sink.opcua.enable-anonymous-access | OPC UA 是否允许匿名访问 | Boolean | 选填 | true | +| sink.user | 用户，这里指 OPC UA 的允许用户 | String | 选填 | root | +| sink.password | 密码，这里指 OPC UA 的允许密码 | String | 选填 | TimechoDB@2021（V2.0.6.x 之前默认密码为root） | +| opcua.with-quality | OPC UA 的测点发布是否为 value + quality 模式。启用配置后，系统将按以下规则处理写入数据：
1. 同时包含 value 和 quality，则直接推送至 OPC UA Server。
2. 仅包含 value，则 quality 自动填充为 UNCERTAIN（默认值，支持自定义配置）。
3. 仅包含 quality，则该写入被忽略，不进行任何处理。
4. 包含非 value/quality 字段，则忽略该数据，并记录警告日志（日志频率可配置，避免高频干扰）。
5. quality 类型限制：目前仅支持布尔类型（true 表示 GOOD，false 表示 BAD）； 注意：V2.0.8-beta 起支持该参数，且仅支持 client-server 模式 | Boolean | 选填 | false | +| opcua.value-name | With-quality 为 true 时生效，表示 value 测点的名字。 注意：V2.0.8-beta 起支持该参数，且仅支持 client-server 模式 | String | 选填 | value | +| opcua.quality-name | With-quality 为 true 时生效，表示 quality 测点的名字。 注意：V2.0.8-beta 起支持该参数，且仅支持 client-server 模式 | String | 选填 | quality | +| opcua.default-quality | 没有 quality 时，可以通过 SQL 参数指定`GOOD`/`UNCERTAIN`/`BAD`。 注意：V2.0.8-beta 起支持该参数，且仅支持 client-server 模式 | String:`GOOD`/`UNCERTAIN`/`BAD` | 选填 | `UNCERTAIN` | +| opcua.timeout-seconds | Client 连接 server 的超时秒数，仅在 IoTDB 为 client 时生效 注意：V2.0.8-beta 起支持该参数，且仅支持 client-server 模式 | Long | 选填 | 10L | #### 2.1.3 示例 @@ -288,7 +288,7 @@ create pipe p1 > **参数命名注意**：以上参数均支持省略 `opcua.` 前缀，例如 `node-urls` 和 `opcua.node-urls` 等价。 > -> **参数支持说明**：V2.0.8 起支持以上`opcua. `相关参数，且仅支持` client-server` 模式 +> **参数支持说明**：V2.0.8-beta 起支持以上`opcua. `相关参数，且仅支持` client-server` 模式 #### 3.1.3 示例 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 7bf4d6d23..67c0278cb 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -87,7 +87,7 @@ b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4 ### 2.3 环境要求 * 建议操作环境: Linux, MacOS； -* IoTDB 版本：>= V 2.0.8； +* IoTDB 版本：>= V 2.0.8-beta； ## 3. 安装部署及使用 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md index cee303d62..167973563 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md @@ -85,7 +85,7 @@ sha512sum timechodb-2.0.6.1-ainode-bin.zip ### 2.3 环境要求 * 建议操作环境: Linux, MacOS； -* TimechoDB 版本：>= V 2.0.8； +* TimechoDB 版本：>= V 2.0.8-beta； ## 3. 安装部署及使用 diff --git a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md index 496c7ed25..8c9f8b550 100644 --- a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md @@ -40,8 +40,8 @@ | -pw | --password | 密码 | 否 | root | | -t | --target | 指定输出文件的目标文件夹，如果路径不存在新建文件夹 | √ | | | -pfn | --prefix\_file\_name | 指定导出文件的名称。例如：abc,生成的文件是abc\_0.tsfile、abc\_1.tsfile | 否 | dump\_0.tsfile | -| -q | --query | 要执行的查询语句。自 V2.0.8 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | -| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8 之前)
`Long.MAX_VALUE`(V2.0.8 及之后)
范围：`-1~Long.MAX_VALUE` | +| -q | --query | 要执行的查询语句。自 V2.0.8-beta 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | +| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8-beta 之前)
`Long.MAX_VALUE`(V2.0.8-beta 及之后)
范围：`-1~Long.MAX_VALUE` | | -help | --help | 显示帮助信息 | 否 | | ### 2.2 Csv 格式 diff --git a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md index 642d29af3..3b98da398 100644 --- a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md +++ b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md @@ -40,8 +40,8 @@ | -pw | --password | 密码 | 否 | TimechoDB@2021 (V2.0.6.x 版本之前为 root) | | -t | --target | 指定输出文件的目标文件夹，如果路径不存在新建文件夹 | √ | | | -pfn | --prefix\_file\_name | 指定导出文件的名称。例如：abc,生成的文件是abc\_0.tsfile、abc\_1.tsfile | 否 | dump\_0.tsfile | -| -q | --query | 要执行的查询语句。自 V2.0.8 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | -| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8 之前)
`Long.MAX_VALUE`(V2.0.8 及之后)
范围：`-1~Long.MAX_VALUE` | +| -q | --query | 要执行的查询语句。自 V2.0.8-beta 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | +| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8-beta 之前)
`Long.MAX_VALUE`(V2.0.8-beta 及之后)
范围：`-1~Long.MAX_VALUE` | | -help | --help | 显示帮助信息 | 否 | | ### 2.2 Csv 格式 diff --git a/src/zh/UserGuide/latest/User-Manual/Audit-Log_timecho.md b/src/zh/UserGuide/latest/User-Manual/Audit-Log_timecho.md index a4de129c8..787b61c27 100644 --- a/src/zh/UserGuide/latest/User-Manual/Audit-Log_timecho.md +++ b/src/zh/UserGuide/latest/User-Manual/Audit-Log_timecho.md @@ -31,7 +31,7 @@ * 可通过参数设置审计日志文件的存储周期，包括基于 TTL 实现时间滚动和基于 SpaceTL 实现空间滚动。 * 审计日志文件默认加密存储 -> 注意：该功能从 V2.0.8 版本开始提供。 +> 注意：该功能从 V2.0.8-beta 版本开始提供。 ## 2. 配置参数 diff --git a/src/zh/UserGuide/latest/User-Manual/Maintenance-statement.md b/src/zh/UserGuide/latest/User-Manual/Maintenance-statement.md index 93259a49a..45b37b014 100644 --- a/src/zh/UserGuide/latest/User-Manual/Maintenance-statement.md +++ b/src/zh/UserGuide/latest/User-Manual/Maintenance-statement.md @@ -248,7 +248,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8 起支持该功能 +> V2.0.8-beta 起支持该功能 #### 语法：