From 5b3ae58f037da563981f7a4d5f2ffe9a37a27e5c Mon Sep 17 00:00:00 2001 From: Leto_b Date: Wed, 15 Apr 2026 11:06:30 +0800 Subject: [PATCH] update apache release history and remove -beta --- src/.vuepress/sidebar/V2.0.x/en-Table.ts | 6 +- src/.vuepress/sidebar/V2.0.x/en-Tree.ts | 6 +- src/.vuepress/sidebar/V2.0.x/zh-Table.ts | 6 +- src/.vuepress/sidebar/V2.0.x/zh-Tree.ts | 6 +- .../API/Programming-Java-Native-API_apache.md | 21 ------- .../Programming-Python-Native-API_apache.md | 2 +- .../Background-knowledge/Data-Type_apache.md | 2 - .../Basic-Concept/Write-Updata-Data_apache.md | 54 ---------------- .../Release-history_apache.md | 50 ++++++++++++++- .../Reference/System-Config-Manual_apache.md | 17 ------ .../Table/Reference/System-Tables_apache.md | 10 +-- .../Table/SQL-Manual/Basis-Function_apache.md | 2 +- .../SQL-Manual/Featured-Functions_apache.md | 41 ------------- .../SQL-Maintenance-Statements_apache.md | 2 +- .../SQL-Metadata-Operations_apache.md | 2 +- .../Table/SQL-Manual/Select-Clause_apache.md | 30 --------- .../Table/User-Manual/Audit-Log_timecho.md | 2 +- .../Table/User-Manual/Data-Sync_apache.md | 4 +- .../Maintenance-commands_apache.md | 4 +- .../Table/User-Manual/Tree-to-Table_apache.md | 4 +- .../Programming-Python-Native-API_apache.md | 2 +- .../Release-history_apache.md | 61 ++++++++++++++++--- .../Tree/User-Manual/Audit-Log_timecho.md | 2 +- .../Tree/User-Manual/Data-Sync_apache.md | 26 ++++---- .../Maintenance-commands_apache.md | 4 +- .../Release-history_apache.md | 13 ++++ .../Release-history_apache.md | 14 +++++ .../API/Programming-Java-Native-API_apache.md | 21 ------- .../Programming-Python-Native-API_apache.md | 2 +- .../Background-knowledge/Data-Type_apache.md | 2 - .../Basic-Concept/Write-Updata-Data_apache.md | 54 ---------------- .../AINode_Deployment_Upgrade_apache.md | 2 +- .../AINode_Deployment_Upgrade_timecho.md | 2 +- .../Release-history_apache.md | 46 ++++++++++++++ .../Reference/System-Config-Manual_apache.md | 17 ------ .../Reference/System-Tables_apache.md | 10 +-- .../SQL-Manual/Basis-Function_apache.md | 2 +- .../SQL-Manual/Featured-Functions_apache.md | 40 ------------ .../SQL-Maintenance-Statements_apache.md | 2 +- .../SQL-Metadata-Operations_apache.md | 2 +- .../SQL-Manual/Select-Clause_apache.md | 31 ---------- .../Tools-System/Data-Export-Tool_apache.md | 4 +- .../User-Manual/Data-Sync_apache.md | 4 +- .../Maintenance-commands_apache.md | 4 +- .../User-Manual/Tree-to-Table_apache.md | 4 +- .../Programming-Python-Native-API_apache.md | 2 +- .../AINode_Deployment_Upgrade_apache.md | 2 +- .../AINode_Deployment_Upgrade_timecho.md | 2 +- .../Release-history_apache.md | 45 ++++++++++++++ .../Tools-System/Data-Export-Tool_apache.md | 4 +- .../latest/User-Manual/Data-Sync_apache.md | 16 ++--- .../Maintenance-commands_apache.md | 4 +- .../API/Programming-Java-Native-API_apache.md | 18 ------ .../Programming-Python-Native-API_apache.md | 2 +- .../Background-knowledge/Data-Type_apache.md | 2 - .../Basic-Concept/Table-Management_apache.md | 2 +- .../Basic-Concept/Write-Updata-Data_apache.md | 53 ---------------- .../Release-history_apache.md | 45 ++++++++++++++ .../Reference/System-Config-Manual_apache.md | 18 ------ .../Table/Reference/System-Tables_apache.md | 10 +-- .../Table/SQL-Manual/Basis-Function_apache.md | 2 +- .../SQL-Manual/Featured-Functions_apache.md | 41 ------------- .../SQL-Maintenance-Statements_apache.md | 2 +- .../SQL-Metadata-Operations_apache.md | 2 +- .../Table/SQL-Manual/Select-Clause_apache.md | 31 ---------- .../Table/User-Manual/Audit-Log_timecho.md | 2 +- .../Table/User-Manual/Data-Sync_apache.md | 4 +- .../Maintenance-statement_apache.md | 4 +- .../Table/User-Manual/Tree-to-Table_apache.md | 4 +- .../Programming-Python-Native-API_apache.md | 2 +- .../Release-history_apache.md | 43 +++++++++++++ .../Tree/User-Manual/Audit-Log_timecho.md | 2 +- .../Tree/User-Manual/Data-Sync_apache.md | 28 ++++----- .../Maintenance-statement_apache.md | 4 +- .../Release-history_apache.md | 12 ++++ .../Release-history_apache.md | 12 ++++ .../API/Programming-Java-Native-API_apache.md | 18 ------ .../Programming-Python-Native-API_apache.md | 2 +- .../Background-knowledge/Data-Type_apache.md | 2 - .../Basic-Concept/Table-Management_apache.md | 2 +- .../Basic-Concept/Write-Updata-Data_apache.md | 53 ---------------- .../AINode_Deployment_Upgrade_apache.md | 2 +- .../AINode_Deployment_Upgrade_timecho.md | 2 +- .../Release-history_apache.md | 45 ++++++++++++++ .../Reference/System-Config-Manual_apache.md | 18 ------ .../Reference/System-Tables_apache.md | 10 +-- .../SQL-Manual/Basis-Function_apache.md | 2 +- .../SQL-Manual/Featured-Functions_apache.md | 41 ------------- .../SQL-Maintenance-Statements_apache.md | 2 +- .../SQL-Metadata-Operations_apache.md | 2 +- .../SQL-Manual/Select-Clause_apache.md | 31 ---------- .../Tools-System/Data-Export-Tool_apache.md | 20 +++--- .../User-Manual/Data-Sync_apache.md | 4 +- .../Maintenance-statement_apache.md | 4 +- .../User-Manual/Tree-to-Table_apache.md | 4 +- .../Programming-Python-Native-API_apache.md | 2 +- .../AINode_Deployment_Upgrade_apache.md | 2 +- .../AINode_Deployment_Upgrade_timecho.md | 2 +- .../Release-history_apache.md | 43 +++++++++++++ .../Tools-System/Data-Export-Tool_apache.md | 24 ++++---- .../latest/User-Manual/Data-Sync_apache.md | 28 ++++----- .../Maintenance-statement_apache.md | 4 +- 102 files changed, 592 insertions(+), 839 deletions(-) diff --git a/src/.vuepress/sidebar/V2.0.x/en-Table.ts b/src/.vuepress/sidebar/V2.0.x/en-Table.ts index e33316c54..81d2082ba 100644 --- a/src/.vuepress/sidebar/V2.0.x/en-Table.ts +++ b/src/.vuepress/sidebar/V2.0.x/en-Table.ts @@ -76,7 +76,7 @@ export const enSidebar = { collapsible: true, children: [ { text: 'AINode Deployment(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode Deployment(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, + { text: 'AINode Deployment(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -132,9 +132,9 @@ export const enSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, { text: 'TimeSeries Large Model(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: 'TimeSeries Large Model(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: 'TimeSeries Large Model(V2.0.8)', 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 dc83196b8..2aeebedea 100644 --- a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts +++ b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts @@ -83,7 +83,7 @@ export const enSidebar = { collapsible: true, children: [ { text: 'AINode Deployment(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode Deployment(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, + { text: 'AINode Deployment(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -148,9 +148,9 @@ export const enSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, { text: 'TimeSeries Large Model(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: 'TimeSeries Large Model(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: 'TimeSeries Large Model(V2.0.8)', 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 a8df5665b..21403f9ca 100644 --- a/src/.vuepress/sidebar/V2.0.x/zh-Table.ts +++ b/src/.vuepress/sidebar/V2.0.x/zh-Table.ts @@ -76,7 +76,7 @@ export const zhSidebar = { collapsible: true, children: [ { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode 部署(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, + { text: 'AINode 部署(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -130,9 +130,9 @@ export const zhSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, { text: '时序大模型(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: '时序大模型(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: '时序大模型(V2.0.8)', 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 0beffc28b..79f701ecf 100644 --- a/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts +++ b/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts @@ -77,7 +77,7 @@ export const zhSidebar = { collapsible: true, children: [ { text: 'AINode 部署(V2.0.5/6)', link: 'AINode_Deployment_apache' }, - { text: 'AINode 部署(V2.0.8-beta)', link: 'AINode_Deployment_Upgrade_apache' }, + { text: 'AINode 部署(V2.0.8)', link: 'AINode_Deployment_Upgrade_apache' }, ], }, ], @@ -139,9 +139,9 @@ export const zhSidebar = { prefix: 'AI-capability/', children: [ { text: 'AINode(V2.0.5/6)', link: 'AINode_apache' }, - { text: 'AINode(V2.0.8-beta)', link: 'AINode_Upgrade_apache' }, + { text: 'AINode(V2.0.8)', link: 'AINode_Upgrade_apache' }, { text: '时序大模型(V2.0.5/6)', link: 'TimeSeries-Large-Model' }, - { text: '时序大模型(V2.0.8-beta)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, + { text: '时序大模型(V2.0.8)', link: 'TimeSeries-Large-Model_Upgrade_apache' }, ], }, { diff --git a/src/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md b/src/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md index 42f813a83..71c5f13d7 100644 --- a/src/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md +++ b/src/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md @@ -64,27 +64,6 @@ The `ITableSession` interface defines basic operations for interacting with IoTD | executeQueryStatement(String sql, long timeoutInMs) | Executes a query SQL statement with a specified timeout in milliseconds. | `sql`: The SQL query statement. `timeoutInMs`: Query timeout in milliseconds. | `SessionDataSet` | `StatementExecutionException` | | close() | Closes the session and releases resources. | None | None | IoTDBConnectionException | -**Description of Object Data Type:** - -Since V2.0.8-beta, the `iTableSession.insert(Tablet tablet)` interface supports splitting a single Object-class file into multiple segments and writing them sequentially in order. When the column data type in the Tablet data structure is **`TSDataType.Object`**, you need to use the following method to populate the Tablet: - -```Java -/* -rowIndex: row position in the tablet -columnIndex: column position in the tablet -isEOF: whether the current write operation contains the last segment of the Object file -offset: starting offset of the current write content within the Object file -content: byte array of the current write content -Note: When writing, ensure the total length of all segmented byte[] arrays equals the original Object size, -otherwise it will cause incorrect data size. -*/ -void addValue(int rowIndex, int columnIndex, boolean isEOF, long offset, byte[] content) -``` - -During queries, the following four methods are supported to retrieve values: -`Field.getStringValue`, `Field.getObjectValue`, `SessionDataSet.DataIterator.getObject`, and `SessionDataSet.DataIterator.getString`. -All these methods return a String containing metadata in the format: -`(Object) XX.XX KB` (where XX.XX KB represents the actual object size). #### 3.1.3 Sample Code diff --git a/src/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md b/src/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md index d60247404..98227e15e 100644 --- a/src/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md +++ b/src/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md @@ -46,7 +46,7 @@ Note: Do not use a newer client to connect to an older server, as this may cause | execute_query_statement | Executes a query SQL statement and retrieves results. | sql: `str` | `SessionDataSet` | | close | Closes the session and releases resources. | None | None | -**Since V2.0.8-beta**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: +**Since V2.0.8**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: ```python # Batch DataFrame retrieval diff --git a/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md b/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md index 955960d69..bab979e10 100644 --- a/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md +++ b/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md @@ -33,8 +33,6 @@ IoTDB supports the following ten data types: - **TEXT** (Text data, suitable for long strings, Not recommended) - **STRING** (String data with additional statistical information for optimized queries) - **BLOB** (Large binary object) -- **OBJECT** (Large Binary Object) - > Supported since V2.0.8-beta - **TIMESTAMP** (Timestamp, representing precise moments in time) - **DATE** (Date, storing only calendar date information) diff --git a/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md b/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md index 58bf91394..d7627d792 100644 --- a/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md +++ b/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md @@ -316,60 +316,6 @@ It costs 0.014s * For more details about user permissions, refer to [Authority Management](../User-Manual/Authority-Management_apache.md). -### 1.7 Writing Object Type - -To avoid oversized Object write requests, values of **Object** type can be split into segments and written sequentially. In SQL, the `to_object(isEOF, offset, content)` function must be used for value insertion. - -> Supported since V2.0.8-beta - -**Syntax:** - -```SQL -INSERT INTO tableName(time, columnName) VALUES(timeValue, TO_OBJECT(isEOF, offset, content)); -``` - -**Parameters:** - -| Name | Data Type | Description | -|---------|--------------------|-----------------------------------------------------------------------------| -| isEOF | BOOLEAN | Whether the current write contains the last segment of the Object | -| offset | INT64 | Starting offset of the current segment within the Object | -| content | Hexadecimal (HEX) | Content of the current segment | - -**Examples:** - -Add an Object-type column `s1` to table `table1`: - -```SQL -ALTER TABLE table1 ADD COLUMN IF NOT EXISTS s1 OBJECT FIELD COMMENT 'object type'; -``` - -1. **Non-segmented write** - -```SQL -INSERT INTO table1(time, device_id, s1) VALUES(NOW(), 'tag1', TO_OBJECT(TRUE, 0, X'696F746462')); -``` - -2. **Segmented write** - -```SQL --- First write: TO_OBJECT(FALSE, 0, X'696F'); -INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(FALSE, 0, X'696F')); - --- Second write: TO_OBJECT(FALSE, 2, X'7464'); -INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(FALSE, 2, X'7464')); - --- Third write: TO_OBJECT(TRUE, 4, X'62'); -INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(TRUE, 4, X'62')); -``` - -**Notes:** - -1. If only partial segments of an Object are written, querying the column will return `NULL`. Data becomes accessible only after all segments are successfully written. -2. During segmented writes, if the `offset` of the current write does not match the current size of the Object, the write operation will fail. -3. If `offset=0` is used after partial writes, the existing content will be overwritten with new data. - - ## 2. Data Updates ### 2.1 Syntax diff --git a/src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md b/src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md index 2e4f65aff..04e6af38b 100644 --- a/src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md +++ b/src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md @@ -20,11 +20,43 @@ --> # Release History +## V2.0.8 + +> Release Date: 2026.04.14 + +V2.0.8 expands AI model capabilities by adding support for Chronos-2, one of the mainstream time-series foundation models, while enabling concurrent inference for built-in large models. On the database side, TIME columns now support custom naming, data synchronization path configuration flexibility has been optimized, and comprehensive improvements have been made to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Query Module**: Added functionality to display the list of available DataNode nodes +* **Query Module**: Added system table for统计查询延迟信息 in the table model +* **Query Module**: Python SessionDataset now supports converting TsBlock to DataFrame and returning DataFrames in batches +* **Storage Module**: TIME column now supports custom column naming +* **Storage Module**: Added SQL support for viewing the complete definition statements of created tables/views +* **Stream Processing Module**: Pipe synchronization now supports excluding specified devices/measurement points from synchronization +* **Stream Processing Module**: Multiple exact paths can now be specified in a single Pipe +* **Stream Processing Module**: When filtering paths in Pipe, `source.pattern` and `source.path` parameters can now be used together with comma separation +* **AI Module**: Built-in Chronos-2 model with prediction support +* **AI Module**: Timer-XL and Sundial built-in models now support concurrent inference +* **System Module**: Added system table for displaying DataNode node connection status in the table model +* **Miscellaneous**: Fixed security vulnerabilities CVE-2025-12183, CVE-2025-66566, and CVE-2025-11226 + +## V2.0.7 + +> Release Date: 2026.03.04 + +V2.0.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V2.0.6 > Release Date: 2026.01.20 -V2.0.6 is the official release of the dual-model (tree and table) architecture. It introduces **query-writeback capability for the table model**, new **bitwise operation functions** (built-in scalar functions), and **push-down-capable time functions**, while delivering comprehensive improvements in database monitoring, performance, and stability. Specific release contents are as follows: +V2.0.6 is the official release of the dual-mode (tree and table) architecture. It introduces **query-writeback capability for the table mode**, new **bitwise operation functions** (built-in scalar functions), and **push-down-capable time functions**, while delivering comprehensive improvements in database monitoring, performance, and stability. Specific release contents are as follows: * **Query Module**: Added support for query-writeback functionality in the table model. * **Query Module**: Enhanced row-pattern recognition in the table model to support aggregate functions, enabling analysis and computation over consecutive data sequences. @@ -37,7 +69,7 @@ V2.0.6 is the official release of the dual-model (tree and table) architecture. > Release Date: 2025.08.21 -V2.0.5, as the official release of the Dual-Model Tree-Table system, primarily introduces the tree-to-table view, window functions for the table model, the aggregate function approx_most_frequent, and supports LEFT & RIGHT JOIN as well as ASOF LEFT JOIN. The AINode now includes two new built-in models, Timer-XL and Timer-Sundial, and supports inference capabilities for both tree and table models. Additionally, this version brings comprehensive improvements to database monitoring, performance, and stability. The specific updates are as follows: +V2.0.5, as the official release of the Dual-Mode Tree-Table system, primarily introduces the tree-to-table view, window functions for the table model, the aggregate function approx_most_frequent, and supports LEFT & RIGHT JOIN as well as ASOF LEFT JOIN. The AINode now includes two new built-in models, Timer-XL and Timer-Sundial, and supports inference capabilities for both tree and table models. Additionally, this version brings comprehensive improvements to database monitoring, performance, and stability. The specific updates are as follows: * **Query Module**: Supports manual creation of tree-to-table views * **Query Module**: Adds window functions for the table model @@ -134,6 +166,20 @@ V2.0.1-beta introduces dual tree-table model configuration, supporting standard * ​**​Ecosystem Integration​**​: * Kubernetes Operator support +## V1.3.7 + +> Release Date: 2026.03.04 + +V1.3.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + + ## V1.3.6 > Release Date: 2026.01.20 diff --git a/src/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md b/src/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md index 2d71d982f..4fc70abb3 100644 --- a/src/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md +++ b/src/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md @@ -1812,23 +1812,6 @@ The `iotdb-system.properties` file contains various configurations for managing | Default | -1 | | Effective | Restart required. | -- max_object_file_size_in_byte - -| Name | max_object_file_size_in_byte | -|-------------|--------------------------------------------------------------------------| -| Description | Maximum size limit for a single object file (supported since V2.0.8-beta). | -| Type | long | -| Default | 4294967296 (4 GB in bytes) | -| Effective | Hot reload | - -- restrict_object_limit - -| Name | restrict_object_limit | -|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Description | No special restrictions on table names, column names, or device identifiers for `OBJECT` type (supported since V2.0.8-beta). When set to `true` and the table contains `OBJECT` columns, the following restrictions apply:
1. Naming Rules: Values in TAG columns, table names, and field names must not use `.` or `..`; Prohibited characters include `./` or `.\`, otherwise metadata creation will fail; Names containing filesystem-unsupported characters will cause write errors.
2. Case Sensitivity: If the underlying filesystem is case-insensitive, device identifiers like `'d1'` and `'D1'` are treated as identical; Creating similar identifiers may overwrite `OBJECT` data files, leading to data corruption.
3. Storage Path: Actual storage path format: `${dataregionid}/${tablename}/${tag1}/${tag2}/.../${field}/${timestamp}.bin` | -| Type | boolean | -| Default | false | -| Effective | Can only be modified before the first service startup. | ### 4.20 Compaction Configurations diff --git a/src/UserGuide/Master/Table/Reference/System-Tables_apache.md b/src/UserGuide/Master/Table/Reference/System-Tables_apache.md index 01d109846..be99de4be 100644 --- a/src/UserGuide/Master/Table/Reference/System-Tables_apache.md +++ b/src/UserGuide/Master/Table/Reference/System-Tables_apache.md @@ -372,7 +372,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS -> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8-beta. +> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8. * Contains information about all models in the database. * The table structure is as follows: @@ -597,7 +597,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * Contains all connections in the cluster. * The table structure is as follows: @@ -624,7 +624,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT_QUERIES -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * 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: @@ -655,7 +655,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES_COSTS_HISTOGRAM -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * 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: @@ -689,7 +689,7 @@ IoTDB> select * from information_schema.queries_costs_histogram limit 10 ### 2.21 SERVICES -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * Displays services (MQTT service, REST service) on all active DataNodes (with RUNNING or READ-ONLY status). * Table structure: diff --git a/src/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md b/src/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md index c6e11f5c9..575551b3b 100644 --- a/src/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md +++ b/src/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md @@ -1292,7 +1292,7 @@ coalesce(value1, value2[, ...]) #### 8.1.1 cast(value AS type) → type -Explicitly converts a value to the specified type. This can be used to convert strings (`VARCHAR`) to numeric types or numeric values to string types. Starting from V2.0.8-beta, OBJECT type can be explicitly cast to STRING type. +Explicitly converts a value to the specified type. This can be used to convert strings (`VARCHAR`) to numeric types or numeric values to string types. If the conversion fails, a runtime error is thrown. diff --git a/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md b/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md index 9980e89f8..d0b771fee 100644 --- a/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md +++ b/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md @@ -693,44 +693,3 @@ IoTDB> SELECT window_start, window_end, stock_id, avg(price) as avg FROM CUMULAT |2021-01-01T09:00:00.000+08:00|2021-01-01T09:10:00.000+08:00| AAPL|101.66666666666667| +-----------------------------+-----------------------------+--------+------------------+ ``` - -## 4. Object Type Read Function - -**Description**: -Reads binary content from an `OBJECT` type column and returns a `BLOB` type (raw binary data of the object). -> Supported since V2.0.8-beta - -**Syntax:** -```SQL -READ_OBJECT(object [, offset, length]) -``` - -**Parameters:** -- **Required**: - `object` (OBJECT type) -- **Optional**: - - `offset` (long/INT64): Start position for reading. Default: `0`. - - Throws error if `offset < 0` or `offset >= full file length`. - - `length` (long/INT64): Number of bytes to read. Default: full file length. - - Error if `length > 2^31 - 1`. - - If `length` exceeds remaining bytes from `offset`, reads until end of file. - - If `length < 0`, reads all remaining data from `offset`. - -**Examples:** -```sql -IoTDB:database1> SELECT READ_OBJECT(s1) FROM table1 WHERE device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 - -IoTDB:database1> SELECT READ_OBJECT(s1, 0, 3) FROM table1 WHERE device_id = 'tag1' -+--------+ -| _col0| -+--------+ -|0x696f74| -+--------+ -Total line number = 1 -``` diff --git a/src/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md b/src/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md index 36808b379..8b975d660 100644 --- a/src/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md +++ b/src/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.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-beta. +> This feature is supported starting from v2.0.8. **Syntax**: diff --git a/src/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md b/src/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md index 85b2aac99..156b68990 100644 --- a/src/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md +++ b/src/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md @@ -212,7 +212,7 @@ CREATE TABLE tableC ( "Temperature" int32 FIELD COMMENT 'temperature' ) with (TTL=DEFAULT); - -- Custom time column: named time_test, located in the second column of the table. (Support from V2.0.8-beta) + -- Custom time column: named time_test, located in the second column of the table. (Support from V2.0.8) CREATE TABLE table1 ( region STRING TAG, time_user_defined TIMESTAMP TIME, diff --git a/src/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md b/src/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md index 57abbe5de..d308e58fb 100644 --- a/src/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md +++ b/src/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md @@ -274,36 +274,6 @@ Total line number = 18 It costs 0.189s ``` -#### 3.1.4 Object Type Query - -> Supported since V2.0.8-beta - -**Example 1: Directly querying Object type data** - -```sql -IoTDB:database1> SELECT s1 FROM table1 WHERE device_id = 'tag1' -+------------+ -| s1| -+------------+ -|(Object) 5 B| -+------------+ -Total line number = 1 -It costs 0.428s -``` - -**Example 2: Retrieving raw content of Object type data using `read_object` function** - -```sql -IoTDB:database1> SELECT read_object(s1) FROM table1 WHERE device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 -It costs 0.188s -``` - ### 3.2 Columns Function diff --git a/src/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md b/src/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md index c4d06e6c1..d62a08f68 100644 --- a/src/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md +++ b/src/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md @@ -32,7 +32,7 @@ Audit logs serve as the record credentials of a database, enabling tracking of v * Supports configuring parameters to count slow requests (with write/query latency exceeding a threshold, default 3000 milliseconds) within any specified time period * Audit log files are stored in encrypted format by default -> Note: This feature is available from version V2.0.8-beta onwards. +> Note: This feature is available from version V2.0.8 onwards. ## 2. Configuration Parameters diff --git a/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md index fb859efa1..5ff5edbb0 100644 --- a/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md @@ -120,7 +120,7 @@ WITH SINK ( **Note**: -Starting from V2.0.8-beta, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: +Starting from V2.0.8, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: * History Pipe: The PipeId is the original name plus the suffix `_history` (e.g. `alldatapipe_history`). The source parameter carries the default configurations: `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` * Realtime Pipe: The PipeId is the original name plus the suffix `_realtime` (e.g. `alldatapipe_realtime`). The source parameter carries the default configuration: `'history.enable'='false'`. If metadata synchronization is configured, the Realtime Pipe will be responsible for sending the data. @@ -194,7 +194,7 @@ Example Output of `SHOW PIPES`: Example: -In V2.0.8-beta and later versions, create a full data synchronization task and view the task details. +In V2.0.8 and later versions, create a full data synchronization task and view the task details. ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') diff --git a/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md index 834b3ed94..bb7f21e18 100644 --- a/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/Master/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-beta. +> This feature is supported starting from v2.0.8. **Syntax**: @@ -371,7 +371,7 @@ IoTDB> SHOW AVAILABLE URLS **Description**: Returns service information (MQTT service, REST service) on all active DataNodes (in RUNNING or READ-ONLY state) in the current cluster. -> Supported since V2.0.8-beta +> Supported since V2.0.8 #### Syntax: ```sql diff --git a/src/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md b/src/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md index cc9c798b9..768d0343c 100644 --- a/src/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md +++ b/src/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md @@ -80,7 +80,7 @@ The name of the view, which follows the same rules as a table name (for specific * If a device in the tree model does not contain certain declared FIELD columns, or if their data types are inconsistent with the declared FIELD columns, the value for that FIELD column will always be `NULL`when querying that device. * If no FIELD columns are specified, the system automatically scans for all measurements under the `prefixPath`subtree (including all ordinary sequence measurements and measurements defined in any templates whose mounted paths overlap with the `prefixPath`) during creation. The column names will use the measurement names from the tree model. * The tree model cannot have measurements with the same name (case-insensitive) but different data types. -* `TIME`: When creating a view, you do not need to specify a time column. IoTDB automatically adds a column named "time" and places it as the first column. Since version V2.0.8-beta, views support **custom naming of the time column** during creation. The order of the custom time column in the view is determined by the order in the creation SQL. The related constraints are as follows: +* `TIME`: When creating a view, you do not need to specify a time column. IoTDB automatically adds a column named "time" and places it as the first column. Since version V2.0.8, views support **custom naming of the time column** during creation. The order of the custom time column in the view is determined by the order in the creation SQL. The related constraints are as follows: * When the column category is set to `TIME`, the data type must be `TIMESTAMP`. * Each view allows at most one time column (columnCategory = TIME). * If no time column is explicitly defined, no other column can use `time` as its name to avoid conflicts with the system's default time column naming. @@ -143,7 +143,7 @@ with (ttl=604800000) AS root.db.** ``` -When customizing the time column (supported since V2.0.8-beta), the SQL changes are as follows: +When customizing the time column (supported since V2.0.8), the SQL changes are as follows: ```SQL CREATE OR REPLACE VIEW viewdb."wind_turbine" diff --git a/src/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md b/src/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md index b0d43b4ac..b77fe093d 100644 --- a/src/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md +++ b/src/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md @@ -557,7 +557,7 @@ session.close() df = ... ``` -**Since V2.0.8-beta**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: +**Since V2.0.8**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: ```python # Batch DataFrame retrieval diff --git a/src/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md b/src/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md index 07fef6080..e0c3142d0 100644 --- a/src/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md +++ b/src/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md @@ -20,26 +20,58 @@ --> # Release History +## V2.0.8 + +> Release Date: 2026.04.14 + +V2.0.8 expands AI model capabilities by adding support for Chronos-2, one of the mainstream time-series foundation models, while enabling concurrent inference for built-in large models. On the database side, TIME columns now support custom naming, data synchronization path configuration flexibility has been optimized, and comprehensive improvements have been made to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Query Module**: Added functionality to display the list of available DataNode nodes +* **Query Module**: Added system table for统计查询延迟信息 in the table model +* **Query Module**: Python SessionDataset now supports converting TsBlock to DataFrame and returning DataFrames in batches +* **Storage Module**: TIME column now supports custom column naming +* **Storage Module**: Added SQL support for viewing the complete definition statements of created tables/views +* **Stream Processing Module**: Pipe synchronization now supports excluding specified devices/measurement points from synchronization +* **Stream Processing Module**: Multiple exact paths can now be specified in a single Pipe +* **Stream Processing Module**: When filtering paths in Pipe, `source.pattern` and `source.path` parameters can now be used together with comma separation +* **AI Module**: Built-in Chronos-2 model with prediction support +* **AI Module**: Timer-XL and Sundial built-in models now support concurrent inference +* **System Module**: Added system table for displaying DataNode node connection status in the table model +* **Miscellaneous**: Fixed security vulnerabilities CVE-2025-12183, CVE-2025-66566, and CVE-2025-11226 + +## V2.0.7 + +> Release Date: 2026.03.04 + +V2.0.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V2.0.6 > Release Date: 2026.01.20 -V2.0.6 is the official release of the dual-model (tree and table) architecture. It introduces **query-writeback capability for the table model**, new **bitwise operation functions** (built-in scalar functions), and **push-down-capable time functions**, while delivering comprehensive improvements in database monitoring, performance, and stability. Specific release contents are as follows: +V2.0.6 is the official release of the dual-mode (tree and table) architecture. It introduces **query-writeback capability for the table mode**, new **bitwise operation functions** (built-in scalar functions), and **push-down-capable time functions**, while delivering comprehensive improvements in database monitoring, performance, and stability. Specific release contents are as follows: -* **Query Module**: Added support for query-writeback functionality in the table model. -* **Query Module**: Enhanced row-pattern recognition in the table model to support aggregate functions, enabling analysis and computation over consecutive data sequences. -* **Query Module**: Introduced built-in scalar bitwise operation functions for the table model. -* **Query Module**: Added a push-down-capable `EXTRACT` time function for the table model. +* **Query Module**: Added support for query-writeback functionality in the table mode. +* **Query Module**: Enhanced row-pattern recognition in the table mode to support aggregate functions, enabling analysis and computation over consecutive data sequences. +* **Query Module**: Introduced built-in scalar bitwise operation functions for the table mode. +* **Query Module**: Added a push-down-capable `EXTRACT` time function for the table mode. * **Others**: Fixed security vulnerabilities CVE-2025-12183, CVE-2025-66566, and CVE-2025-11226. ## V2.0.5 > Release Date: 2025.08.21 -V2.0.5, as the official release of the Dual-Model Tree-Table system, primarily introduces the tree-to-table view, window functions for the table model, the aggregate function approx_most_frequent, and supports LEFT & RIGHT JOIN as well as ASOF LEFT JOIN. The AINode now includes two new built-in models, Timer-XL and Timer-Sundial, and supports inference capabilities for both tree and table models. Additionally, this version brings comprehensive improvements to database monitoring, performance, and stability. The specific updates are as follows: +V2.0.5, as the official release of the Dual-Mode Tree-Table system, primarily introduces the tree-to-table view, window functions for the table mode, the aggregate function approx_most_frequent, and supports LEFT & RIGHT JOIN as well as ASOF LEFT JOIN. The AINode now includes two new built-in models, Timer-XL and Timer-Sundial, and supports inference capabilities for both tree and table models. Additionally, this version brings comprehensive improvements to database monitoring, performance, and stability. The specific updates are as follows: * **Query Module**: Supports manual creation of tree-to-table views -* **Query Module**: Adds window functions for the table model +* **Query Module**: Adds window functions for the table mode * **Query Module**: Adds the aggregate function approx_most_frequent for the table model * **Query Module**: Extends JOIN functionality for the table model, supporting LEFT & RIGHT JOIN and ASOF LEFT JOIN * **Query Module**: The table model now supports row pattern recognition, enabling the capture of continuous data for analysis and computation @@ -114,7 +146,7 @@ As the official release of the dual tree-table model, V2.0.2 introduces table mo V2.0.1-beta introduces dual tree-table model configuration, supporting standard SQL query syntax, various functions/operators, stream processing, and Benchmark capabilities for the table model. Additional updates include: -* ​**​Table Model​**​: +* ​**​Table Mode​**​: * Supports standard SQL syntax (SELECT/WHERE/JOIN/GROUP BY/ORDER BY/LIMIT/subqueries) * Various functions including logical operators, mathematical functions, and time-series functions like DIFF * ​**​Storage Module​**​: @@ -134,6 +166,19 @@ V2.0.1-beta introduces dual tree-table model configuration, supporting standard * ​**​Ecosystem Integration​**​: * Kubernetes Operator support +## V1.3.7 + +> Release Date: 2026.03.04 + +V1.3.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V1.3.6 > Release Date: 2026.01.20 diff --git a/src/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md b/src/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md index 39c68b7ec..2264aaca2 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md +++ b/src/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md @@ -32,7 +32,7 @@ Audit logs serve as the record credentials of a database, enabling tracking of v * Supports configuring parameters to count slow requests (with write/query latency exceeding a threshold, default 3000 milliseconds) within any specified time period * Audit log files are stored in encrypted format by default -> Note: This feature is available from version V2.0.8-beta onwards. +> Note: This feature is available from version V2.0.8 onwards. ## 2. Configuration Parameters diff --git a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md index 7416a56a3..0f0a73962 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md @@ -125,7 +125,7 @@ WITH SINK ( **Note**: -Starting from V2.0.8-beta, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: +Starting from V2.0.8, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: * History Pipe: The PipeId is the original name plus the suffix `_history` (e.g. `alldatapipe_history`). The source parameter carries the default configurations: `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` * Realtime Pipe: The PipeId is the original name plus the suffix `_realtime` (e.g. `alldatapipe_realtime`). The source parameter carries the default configuration: `'history.enable'='false'`. If metadata synchronization is configured, the Realtime Pipe will be responsible for sending the data. @@ -198,7 +198,7 @@ The meanings of each column are as follows: Example: -In V2.0.8-beta and later versions, create a full data synchronization task and view the task details. +In V2.0.8 and later versions, create a full data synchronization task and view the task details. ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') @@ -515,18 +515,18 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1 ### 5.1 source parameter -| key | value | value range | required or not | default value | -| :------------------------------ | :----------------------------------------------------------- |:-----------------------------------------------------------------------| :------- | :------------- | -| source | iotdb-source | String: iotdb-source | Required | - | -| inclusion | Used to specify the range of data to be synchronized in the data synchronization task, including data, schema, and auth | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | Optional | data.insert | -| inclusion.exclusion | Used to exclude specific operations from the range specified by inclusion, reducing the amount of data synchronized | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | Optional | - | +| key | value | value range | required or not | default value | +| :------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------| :------- | :------------- | +| source | iotdb-source | String: iotdb-source | Required | - | +| inclusion | Used to specify the range of data to be synchronized in the data synchronization task, including data, schema, and auth | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | Optional | data.insert | +| inclusion.exclusion | Used to exclude specific operations from the range specified by inclusion, reducing the amount of data synchronized | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | Optional | - | | mode.streaming | Specifies the capture source for time-series data writes. Applicable when mode.streamingis false, determining the source for capturing data.insertspecified in inclusion. Offers two strategies:- true: ​​Dynamic capture selection.​​ The system adaptively chooses between capturing individual write requests or only TsFile sealing requests based on downstream processing speed. Prioritizes capturing write requests for lower latency when processing is fast; captures only file sealing requests to avoid backlog when slow. Suitable for most scenarios, balancing latency and throughput optimally.- false: ​​Fixed batch capture.​​ Captures only TsFile sealing requests. Suitable for resource-constrained scenarios to reduce system load. Note: The snapshot data captured upon pipe startup is only provided to downstream processing in file format. | Boolean: true / false | Optional | true | -| mode.strict | Determines the strictness when filtering data using time/ path/ database-name/ table-nameparameters:- true: ​​Strict filtering.​​ The system strictly filters captured data according to the given conditions, ensuring only matching data is selected.- false: ​​Non-strict filtering.​​ The system may include some extra data during filtering. Suitable for performance-sensitive scenarios to reduce CPU and I/O consumption. | Boolean: true / false | Optional | true | -| mode.snapshot | Determines the capture mode for time-series data, affecting the dataspecified in inclusion. Offers two modes:- true: ​​Static data capture.​​ Upon pipe startup, a one-time data snapshot is captured. ​​The pipe will automatically terminate (DROP PIPE SQL is executed automatically) after the snapshot data is fully consumed.​​- false: ​​Dynamic data capture.​​ In addition to capturing a snapshot upon startup, the pipe continuously captures subsequent data changes. The pipe runs continuously to handle the dynamic data stream. | Boolean: true / false | Optional | false | -| path | Can be specified when the user connects with sql_dialectset to tree. For upgraded user pipes, the default sql_dialectis tree. This parameter determines the capture scope for time-series data, affecting the dataspecified in inclusion, as well as some sequence-related metadata. Data is selected into the streaming pipe if its tree model path matches the specified path.
Starting from version V2.0.8-beta, this parameter supports specifying multiple exact paths in a single pipe, e.g., `'path'='root.test.d0.s1,root.test.d0.s2,root.test.d0.s3'`. | String: IoTDB-standard tree path pattern, wildcards allowed | Optional | root.** | -| start-time | The start event time for synchronizing all data, including start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MIN_VALUE | -| end-time | The end event time for synchronizing all data, including end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MAX_VALUE | -| forwarding-pipe-requests | Whether to forward data written by other Pipes (usually data synchronization) | Boolean: true /false | Optional | true | +| mode.strict | Determines the strictness when filtering data using time/ path/ database-name/ table-nameparameters:- true: ​​Strict filtering.​​ The system strictly filters captured data according to the given conditions, ensuring only matching data is selected.- false: ​​Non-strict filtering.​​ The system may include some extra data during filtering. Suitable for performance-sensitive scenarios to reduce CPU and I/O consumption. | Boolean: true / false | Optional | true | +| mode.snapshot | Determines the capture mode for time-series data, affecting the dataspecified in inclusion. Offers two modes:- true: ​​Static data capture.​​ Upon pipe startup, a one-time data snapshot is captured. ​​The pipe will automatically terminate (DROP PIPE SQL is executed automatically) after the snapshot data is fully consumed.​​- false: ​​Dynamic data capture.​​ In addition to capturing a snapshot upon startup, the pipe continuously captures subsequent data changes. The pipe runs continuously to handle the dynamic data stream. | Boolean: true / false | Optional | false | +| path | Can be specified when the user connects with sql_dialectset to tree. For upgraded user pipes, the default sql_dialectis tree. This parameter determines the capture scope for time-series data, affecting the dataspecified in inclusion, as well as some sequence-related metadata. Data is selected into the streaming pipe if its tree model path matches the specified path.
Starting from version V2.0.8, this parameter supports specifying multiple exact paths in a single pipe, e.g., `'path'='root.test.d0.s1,root.test.d0.s2,root.test.d0.s3'`. | String: IoTDB-standard tree path pattern, wildcards allowed | Optional | root.** | +| start-time | The start event time for synchronizing all data, including start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MIN_VALUE | +| end-time | The end event time for synchronizing all data, including end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MAX_VALUE | +| forwarding-pipe-requests | Whether to forward data written by other Pipes (usually data synchronization) | Boolean: true /false | Optional | true | | mods | Same as mods.enable, whether to send the MODS file for TSFile. | Boolean: true / false | Optional | false | > 💎 **Note:** The difference between the values of true and false for the data extraction mode `mode.streaming` diff --git a/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md index 1ed8b8521..af354af4d 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.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-beta. +> This feature is supported starting from v2.0.8. **Syntax**: @@ -277,7 +277,7 @@ IoTDB> SHOW AVAILABLE URLS **Description**: Returns service information (MQTT service, REST service) on all active DataNodes (in RUNNING or READ-ONLY state) in the current cluster. -> This feature is supported starting from v2.0.8-beta. +> This feature is supported starting from v2.0.8. #### Syntax: ```sql diff --git a/src/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md b/src/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md index 82f73cf2f..a631082cb 100644 --- a/src/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md +++ b/src/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,19 @@ --> # Release History +## V1.3.7 + +> Release Date: 2026.03.04 + +V1.3.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V1.3.6 > Release Date: 2026.01.20 diff --git a/src/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md b/src/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md index 82f73cf2f..ffa3c3d1f 100644 --- a/src/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md +++ b/src/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,20 @@ --> # Release History +## V1.3.7 + +> Release Date: 2026.03.04 + +V1.3.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + + ## V1.3.6 > Release Date: 2026.01.20 diff --git a/src/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md b/src/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md index 42f813a83..71c5f13d7 100644 --- a/src/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md +++ b/src/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md @@ -64,27 +64,6 @@ The `ITableSession` interface defines basic operations for interacting with IoTD | executeQueryStatement(String sql, long timeoutInMs) | Executes a query SQL statement with a specified timeout in milliseconds. | `sql`: The SQL query statement. `timeoutInMs`: Query timeout in milliseconds. | `SessionDataSet` | `StatementExecutionException` | | close() | Closes the session and releases resources. | None | None | IoTDBConnectionException | -**Description of Object Data Type:** - -Since V2.0.8-beta, the `iTableSession.insert(Tablet tablet)` interface supports splitting a single Object-class file into multiple segments and writing them sequentially in order. When the column data type in the Tablet data structure is **`TSDataType.Object`**, you need to use the following method to populate the Tablet: - -```Java -/* -rowIndex: row position in the tablet -columnIndex: column position in the tablet -isEOF: whether the current write operation contains the last segment of the Object file -offset: starting offset of the current write content within the Object file -content: byte array of the current write content -Note: When writing, ensure the total length of all segmented byte[] arrays equals the original Object size, -otherwise it will cause incorrect data size. -*/ -void addValue(int rowIndex, int columnIndex, boolean isEOF, long offset, byte[] content) -``` - -During queries, the following four methods are supported to retrieve values: -`Field.getStringValue`, `Field.getObjectValue`, `SessionDataSet.DataIterator.getObject`, and `SessionDataSet.DataIterator.getString`. -All these methods return a String containing metadata in the format: -`(Object) XX.XX KB` (where XX.XX KB represents the actual object size). #### 3.1.3 Sample Code diff --git a/src/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md b/src/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md index 2d6b6f7eb..fdf0a6c20 100644 --- a/src/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md +++ b/src/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md @@ -46,7 +46,7 @@ Note: Do not use a newer client to connect to an older server, as this may cause | execute_query_statement | Executes a query SQL statement and retrieves results. | sql: `str` | `SessionDataSet` | | close | Closes the session and releases resources. | None | None | -**Since V2.0.8-beta**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: +**Since V2.0.8**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: ```python # Batch DataFrame retrieval diff --git a/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md b/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md index 955960d69..bab979e10 100644 --- a/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md +++ b/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md @@ -33,8 +33,6 @@ IoTDB supports the following ten data types: - **TEXT** (Text data, suitable for long strings, Not recommended) - **STRING** (String data with additional statistical information for optimized queries) - **BLOB** (Large binary object) -- **OBJECT** (Large Binary Object) - > Supported since V2.0.8-beta - **TIMESTAMP** (Timestamp, representing precise moments in time) - **DATE** (Date, storing only calendar date information) diff --git a/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md b/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md index 58bf91394..d7627d792 100644 --- a/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md +++ b/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md @@ -316,60 +316,6 @@ It costs 0.014s * For more details about user permissions, refer to [Authority Management](../User-Manual/Authority-Management_apache.md). -### 1.7 Writing Object Type - -To avoid oversized Object write requests, values of **Object** type can be split into segments and written sequentially. In SQL, the `to_object(isEOF, offset, content)` function must be used for value insertion. - -> Supported since V2.0.8-beta - -**Syntax:** - -```SQL -INSERT INTO tableName(time, columnName) VALUES(timeValue, TO_OBJECT(isEOF, offset, content)); -``` - -**Parameters:** - -| Name | Data Type | Description | -|---------|--------------------|-----------------------------------------------------------------------------| -| isEOF | BOOLEAN | Whether the current write contains the last segment of the Object | -| offset | INT64 | Starting offset of the current segment within the Object | -| content | Hexadecimal (HEX) | Content of the current segment | - -**Examples:** - -Add an Object-type column `s1` to table `table1`: - -```SQL -ALTER TABLE table1 ADD COLUMN IF NOT EXISTS s1 OBJECT FIELD COMMENT 'object type'; -``` - -1. **Non-segmented write** - -```SQL -INSERT INTO table1(time, device_id, s1) VALUES(NOW(), 'tag1', TO_OBJECT(TRUE, 0, X'696F746462')); -``` - -2. **Segmented write** - -```SQL --- First write: TO_OBJECT(FALSE, 0, X'696F'); -INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(FALSE, 0, X'696F')); - --- Second write: TO_OBJECT(FALSE, 2, X'7464'); -INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(FALSE, 2, X'7464')); - --- Third write: TO_OBJECT(TRUE, 4, X'62'); -INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(TRUE, 4, X'62')); -``` - -**Notes:** - -1. If only partial segments of an Object are written, querying the column will return `NULL`. Data becomes accessible only after all segments are successfully written. -2. During segmented writes, if the `offset` of the current write does not match the current size of the Object, the write operation will fail. -3. If `offset=0` is used after partial writes, the existing content will be overwritten with new data. - - ## 2. Data Updates ### 2.1 Syntax 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 e11e3f9a5..137a44225 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-beta. +- IoTDB Version: >= V2.0.8. ## 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 769c49f0a..41dcd291e 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-beta. +- TimechoDB Version: >= V2.0.8. ## 3. Installation, Deployment, and Usage diff --git a/src/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md b/src/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md index 7d4069b2a..04e6af38b 100644 --- a/src/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md +++ b/src/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,38 @@ --> # Release History +## V2.0.8 + +> Release Date: 2026.04.14 + +V2.0.8 expands AI model capabilities by adding support for Chronos-2, one of the mainstream time-series foundation models, while enabling concurrent inference for built-in large models. On the database side, TIME columns now support custom naming, data synchronization path configuration flexibility has been optimized, and comprehensive improvements have been made to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Query Module**: Added functionality to display the list of available DataNode nodes +* **Query Module**: Added system table for统计查询延迟信息 in the table model +* **Query Module**: Python SessionDataset now supports converting TsBlock to DataFrame and returning DataFrames in batches +* **Storage Module**: TIME column now supports custom column naming +* **Storage Module**: Added SQL support for viewing the complete definition statements of created tables/views +* **Stream Processing Module**: Pipe synchronization now supports excluding specified devices/measurement points from synchronization +* **Stream Processing Module**: Multiple exact paths can now be specified in a single Pipe +* **Stream Processing Module**: When filtering paths in Pipe, `source.pattern` and `source.path` parameters can now be used together with comma separation +* **AI Module**: Built-in Chronos-2 model with prediction support +* **AI Module**: Timer-XL and Sundial built-in models now support concurrent inference +* **System Module**: Added system table for displaying DataNode node connection status in the table model +* **Miscellaneous**: Fixed security vulnerabilities CVE-2025-12183, CVE-2025-66566, and CVE-2025-11226 + +## V2.0.7 + +> Release Date: 2026.03.04 + +V2.0.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V2.0.6 > Release Date: 2026.01.20 @@ -134,6 +166,20 @@ V2.0.1-beta introduces dual tree-table model configuration, supporting standard * ​**​Ecosystem Integration​**​: * Kubernetes Operator support +## V1.3.7 + +> Release Date: 2026.03.04 + +V1.3.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + + ## V1.3.6 > Release Date: 2026.01.20 diff --git a/src/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md b/src/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md index 2d71d982f..4fc70abb3 100644 --- a/src/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md +++ b/src/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md @@ -1812,23 +1812,6 @@ The `iotdb-system.properties` file contains various configurations for managing | Default | -1 | | Effective | Restart required. | -- max_object_file_size_in_byte - -| Name | max_object_file_size_in_byte | -|-------------|--------------------------------------------------------------------------| -| Description | Maximum size limit for a single object file (supported since V2.0.8-beta). | -| Type | long | -| Default | 4294967296 (4 GB in bytes) | -| Effective | Hot reload | - -- restrict_object_limit - -| Name | restrict_object_limit | -|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Description | No special restrictions on table names, column names, or device identifiers for `OBJECT` type (supported since V2.0.8-beta). When set to `true` and the table contains `OBJECT` columns, the following restrictions apply:
1. Naming Rules: Values in TAG columns, table names, and field names must not use `.` or `..`; Prohibited characters include `./` or `.\`, otherwise metadata creation will fail; Names containing filesystem-unsupported characters will cause write errors.
2. Case Sensitivity: If the underlying filesystem is case-insensitive, device identifiers like `'d1'` and `'D1'` are treated as identical; Creating similar identifiers may overwrite `OBJECT` data files, leading to data corruption.
3. Storage Path: Actual storage path format: `${dataregionid}/${tablename}/${tag1}/${tag2}/.../${field}/${timestamp}.bin` | -| Type | boolean | -| Default | false | -| Effective | Can only be modified before the first service startup. | ### 4.20 Compaction Configurations diff --git a/src/UserGuide/latest-Table/Reference/System-Tables_apache.md b/src/UserGuide/latest-Table/Reference/System-Tables_apache.md index 01d109846..be99de4be 100644 --- a/src/UserGuide/latest-Table/Reference/System-Tables_apache.md +++ b/src/UserGuide/latest-Table/Reference/System-Tables_apache.md @@ -372,7 +372,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS -> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8-beta. +> This system table is available starting from version V 2.0.5 and has been discontinued since version V 2.0.8. * Contains information about all models in the database. * The table structure is as follows: @@ -597,7 +597,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * Contains all connections in the cluster. * The table structure is as follows: @@ -624,7 +624,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT_QUERIES -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * 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: @@ -655,7 +655,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES_COSTS_HISTOGRAM -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * 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: @@ -689,7 +689,7 @@ IoTDB> select * from information_schema.queries_costs_histogram limit 10 ### 2.21 SERVICES -> This system table is available starting from version V 2.0.8-beta +> This system table is available starting from version V 2.0.8 * Displays services (MQTT service, REST service) on all active DataNodes (with RUNNING or READ-ONLY status). * Table structure: diff --git a/src/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md b/src/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md index c6e11f5c9..575551b3b 100644 --- a/src/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md +++ b/src/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md @@ -1292,7 +1292,7 @@ coalesce(value1, value2[, ...]) #### 8.1.1 cast(value AS type) → type -Explicitly converts a value to the specified type. This can be used to convert strings (`VARCHAR`) to numeric types or numeric values to string types. Starting from V2.0.8-beta, OBJECT type can be explicitly cast to STRING type. +Explicitly converts a value to the specified type. This can be used to convert strings (`VARCHAR`) to numeric types or numeric values to string types. If the conversion fails, a runtime error is thrown. diff --git a/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md b/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md index 9980e89f8..fd91d58ef 100644 --- a/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md +++ b/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md @@ -694,43 +694,3 @@ IoTDB> SELECT window_start, window_end, stock_id, avg(price) as avg FROM CUMULAT +-----------------------------+-----------------------------+--------+------------------+ ``` -## 4. Object Type Read Function - -**Description**: -Reads binary content from an `OBJECT` type column and returns a `BLOB` type (raw binary data of the object). -> Supported since V2.0.8-beta - -**Syntax:** -```SQL -READ_OBJECT(object [, offset, length]) -``` - -**Parameters:** -- **Required**: - `object` (OBJECT type) -- **Optional**: - - `offset` (long/INT64): Start position for reading. Default: `0`. - - Throws error if `offset < 0` or `offset >= full file length`. - - `length` (long/INT64): Number of bytes to read. Default: full file length. - - Error if `length > 2^31 - 1`. - - If `length` exceeds remaining bytes from `offset`, reads until end of file. - - If `length < 0`, reads all remaining data from `offset`. - -**Examples:** -```sql -IoTDB:database1> SELECT READ_OBJECT(s1) FROM table1 WHERE device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 - -IoTDB:database1> SELECT READ_OBJECT(s1, 0, 3) FROM table1 WHERE device_id = 'tag1' -+--------+ -| _col0| -+--------+ -|0x696f74| -+--------+ -Total line number = 1 -``` diff --git a/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md b/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md index 36808b379..8b975d660 100644 --- a/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md +++ b/src/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.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-beta. +> This feature is supported starting from v2.0.8. **Syntax**: diff --git a/src/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md b/src/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md index 85b2aac99..156b68990 100644 --- a/src/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md +++ b/src/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md @@ -212,7 +212,7 @@ CREATE TABLE tableC ( "Temperature" int32 FIELD COMMENT 'temperature' ) with (TTL=DEFAULT); - -- Custom time column: named time_test, located in the second column of the table. (Support from V2.0.8-beta) + -- Custom time column: named time_test, located in the second column of the table. (Support from V2.0.8) CREATE TABLE table1 ( region STRING TAG, time_user_defined TIMESTAMP TIME, diff --git a/src/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md b/src/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md index 57abbe5de..3ca612e94 100644 --- a/src/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md +++ b/src/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md @@ -274,37 +274,6 @@ Total line number = 18 It costs 0.189s ``` -#### 3.1.4 Object Type Query - -> Supported since V2.0.8-beta - -**Example 1: Directly querying Object type data** - -```sql -IoTDB:database1> SELECT s1 FROM table1 WHERE device_id = 'tag1' -+------------+ -| s1| -+------------+ -|(Object) 5 B| -+------------+ -Total line number = 1 -It costs 0.428s -``` - -**Example 2: Retrieving raw content of Object type data using `read_object` function** - -```sql -IoTDB:database1> SELECT read_object(s1) FROM table1 WHERE device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 -It costs 0.188s -``` - - ### 3.2 Columns Function 1. Without combining expressions 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 770bcc688..4d05a188b 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-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`) | +| `-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`) | | `-help` | `--help` | Display help information. | No | - | ### 2.2 CSV Format diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md index fb859efa1..5ff5edbb0 100644 --- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md @@ -120,7 +120,7 @@ WITH SINK ( **Note**: -Starting from V2.0.8-beta, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: +Starting from V2.0.8, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: * History Pipe: The PipeId is the original name plus the suffix `_history` (e.g. `alldatapipe_history`). The source parameter carries the default configurations: `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` * Realtime Pipe: The PipeId is the original name plus the suffix `_realtime` (e.g. `alldatapipe_realtime`). The source parameter carries the default configuration: `'history.enable'='false'`. If metadata synchronization is configured, the Realtime Pipe will be responsible for sending the data. @@ -194,7 +194,7 @@ Example Output of `SHOW PIPES`: Example: -In V2.0.8-beta and later versions, create a full data synchronization task and view the task details. +In V2.0.8 and later versions, create a full data synchronization task and view the task details. ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') 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 834b3ed94..bb7f21e18 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-beta. +> This feature is supported starting from v2.0.8. **Syntax**: @@ -371,7 +371,7 @@ IoTDB> SHOW AVAILABLE URLS **Description**: Returns service information (MQTT service, REST service) on all active DataNodes (in RUNNING or READ-ONLY state) in the current cluster. -> Supported since V2.0.8-beta +> Supported since V2.0.8 #### Syntax: ```sql diff --git a/src/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md b/src/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md index cc9c798b9..768d0343c 100644 --- a/src/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md +++ b/src/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md @@ -80,7 +80,7 @@ The name of the view, which follows the same rules as a table name (for specific * If a device in the tree model does not contain certain declared FIELD columns, or if their data types are inconsistent with the declared FIELD columns, the value for that FIELD column will always be `NULL`when querying that device. * If no FIELD columns are specified, the system automatically scans for all measurements under the `prefixPath`subtree (including all ordinary sequence measurements and measurements defined in any templates whose mounted paths overlap with the `prefixPath`) during creation. The column names will use the measurement names from the tree model. * The tree model cannot have measurements with the same name (case-insensitive) but different data types. -* `TIME`: When creating a view, you do not need to specify a time column. IoTDB automatically adds a column named "time" and places it as the first column. Since version V2.0.8-beta, views support **custom naming of the time column** during creation. The order of the custom time column in the view is determined by the order in the creation SQL. The related constraints are as follows: +* `TIME`: When creating a view, you do not need to specify a time column. IoTDB automatically adds a column named "time" and places it as the first column. Since version V2.0.8, views support **custom naming of the time column** during creation. The order of the custom time column in the view is determined by the order in the creation SQL. The related constraints are as follows: * When the column category is set to `TIME`, the data type must be `TIMESTAMP`. * Each view allows at most one time column (columnCategory = TIME). * If no time column is explicitly defined, no other column can use `time` as its name to avoid conflicts with the system's default time column naming. @@ -143,7 +143,7 @@ with (ttl=604800000) AS root.db.** ``` -When customizing the time column (supported since V2.0.8-beta), the SQL changes are as follows: +When customizing the time column (supported since V2.0.8), the SQL changes are as follows: ```SQL CREATE OR REPLACE VIEW viewdb."wind_turbine" diff --git a/src/UserGuide/latest/API/Programming-Python-Native-API_apache.md b/src/UserGuide/latest/API/Programming-Python-Native-API_apache.md index b0d43b4ac..b77fe093d 100644 --- a/src/UserGuide/latest/API/Programming-Python-Native-API_apache.md +++ b/src/UserGuide/latest/API/Programming-Python-Native-API_apache.md @@ -557,7 +557,7 @@ session.close() df = ... ``` -**Since V2.0.8-beta**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: +**Since V2.0.8**, `SessionDataSet` provides methods for batch DataFrame retrieval to efficiently handle large-volume queries: ```python # Batch DataFrame retrieval 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 e11e3f9a5..137a44225 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-beta. +- IoTDB Version: >= V2.0.8. ## 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 769c49f0a..41dcd291e 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-beta. +- TimechoDB Version: >= V2.0.8. ## 3. Installation, Deployment, and Usage diff --git a/src/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md b/src/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md index 7a39c6250..e0c3142d0 100644 --- a/src/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md +++ b/src/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,38 @@ --> # Release History +## V2.0.8 + +> Release Date: 2026.04.14 + +V2.0.8 expands AI model capabilities by adding support for Chronos-2, one of the mainstream time-series foundation models, while enabling concurrent inference for built-in large models. On the database side, TIME columns now support custom naming, data synchronization path configuration flexibility has been optimized, and comprehensive improvements have been made to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Query Module**: Added functionality to display the list of available DataNode nodes +* **Query Module**: Added system table for统计查询延迟信息 in the table model +* **Query Module**: Python SessionDataset now supports converting TsBlock to DataFrame and returning DataFrames in batches +* **Storage Module**: TIME column now supports custom column naming +* **Storage Module**: Added SQL support for viewing the complete definition statements of created tables/views +* **Stream Processing Module**: Pipe synchronization now supports excluding specified devices/measurement points from synchronization +* **Stream Processing Module**: Multiple exact paths can now be specified in a single Pipe +* **Stream Processing Module**: When filtering paths in Pipe, `source.pattern` and `source.path` parameters can now be used together with comma separation +* **AI Module**: Built-in Chronos-2 model with prediction support +* **AI Module**: Timer-XL and Sundial built-in models now support concurrent inference +* **System Module**: Added system table for displaying DataNode node connection status in the table model +* **Miscellaneous**: Fixed security vulnerabilities CVE-2025-12183, CVE-2025-66566, and CVE-2025-11226 + +## V2.0.7 + +> Release Date: 2026.03.04 + +V2.0.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V2.0.6 > Release Date: 2026.01.20 @@ -134,6 +166,19 @@ V2.0.1-beta introduces dual tree-table model configuration, supporting standard * ​**​Ecosystem Integration​**​: * Kubernetes Operator support +## V1.3.7 + +> Release Date: 2026.03.04 + +V1.3.7 focuses on security hardening and stability optimization. It removes high-risk RPC interfaces and JEXL functions, strengthens naming convention validation and service address configuration logic, optimizes the automatic deletion mechanism for partitioned tables, and provides comprehensive improvements to database monitoring, performance, and stability. The specific release contents are as follows: + +* **Miscellaneous**: Removed high-risk RPC interfaces +* **Miscellaneous**: Removed JEXL functions +* **Miscellaneous**: Added naming合法性校验 when creating Pipe +* **Miscellaneous**: Changed the default client RPC service address to 127.0.0.1 +* **Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address + + ## V1.3.6 > Release Date: 2026.01.20 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 932c08135..8e1f0cdfc 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-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`) | +| `-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`) | | `-help` | `--help` | Display help information. | No | - | ### 2.2 CSV Format diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md index 863eb9a5a..0f0a73962 100644 --- a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md @@ -125,7 +125,7 @@ WITH SINK ( **Note**: -Starting from V2.0.8-beta, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: +Starting from V2.0.8, when creating a full data synchronization Pipe (e.g. Pipeid: `alldatapipe`), the system will automatically split it into two independent Pipes: * History Pipe: The PipeId is the original name plus the suffix `_history` (e.g. `alldatapipe_history`). The source parameter carries the default configurations: `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` * Realtime Pipe: The PipeId is the original name plus the suffix `_realtime` (e.g. `alldatapipe_realtime`). The source parameter carries the default configuration: `'history.enable'='false'`. If metadata synchronization is configured, the Realtime Pipe will be responsible for sending the data. @@ -198,7 +198,7 @@ The meanings of each column are as follows: Example: -In V2.0.8-beta and later versions, create a full data synchronization task and view the task details. +In V2.0.8 and later versions, create a full data synchronization task and view the task details. ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') @@ -521,12 +521,12 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1 | inclusion | Used to specify the range of data to be synchronized in the data synchronization task, including data, schema, and auth | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | Optional | data.insert | | inclusion.exclusion | Used to exclude specific operations from the range specified by inclusion, reducing the amount of data synchronized | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | Optional | - | | mode.streaming | Specifies the capture source for time-series data writes. Applicable when mode.streamingis false, determining the source for capturing data.insertspecified in inclusion. Offers two strategies:- true: ​​Dynamic capture selection.​​ The system adaptively chooses between capturing individual write requests or only TsFile sealing requests based on downstream processing speed. Prioritizes capturing write requests for lower latency when processing is fast; captures only file sealing requests to avoid backlog when slow. Suitable for most scenarios, balancing latency and throughput optimally.- false: ​​Fixed batch capture.​​ Captures only TsFile sealing requests. Suitable for resource-constrained scenarios to reduce system load. Note: The snapshot data captured upon pipe startup is only provided to downstream processing in file format. | Boolean: true / false | Optional | true | -| mode.strict | Determines the strictness when filtering data using time/ path/ database-name/ table-nameparameters:- true: ​​Strict filtering.​​ The system strictly filters captured data according to the given conditions, ensuring only matching data is selected.- false: ​​Non-strict filtering.​​ The system may include some extra data during filtering. Suitable for performance-sensitive scenarios to reduce CPU and I/O consumption. | Boolean: true / false | Optional | true | -| mode.snapshot | Determines the capture mode for time-series data, affecting the dataspecified in inclusion. Offers two modes:- true: ​​Static data capture.​​ Upon pipe startup, a one-time data snapshot is captured. ​​The pipe will automatically terminate (DROP PIPE SQL is executed automatically) after the snapshot data is fully consumed.​​- false: ​​Dynamic data capture.​​ In addition to capturing a snapshot upon startup, the pipe continuously captures subsequent data changes. The pipe runs continuously to handle the dynamic data stream. | Boolean: true / false | Optional | false | -| path | Can be specified when the user connects with sql_dialectset to tree. For upgraded user pipes, the default sql_dialectis tree. This parameter determines the capture scope for time-series data, affecting the dataspecified in inclusion, as well as some sequence-related metadata. Data is selected into the streaming pipe if its tree model path matches the specified path.
Starting from version V2.0.8-beta, this parameter supports specifying multiple exact paths in a single pipe, e.g., `'path'='root.test.d0.s1,root.test.d0.s2,root.test.d0.s3'`. | String: IoTDB-standard tree path pattern, wildcards allowed | Optional | root.** | -| start-time | The start event time for synchronizing all data, including start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MIN_VALUE | -| end-time | The end event time for synchronizing all data, including end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MAX_VALUE | -| forwarding-pipe-requests | Whether to forward data written by other Pipes (usually data synchronization) | Boolean: true /false | Optional | true | +| mode.strict | Determines the strictness when filtering data using time/ path/ database-name/ table-nameparameters:- true: ​​Strict filtering.​​ The system strictly filters captured data according to the given conditions, ensuring only matching data is selected.- false: ​​Non-strict filtering.​​ The system may include some extra data during filtering. Suitable for performance-sensitive scenarios to reduce CPU and I/O consumption. | Boolean: true / false | Optional | true | +| mode.snapshot | Determines the capture mode for time-series data, affecting the dataspecified in inclusion. Offers two modes:- true: ​​Static data capture.​​ Upon pipe startup, a one-time data snapshot is captured. ​​The pipe will automatically terminate (DROP PIPE SQL is executed automatically) after the snapshot data is fully consumed.​​- false: ​​Dynamic data capture.​​ In addition to capturing a snapshot upon startup, the pipe continuously captures subsequent data changes. The pipe runs continuously to handle the dynamic data stream. | Boolean: true / false | Optional | false | +| path | Can be specified when the user connects with sql_dialectset to tree. For upgraded user pipes, the default sql_dialectis tree. This parameter determines the capture scope for time-series data, affecting the dataspecified in inclusion, as well as some sequence-related metadata. Data is selected into the streaming pipe if its tree model path matches the specified path.
Starting from version V2.0.8, this parameter supports specifying multiple exact paths in a single pipe, e.g., `'path'='root.test.d0.s1,root.test.d0.s2,root.test.d0.s3'`. | String: IoTDB-standard tree path pattern, wildcards allowed | Optional | root.** | +| start-time | The start event time for synchronizing all data, including start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MIN_VALUE | +| end-time | The end event time for synchronizing all data, including end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | Optional | Long.MAX_VALUE | +| forwarding-pipe-requests | Whether to forward data written by other Pipes (usually data synchronization) | Boolean: true /false | Optional | true | | mods | Same as mods.enable, whether to send the MODS file for TSFile. | Boolean: true / false | Optional | false | > 💎 **Note:** The difference between the values of true and false for the data extraction mode `mode.streaming` diff --git a/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md index 1ed8b8521..af354af4d 100644 --- a/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.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-beta. +> This feature is supported starting from v2.0.8. **Syntax**: @@ -277,7 +277,7 @@ IoTDB> SHOW AVAILABLE URLS **Description**: Returns service information (MQTT service, REST service) on all active DataNodes (in RUNNING or READ-ONLY state) in the current cluster. -> This feature is supported starting from v2.0.8-beta. +> This feature is supported starting from v2.0.8. #### Syntax: ```sql diff --git a/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md b/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md index d07763cdd..42afb1ded 100644 --- a/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md +++ b/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md @@ -67,24 +67,6 @@ ITableSession接口定义了与IoTDB交互的基本操作，可以执行数据 | executeQueryStatement(String sql, long timeoutInMs) | 执行查询SQL语句，并设置查询超时时间（以毫秒为单位） | sql: 要执行的查询SQL语句。timeoutInMs: 查询超时时间（毫秒） | SessionDataSet | StatementExecutionException | | close() | 关闭会话，释放所持有的资源 | 无 | 无 | IoTDBConnectionException | -**关于 Object 数据类型的说明：** - -自 V2.0.8-beta 起，`iTableSession.insert(Tablet tablet)`接口支持将单个 Object 类文件拆成多段后按顺序分段写入。当 Tablet 数据结构中列数据类型为 **`TSDataType.Object`​ ​**时，需要使用如下方法向 Tablet 填值。 - -```Java -/* -rowIndex：tablet 行位置 -columnIndex：tablet 列位置 -isEOF：本次写入内容是否为 Object 文件的最后一部分 -offset：本次写入的内容在 Object 文件中的起始偏移量 -content：本次写入的文件内容 -写入时需要确保分段的多个 byte[] 总长度与原始 Object 大小相等，否则会导致写入的数据大小不正确 -*/ -void addValue(int rowIndex, int columnIndex, boolean isEOF, long offset, byte[] content) -``` - -查询时，支持通过`Field.getStringValue`、`Field.getObjectValue`、`SessionDataSet.DataIterator.getObject`、`SessionDataSet.DataIterator.getString` 四种方法进行获取，其返回内容均为以 (Object) 开头且以对象大小结尾的字符串（String 类型），形如：(Object) XX.XX KB 。 - #### 3.1.3 接口展示 diff --git a/src/zh/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md b/src/zh/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md index e19a376a4..dd527d31c 100644 --- a/src/zh/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md +++ b/src/zh/UserGuide/Master/Table/API/Programming-Python-Native-API_apache.md @@ -47,7 +47,7 @@ TableSession是IoTDB的一个核心类，用于与IoTDB数据库进行交互。 | execute_query_statement | 执行查询 SQL 语句并返回结果集 | sql: str | SessionDataSet | | close | 关闭会话并释放资源 | None | None | -自 V2.0.8-beta 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： +自 V2.0.8 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： ```python # 分批获取 DataFrame diff --git a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md index 0a2ab4366..f85ef79f8 100644 --- a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md +++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md @@ -33,8 +33,6 @@ IoTDB 支持以下十种数据类型： * TEXT（长字符串，不推荐使用） * STRING（字符串） * BLOB（大二进制对象） -* OBJECT（大二进制对象） - > V2.0.8-beta 版本起支持 * TIMESTAMP（时间戳） * DATE（日期） diff --git a/src/zh/UserGuide/Master/Table/Basic-Concept/Table-Management_apache.md b/src/zh/UserGuide/Master/Table/Basic-Concept/Table-Management_apache.md index ea6c1559a..41d46a331 100644 --- a/src/zh/UserGuide/Master/Table/Basic-Concept/Table-Management_apache.md +++ b/src/zh/UserGuide/Master/Table/Basic-Concept/Table-Management_apache.md @@ -67,7 +67,7 @@ comment **说明：** 1. 在创建表时，可以不指定时间列（TIME），IoTDB会自动添加该列并命名为"time"， 且顺序上位于第一列。其他所有列可以通过在数据库配置时启用`enable_auto_create_schema`选项，或通过 session 接口自动创建或修改表的语句来添加。 -2. 自 V2.0.8-beta 版本起，支持创建表时自定义命名时间列，自定义时间列在表中的顺序由创建 SQL 中的顺序决定。相关约束如下： +2. 自 V2.0.8 版本起，支持创建表时自定义命名时间列，自定义时间列在表中的顺序由创建 SQL 中的顺序决定。相关约束如下： - 当列分类（columnCategory）设为 TIME 时，数据类型（dataType）必须为 TIMESTAMP。 - 每张表最多允许定义 1个时间列（columnCategory = TIME）。 - 当未显式定义时间列时，不允许其他列使用 time 作为名称，否则会与系统默认时间列命名冲突。 diff --git a/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md b/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md index ce5d55fdc..6636c1530 100644 --- a/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md +++ b/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md @@ -302,59 +302,6 @@ It costs 0.014s * 对目标表具有`WRITE`权限。 * 更多用户权限相关的内容，请参考[权限管理](../User-Manual/Authority-Management_apache.md)。 -### 1.7 Object 类型写入 - -自为了避免单个 Object 过大导致写入请求过大，Object 类型的值支持拆分后按顺序分段写入。SQL 中需要使用 `to_object(isEOF, offset, content)` 函数进行值填充。 - -> V2.0.8-beta 版本起支持 - -**语法：** - -```SQL -insert into tableName(time, columnName) values(timeValue, to_object(isEOF, offset, content)); -``` - -**参数：** - -| 名称 | 数据类型 | 描述 | -| --------- | ------------------- | ---------------------------------------- | -| isEOF | boolean | 本次写入内容是否为 Object 的最后一部分 | -| offset | int64 | 本次写入的内容在 Object 中的起始偏移量 | -| content | 十六进制(hex)格式 | 本次写入的 Object 内容 | - -**示例：** - -向表 table1 中增加 object 类型字段 s1 - -```SQL -ALTER TABLE table1 ADD COLUMN IF NOT EXISTS s1 OBJECT FIELD COMMENT 'object类型'; -``` - -1. 不分段写入 - -```SQL -insert into table1(time, device_id, s1) values(now(), 'tag1', to_object(true, 0, X'696F746462')); -``` - -2. 分段写入 - -```SQL ---分段写入 object 数据; ---第一次写入：to_object(false, 0, X'696F'); -insert into table1(time, device_id, s1) values(1, 'tag1', to_object(false, 0, X'696F')); ---第二次写入：to_object(false, 2, X'7464'); -insert into table1(time, device_id, s1) values(1, 'tag1', to_object(false, 2, X'7464')); ---第三次写入：to_object(true, 4, X'62'); -insert into table1(time, device_id, s1) values(1, 'tag1', to_object(true, 4, X'62')); -``` - -**注意：** - -1. 如果某个 Object 值只写入了部分片段，查询该 Object 值时会显示 null，只有写入完全后才能查询到数据 -2. 分段写入时，如果本次写入的 offset 不等于已写入的 Object 大小，本次写入报错 -3. 如果已写入了部分数据，本次写入的 offset 为 0，本次写入会清除之前已写入的数据部分，重新写入新的数据 - - ## 2. 数据更新 diff --git a/src/zh/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md b/src/zh/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md index 30c0d1d4c..dde4a7a00 100644 --- a/src/zh/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md +++ b/src/zh/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,39 @@ --> # 发布历史 +## V2.0.8 + +> 发版时间：2026.04.14 + +V2.0.8 版本在 AI 模型能力上扩充了对现有主流时序大模型之一 Chronos-2 的支持，同时内置大模型支持并发推理能力。在数据库方面，TIME 列支持自定义命名，优化数据同步路径配置的灵活性，并对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 查询模块：新增可用 DataNode 节点的列表展示功能 +* 查询模块：新增系统表，用于在表模型中统计查询延迟信息 +* 查询模块：Python SessionDataset 支持将 TsBlock 转换为 DataFrame，并批量返回 DataFrame +* 存储模块：支持为 TIME 时间列自定义列名 +* 存储模块：支持通过 SQL 查看已创建表 / 视图的完整定义语句 +* 流处理模块：Pipe 同步支持排除指定设备 / 测点进行同步 +* 流处理模块：支持在一个 Pipe 中填写多个精确路径的 path +* 流处理模块：Pipe 过滤路径时，支持以逗号分隔，混合使用 source.pattern 与 source.path 参数 +* AI 模块：内置 Chronos-2 模型，支持预测功能 +* AI 模块：Timer-XL、Sundial 内置模型支持并发推理功能 +* 系统模块：新增系统表，用于在表模型中展示 DataNode 节点连接状态 +* 其他：修复安全漏洞 CVE-2025-12183、CVE-2025-66566 及 CVE-2025-11226 + + +## V2.0.7 + +> 发版时间：2026.03.04 + +V2.0.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + + ## V2.0.6 > 发版时间：2026.01.20 @@ -117,6 +150,18 @@ V2.0.1-beta 主要新增了树表双模型配置，并配合表模型支持标 - 脚本与工具：import-data/export-data 脚本迭代，同时兼容 TsFile、CSV 和 SQL 三种类型数据的导入导出 - 生态集成：支持 Kubernetes Operator +## V1.3.7 + +> 发版时间：2026.03.04 + +V1.3.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V1.3.6 > 发版时间：2026.01.20 diff --git a/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md b/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md index d5e203b4f..eacc9610f 100644 --- a/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md +++ b/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual_apache.md @@ -1789,24 +1789,6 @@ IoTDB 配置文件位于 IoTDB 安装目录：`conf`文件夹下。 | 默认值 | -1 | | 改后生效方式 | 重启服务生效 | -* max_object_file_size_in_byte - -| 名字 | max\_object\_file\_size\_in\_byte | -| -------------- |-----------------------------------| -| 描述 | 单对象文件的最大尺寸限制 （V2.0.8-beta 版本起支持） | -| 类型 | long | -| 默认值 | 4294967296 | -| 改后生效方式 | 热加载 | - -* restrict_object_limit - -| 名字 | restrict\_object\_limit | -|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 描述 | 对 OBJECT 类型的表名、列名和设备名称没有特殊限制。（V2.0.8-beta 版本起支持）当设置为 true 且表中包含 OBJECT 列时，需遵循以下限制：
1. 命名规范：TAG 列的值、表名和字段名禁止使用 “.” 或 “..”，且不得包含 “./” 或 “.\” 字符，否则元数据创建将失败。若名称包含文件系统不支持的字符，则会在数据写入时报错。
2. 大小写敏感：如果底层文件系统不区分大小写，则设备标识符（如 'd1' 与 'D1'）将被视为相同。在此情况下，若创建此类名称相似的设备，其 OBJECT 数据文件可能互相覆盖，导致数据错误。
3. 存储路径：OBJECT 类型数据的实际存储路径格式为：`${dataregionid}/${tablename}/${tag1}/${tag2}/.../${field}/${timestamp}.bin`。 | -| 类型 | boolean | -| 默认值 | false | -| 改后生效方式 | 仅允许在第一次启动服务前修改 | - ### 3.20 合并配置 diff --git a/src/zh/UserGuide/Master/Table/Reference/System-Tables_apache.md b/src/zh/UserGuide/Master/Table/Reference/System-Tables_apache.md index 44079527f..e1ad8b5f3 100644 --- a/src/zh/UserGuide/Master/Table/Reference/System-Tables_apache.md +++ b/src/zh/UserGuide/Master/Table/Reference/System-Tables_apache.md @@ -370,7 +370,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS 表 -> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8-beta 版本开始不再提供 +> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8 版本开始不再提供 * 包含数据库内所有的模型信息 * 表结构如下表所示： @@ -590,7 +590,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 包含集群中所有连接。 * 表结构如下表所示： @@ -617,7 +617,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT\_QUERIES 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 包含所有执行结束时间在 `[now() - query_cost_stat_window, now())` 范围内的所有查询，也包括当前正在执行的查询。其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： @@ -648,7 +648,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES\_COSTS\_HISTOGRAM 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 包含过去 `query_cost_stat_window` 时间内的查询耗时的直方图（仅统计已经执行结束的 SQL），其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： @@ -681,7 +681,7 @@ IoTDB> select * from information_schema.queries_costs_histogram limit 10 ``` ### 2.21 SERVICES 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 可展示所有正常工作（RUNNING 或 READ-ONLY） DN 上的服务（MQTT 服务、REST 服务）。 * 表结构如下表所示： diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md b/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md index a3e47d977..78febd1b0 100644 --- a/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md +++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md @@ -1272,7 +1272,7 @@ coalesce(value1, value2[, ...]) #### 8.1.1 cast(value AS type) → type 1. 显式地将一个值转换为指定类型。 -2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型，V2.0.8-beta 版本起支持 OBJECT 类型强转成 STRING 类型。 +2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型。 3. 如果转换失败，将抛出运行时错误。 示例： diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md b/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md index e30a96346..20abca659 100644 --- a/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md +++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md @@ -695,44 +695,3 @@ IoTDB> SELECT window_start, window_end, stock_id, avg(price) as avg FROM CUMULAT +-----------------------------+-----------------------------+--------+------------------+ ``` -## 4. Object 类型读取函数 - -描述：用于读取 OBJECT 对象的二进制内容。返回 BLOB 类型（对象的二进制内容）。 -> V2.0.8-beta 版本起支持 - -语法： - -```SQL -READ_OBJECT(object [, offset, length]) -``` - -参数： - -* 必选参数：`object`，类型为 OBJECT -* 可选参数： - * `offset`，类型为 long（int64），为读取的偏移量，缺省值为0。如果 offset 小于 0，或者大于等于全文件长度，则抛异常 - * `length`，类型为 long（int64），为读取的数据长度，缺省值为全文件长度 - * 当长度大于 2^31 - 1 时，报错 - * 当长度大于从 offset 起的剩余文件长度时，会取从 offset 起的文件内容 - * length 小于 0 时，视为读取 offset 开始 object 剩下的所有数据 - -示例： - -```SQL -IoTDB:database1> select READ_OBJECT(s1) from table1 where device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 - - -IoTDB:database1> select READ_OBJECT(s1, 0, 3) from table1 where device_id = 'tag1' -+--------+ -| _col0| -+--------+ -|0x696f74| -+--------+ -Total line number = 1 -``` diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md b/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md index 00efaff14..4793ddd1f 100644 --- a/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md +++ b/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Maintenance-Statements_apache.md @@ -228,7 +228,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md b/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md index 940eddc93..6eb4883c6 100644 --- a/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md +++ b/src/zh/UserGuide/Master/Table/SQL-Manual/SQL-Metadata-Operations_apache.md @@ -212,7 +212,7 @@ CREATE TABLE tableC ( temperature int32 FIELD COMMENT 'temperature' ) with (TTL=DEFAULT); --- 自定义时间列:命名为time_test, 位于表的第二列 (V2.0.8-beta 起支持） +-- 自定义时间列:命名为time_test, 位于表的第二列 (V2.0.8 起支持） CREATE TABLE table1 ( region STRING TAG, time_user_defined TIMESTAMP TIME, diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md b/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md index a1ede9228..ae6473613 100644 --- a/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md +++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause_apache.md @@ -267,37 +267,6 @@ Total line number = 18 It costs 0.189s ``` -#### 3.1.4 Object 类型查询 - -> V2.0.8-beta 版本起支持 - -示例一：直接查询 object 类型数据 - -```SQL -IoTDB:database1> select s1 from table1 where device_id = 'tag1' -+------------+ -| s1| -+------------+ -|(Object) 5 B| -+------------+ -Total line number = 1 -It costs 0.428s -``` - -示例二：通过 read\_object 函数查询 Object 类型数据的真实内容 - -```SQL -IoTDB:database1> select read_object(s1) from table1 where device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 -It costs 0.188s -``` - - ### 3.2 Columns 函数 1. 不结合表达式 diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md b/src/zh/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md index e8adddc86..2e6615ed2 100644 --- a/src/zh/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md +++ b/src/zh/UserGuide/Master/Table/User-Manual/Audit-Log_timecho.md @@ -32,7 +32,7 @@ * 可通过参数设置统计任意时间段内写入和查询延时大于阈值（默认3000毫秒）的慢请求个数。 * 审计日志文件默认加密存储 -> 注意：该功能从 V2.0.8-beta 版本开始提供。 +> 注意：该功能从 V2.0.8 版本开始提供。 ## 2. 配置参数 diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md index cb872116b..4eadd15fa 100644 --- a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md @@ -117,7 +117,7 @@ WITH SINK ( **IF NOT EXISTS 语义**：用于创建操作中，确保当指定 Pipe 不存在时，执行创建命令，防止因尝试创建已存在的 Pipe 而导致报错。 -**注意**：V2.0.8-beta 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： +**注意**：V2.0.8 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： * 历史 Pipe：PipeId 为原名称加 _history后缀（如 `alldatapipe_history`），source 参数默认携带 `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` @@ -192,7 +192,7 @@ SHOW PIPE 示例： -在 V2.0.8-beta 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 +在 V2.0.8 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md index 6dee9a2ec..36b6f61a2 100644 --- a/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md @@ -340,7 +340,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： @@ -370,7 +370,7 @@ IoTDB> SHOW AVAILABLE URLS **含义**：返回当前集群所有正常工作（RUNNING 或 READ-ONLY） DN 上的服务信息（MQTT 服务、REST 服务）。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md b/src/zh/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md index 4465dc555..20a99f346 100644 --- a/src/zh/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md +++ b/src/zh/UserGuide/Master/Table/User-Manual/Tree-to-Table_apache.md @@ -79,7 +79,7 @@ comment * 若树模型中的设备不包含某些声明的 FIELD 列，或与声明的 FIELD 列的数据类型不一致，则在查询该设备时，该 FIELD 列的值永远为 NULL。 * 若未指定 FIELD 列，则创建时会自动扫描出`prefixPath`子树下所有的测点（包括定义为所有普通序列的测点，以及挂载路径与 `prefixPath `有所重合的所有模板中的测点），列名使用树模型测点名称。 * 不支持树模型存在名称（含小写）相同但类型不同的测点 -* `TIME`：创建视图时可以不指定时间列（TIME），IoTDB 会自动添加该列并命名为"time"， 且顺序上位于第一列。自 V2.0.8-beta 版本起，支持创建视图时**自定义命名时间列**，自定义时间列在视图中的顺序由创建 SQL 中的顺序决定。相关约束如下： +* `TIME`：创建视图时可以不指定时间列（TIME），IoTDB 会自动添加该列并命名为"time"， 且顺序上位于第一列。自 V2.0.8 版本起，支持创建视图时**自定义命名时间列**，自定义时间列在视图中的顺序由创建 SQL 中的顺序决定。相关约束如下： * 当列分类（columnCategory）设为 `TIME` 时，数据类型（dataType）必须为 `TIMESTAMP`。 * 每个视图最多允许定义 1个时间列（columnCategory = TIME）。 * 当未显式定义时间列时，不允许其他列使用 `time` 作为名称，否则会与系统默认时间列命名冲突。 @@ -139,7 +139,7 @@ AS root.db.** with (ttl=604800000) ``` -* 当需要自定义时间列（V2.0.8-beta 起支持）时，SQL 变更如下： +* 当需要自定义时间列（V2.0.8 起支持）时，SQL 变更如下： ```SQL CREATE OR REPLACE VIEW viewdb."风机表" diff --git a/src/zh/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md b/src/zh/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md index ac5477cc9..d29f2f00f 100644 --- a/src/zh/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md +++ b/src/zh/UserGuide/Master/Tree/API/Programming-Python-Native-API_apache.md @@ -555,7 +555,7 @@ session.close() df = ... ``` -自 V2.0.8-beta 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： +自 V2.0.8 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： ```python # 分批获取 DataFrame diff --git a/src/zh/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md b/src/zh/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md index b43045517..f303f6b6b 100644 --- a/src/zh/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md +++ b/src/zh/UserGuide/Master/Tree/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,37 @@ --> # 发布历史 +## V2.0.8 + +> 发版时间：2026.04.14 + +V2.0.8 版本在 AI 模型能力上扩充了对现有主流时序大模型之一 Chronos-2 的支持，同时内置大模型支持并发推理能力。在数据库方面，TIME 列支持自定义命名，优化数据同步路径配置的灵活性，并对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 查询模块：新增可用 DataNode 节点的列表展示功能 +* 查询模块：新增系统表，用于在表模型中统计查询延迟信息 +* 查询模块：Python SessionDataset 支持将 TsBlock 转换为 DataFrame，并批量返回 DataFrame +* 存储模块：支持为 TIME 时间列自定义列名 +* 存储模块：支持通过 SQL 查看已创建表 / 视图的完整定义语句 +* 流处理模块：Pipe 同步支持排除指定设备 / 测点进行同步 +* 流处理模块：支持在一个 Pipe 中填写多个精确路径的 path +* 流处理模块：Pipe 过滤路径时，支持以逗号分隔，混合使用 source.pattern 与 source.path 参数 +* AI 模块：内置 Chronos-2 模型，支持预测功能 +* AI 模块：Timer-XL、Sundial 内置模型支持并发推理功能 +* 系统模块：新增系统表，用于在表模型中展示 DataNode 节点连接状态 +* 其他：修复安全漏洞 CVE-2025-12183、CVE-2025-66566 及 CVE-2025-11226 + +## V2.0.7 + +> 发版时间：2026.03.04 + +V2.0.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V2.0.6 > 发版时间：2026.01.20 @@ -118,6 +149,18 @@ V2.0.1-beta 主要新增了树表双模型配置，并配合表模型支持标 - 脚本与工具：import-data/export-data 脚本迭代，同时兼容 TsFile、CSV 和 SQL 三种类型数据的导入导出 - 生态集成：支持 Kubernetes Operator +## V1.3.7 + +> 发版时间：2026.03.04 + +V1.3.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V1.3.6 > 发版时间：2026.01.20 diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md b/src/zh/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md index 4897871d2..cfc2e0fe0 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Audit-Log_timecho.md @@ -32,7 +32,7 @@ * 可通过参数设置统计任意时间段内写入和查询延时大于阈值（默认3000毫秒）的慢请求个数。 * 审计日志文件默认加密存储 -> 注意：该功能从 V2.0.8-beta 版本开始提供。 +> 注意：该功能从 V2.0.8 版本开始提供。 ## 2. 配置参数 diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md index ffacb90d6..750765fe3 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md @@ -122,7 +122,7 @@ WITH SINK ( **IF NOT EXISTS 语义**：用于创建操作中，确保当指定 Pipe 不存在时，执行创建命令，防止因尝试创建已存在的 Pipe 而导致报错。 -**注意**：V2.0.8-beta 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： +**注意**：V2.0.8 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： * 历史 Pipe：PipeId 为原名称加 _history后缀（如 `alldatapipe_history`），source 参数默认携带 `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` @@ -198,7 +198,7 @@ SHOW PIPE 示例： -在 V2.0.8-beta 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 +在 V2.0.8 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') @@ -511,19 +511,19 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1 ### 5.1 source 参数 -| 参数 | 描述 | value 取值范围 | 是否必填 | 默认取值 | -|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| -------- | -------------- | -| source | iotdb-source | String: iotdb-source | 必填 | - | -| inclusion | 用于指定数据同步任务中需要同步范围，分为数据、元数据和权限 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | data.insert | -| inclusion.exclusion | 用于从 inclusion 指定的同步范围内排除特定的操作，减少同步的数据量 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | 空字符串 | +| 参数 | 描述 | value 取值范围 | 是否必填 | 默认取值 | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| -------- | -------------- | +| source | iotdb-source | String: iotdb-source | 必填 | - | +| inclusion | 用于指定数据同步任务中需要同步范围，分为数据、元数据和权限 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | data.insert | +| inclusion.exclusion | 用于从 inclusion 指定的同步范围内排除特定的操作，减少同步的数据量 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | 空字符串 | | mode.streaming | 此参数指定时序数据写入的捕获来源。适用于 `mode.streaming`为 `false` 模式下的场景，决定`inclusion`中`data.insert`数据的捕获来源。提供两种捕获策略：true： 动态选择捕获的类型。系统将根据下游处理速度，自适应地选择是捕获每个写入请求还是仅捕获 TsFile 文件的封口请求。当下游处理速度快时，优先捕获写入请求以减少延迟；当处理速度慢时，仅捕获文件封口请求以避免处理堆积。这种模式适用于大多数场景，能够实现处理延迟和吞吐量的最优平衡。false：固定按批捕获方式。仅捕获 TsFile 文件的封口请求，适用于资源受限的应用场景，以降低系统负载。注意，pipe 启动时捕获的快照数据只会以文件的方式供下游处理。 | Boolean: true / false | 否 | true | -| mode.strict | 在使用 time / path / database-name / table-name 参数过滤数据时，是否需要严格按照条件筛选：`true`： 严格筛选。系统将完全按照给定条件过滤筛选被捕获的数据，确保只有符合条件的数据被选中。`false`：非严格筛选。系统在筛选被捕获的数据时可能会包含一些额外的数据，适用于性能敏感的场景，可降低 CPU 和 IO 消耗。 | Boolean: true / false | 否 | true | -| mode.snapshot | 此参数决定时序数据的捕获方式，影响`inclusion`中的`data`数据。提供两种模式：`true`：静态数据捕获。启动 pipe 时，会进行一次性的数据快照捕获。当快照数据被完全消费后，**pipe 将自动终止（DROP PIPE SQL 会自动执行）**。`false`：动态数据捕获。除了在 pipe 启动时捕获快照数据外，还会持续捕获后续的数据变更。pipe 将持续运行以处理动态数据流。 | Boolean: true / false | 否 | false | -| path | 当用户连接指定的sql_dialect为tree时可以指定。对于升级上来的用户pipe,默认sql_dialect为tree。此参数决定时序数据的捕获范围,影响 inclusion中的data数据,以及部分序列相关的元数据。当数据的树模型路径能够被path匹配时，数据会被筛选出来进入流处理pipe。
自 V2.0.8-beta 版本起，该参数支持在一个pipe中填写多个精确路径的path , 如 `'path'='root.test.d0,s1,root.test.d0.s2,root.test.d0.s3'` | String:IoTDB标准的树路径模式,可以带通配符 | 选填 | root.** | -| start-time | 同步所有数据的开始 event time，包含 start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MIN_VALUE | -| end-time | 同步所有数据的结束 event time，包含 end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MAX_VALUE | -| forwarding-pipe-requests | 是否转发由其他 Pipe （通常是数据同步）写入的数据 | Boolean: true, false | 选填 | true | -| mods | 同 mods.enable，是否发送 tsfile 的 mods 文件 | Boolean: true / false | 选填 | false | +| mode.strict | 在使用 time / path / database-name / table-name 参数过滤数据时，是否需要严格按照条件筛选：`true`： 严格筛选。系统将完全按照给定条件过滤筛选被捕获的数据，确保只有符合条件的数据被选中。`false`：非严格筛选。系统在筛选被捕获的数据时可能会包含一些额外的数据，适用于性能敏感的场景，可降低 CPU 和 IO 消耗。 | Boolean: true / false | 否 | true | +| mode.snapshot | 此参数决定时序数据的捕获方式，影响`inclusion`中的`data`数据。提供两种模式：`true`：静态数据捕获。启动 pipe 时，会进行一次性的数据快照捕获。当快照数据被完全消费后，**pipe 将自动终止（DROP PIPE SQL 会自动执行）**。`false`：动态数据捕获。除了在 pipe 启动时捕获快照数据外，还会持续捕获后续的数据变更。pipe 将持续运行以处理动态数据流。 | Boolean: true / false | 否 | false | +| path | 当用户连接指定的sql_dialect为tree时可以指定。对于升级上来的用户pipe,默认sql_dialect为tree。此参数决定时序数据的捕获范围,影响 inclusion中的data数据,以及部分序列相关的元数据。当数据的树模型路径能够被path匹配时，数据会被筛选出来进入流处理pipe。
自 V2.0.8 版本起，该参数支持在一个pipe中填写多个精确路径的path , 如 `'path'='root.test.d0,s1,root.test.d0.s2,root.test.d0.s3'` | String:IoTDB标准的树路径模式,可以带通配符 | 选填 | root.** | +| start-time | 同步所有数据的开始 event time，包含 start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MIN_VALUE | +| end-time | 同步所有数据的结束 event time，包含 end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MAX_VALUE | +| forwarding-pipe-requests | 是否转发由其他 Pipe （通常是数据同步）写入的数据 | Boolean: true, false | 选填 | true | +| mods | 同 mods.enable，是否发送 tsfile 的 mods 文件 | Boolean: true / false | 选填 | false | > 💎 **说明：数据抽取模式 mode.streaming 取值 true 和 false 的差异** > - **true（推荐）**：该取值下，任务将对数据进行实时处理、发送，其特点是高时效、低吞吐 diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md index 1cba1564c..012236f2f 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md @@ -248,7 +248,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： @@ -278,7 +278,7 @@ IoTDB> SHOW AVAILABLE URLS **含义**：返回当前集群所有正常工作（RUNNING 或 READ-ONLY） DN 上的服务信息（MQTT 服务、REST 服务）。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md b/src/zh/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md index 53108483b..07f9cdb8f 100644 --- a/src/zh/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md +++ b/src/zh/UserGuide/V1.3.x/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,18 @@ --> # 发版历史 +## V1.3.7 + +> 发版时间：2026.03.04 + +V1.3.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V1.3.6 > 发版时间：2026.01.20 diff --git a/src/zh/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md b/src/zh/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md index 53108483b..07f9cdb8f 100644 --- a/src/zh/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md +++ b/src/zh/UserGuide/dev-1.3/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,18 @@ --> # 发版历史 +## V1.3.7 + +> 发版时间：2026.03.04 + +V1.3.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V1.3.6 > 发版时间：2026.01.20 diff --git a/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md b/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md index d07763cdd..42afb1ded 100644 --- a/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md +++ b/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_apache.md @@ -67,24 +67,6 @@ ITableSession接口定义了与IoTDB交互的基本操作，可以执行数据 | executeQueryStatement(String sql, long timeoutInMs) | 执行查询SQL语句，并设置查询超时时间（以毫秒为单位） | sql: 要执行的查询SQL语句。timeoutInMs: 查询超时时间（毫秒） | SessionDataSet | StatementExecutionException | | close() | 关闭会话，释放所持有的资源 | 无 | 无 | IoTDBConnectionException | -**关于 Object 数据类型的说明：** - -自 V2.0.8-beta 起，`iTableSession.insert(Tablet tablet)`接口支持将单个 Object 类文件拆成多段后按顺序分段写入。当 Tablet 数据结构中列数据类型为 **`TSDataType.Object`​ ​**时，需要使用如下方法向 Tablet 填值。 - -```Java -/* -rowIndex：tablet 行位置 -columnIndex：tablet 列位置 -isEOF：本次写入内容是否为 Object 文件的最后一部分 -offset：本次写入的内容在 Object 文件中的起始偏移量 -content：本次写入的文件内容 -写入时需要确保分段的多个 byte[] 总长度与原始 Object 大小相等，否则会导致写入的数据大小不正确 -*/ -void addValue(int rowIndex, int columnIndex, boolean isEOF, long offset, byte[] content) -``` - -查询时，支持通过`Field.getStringValue`、`Field.getObjectValue`、`SessionDataSet.DataIterator.getObject`、`SessionDataSet.DataIterator.getString` 四种方法进行获取，其返回内容均为以 (Object) 开头且以对象大小结尾的字符串（String 类型），形如：(Object) XX.XX KB 。 - #### 3.1.3 接口展示 diff --git a/src/zh/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md b/src/zh/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md index 92c19afb6..c2fe3336c 100644 --- a/src/zh/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md +++ b/src/zh/UserGuide/latest-Table/API/Programming-Python-Native-API_apache.md @@ -47,7 +47,7 @@ TableSession是IoTDB的一个核心类，用于与IoTDB数据库进行交互。 | execute_query_statement | 执行查询 SQL 语句并返回结果集 | sql: str | SessionDataSet | | close | 关闭会话并释放资源 | None | None | -自 V2.0.8-beta 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： +自 V2.0.8 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： ```python # 分批获取 DataFrame diff --git a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md index 0a2ab4366..f85ef79f8 100644 --- a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md +++ b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md @@ -33,8 +33,6 @@ IoTDB 支持以下十种数据类型： * TEXT（长字符串，不推荐使用） * STRING（字符串） * BLOB（大二进制对象） -* OBJECT（大二进制对象） - > V2.0.8-beta 版本起支持 * TIMESTAMP（时间戳） * DATE（日期） diff --git a/src/zh/UserGuide/latest-Table/Basic-Concept/Table-Management_apache.md b/src/zh/UserGuide/latest-Table/Basic-Concept/Table-Management_apache.md index ea6c1559a..41d46a331 100644 --- a/src/zh/UserGuide/latest-Table/Basic-Concept/Table-Management_apache.md +++ b/src/zh/UserGuide/latest-Table/Basic-Concept/Table-Management_apache.md @@ -67,7 +67,7 @@ comment **说明：** 1. 在创建表时，可以不指定时间列（TIME），IoTDB会自动添加该列并命名为"time"， 且顺序上位于第一列。其他所有列可以通过在数据库配置时启用`enable_auto_create_schema`选项，或通过 session 接口自动创建或修改表的语句来添加。 -2. 自 V2.0.8-beta 版本起，支持创建表时自定义命名时间列，自定义时间列在表中的顺序由创建 SQL 中的顺序决定。相关约束如下： +2. 自 V2.0.8 版本起，支持创建表时自定义命名时间列，自定义时间列在表中的顺序由创建 SQL 中的顺序决定。相关约束如下： - 当列分类（columnCategory）设为 TIME 时，数据类型（dataType）必须为 TIMESTAMP。 - 每张表最多允许定义 1个时间列（columnCategory = TIME）。 - 当未显式定义时间列时，不允许其他列使用 time 作为名称，否则会与系统默认时间列命名冲突。 diff --git a/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md b/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md index ce5d55fdc..6636c1530 100644 --- a/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md +++ b/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_apache.md @@ -302,59 +302,6 @@ It costs 0.014s * 对目标表具有`WRITE`权限。 * 更多用户权限相关的内容，请参考[权限管理](../User-Manual/Authority-Management_apache.md)。 -### 1.7 Object 类型写入 - -自为了避免单个 Object 过大导致写入请求过大，Object 类型的值支持拆分后按顺序分段写入。SQL 中需要使用 `to_object(isEOF, offset, content)` 函数进行值填充。 - -> V2.0.8-beta 版本起支持 - -**语法：** - -```SQL -insert into tableName(time, columnName) values(timeValue, to_object(isEOF, offset, content)); -``` - -**参数：** - -| 名称 | 数据类型 | 描述 | -| --------- | ------------------- | ---------------------------------------- | -| isEOF | boolean | 本次写入内容是否为 Object 的最后一部分 | -| offset | int64 | 本次写入的内容在 Object 中的起始偏移量 | -| content | 十六进制(hex)格式 | 本次写入的 Object 内容 | - -**示例：** - -向表 table1 中增加 object 类型字段 s1 - -```SQL -ALTER TABLE table1 ADD COLUMN IF NOT EXISTS s1 OBJECT FIELD COMMENT 'object类型'; -``` - -1. 不分段写入 - -```SQL -insert into table1(time, device_id, s1) values(now(), 'tag1', to_object(true, 0, X'696F746462')); -``` - -2. 分段写入 - -```SQL ---分段写入 object 数据; ---第一次写入：to_object(false, 0, X'696F'); -insert into table1(time, device_id, s1) values(1, 'tag1', to_object(false, 0, X'696F')); ---第二次写入：to_object(false, 2, X'7464'); -insert into table1(time, device_id, s1) values(1, 'tag1', to_object(false, 2, X'7464')); ---第三次写入：to_object(true, 4, X'62'); -insert into table1(time, device_id, s1) values(1, 'tag1', to_object(true, 4, X'62')); -``` - -**注意：** - -1. 如果某个 Object 值只写入了部分片段，查询该 Object 值时会显示 null，只有写入完全后才能查询到数据 -2. 分段写入时，如果本次写入的 offset 不等于已写入的 Object 大小，本次写入报错 -3. 如果已写入了部分数据，本次写入的 offset 为 0，本次写入会清除之前已写入的数据部分，重新写入新的数据 - - ## 2. 数据更新 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 67c0278cb..7bf4d6d23 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-beta； +* IoTDB 版本：>= V 2.0.8； ## 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 167973563..cee303d62 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-beta； +* TimechoDB 版本：>= V 2.0.8； ## 3. 安装部署及使用 diff --git a/src/zh/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md b/src/zh/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md index 30c0d1d4c..dde4a7a00 100644 --- a/src/zh/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md +++ b/src/zh/UserGuide/latest-Table/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,39 @@ --> # 发布历史 +## V2.0.8 + +> 发版时间：2026.04.14 + +V2.0.8 版本在 AI 模型能力上扩充了对现有主流时序大模型之一 Chronos-2 的支持，同时内置大模型支持并发推理能力。在数据库方面，TIME 列支持自定义命名，优化数据同步路径配置的灵活性，并对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 查询模块：新增可用 DataNode 节点的列表展示功能 +* 查询模块：新增系统表，用于在表模型中统计查询延迟信息 +* 查询模块：Python SessionDataset 支持将 TsBlock 转换为 DataFrame，并批量返回 DataFrame +* 存储模块：支持为 TIME 时间列自定义列名 +* 存储模块：支持通过 SQL 查看已创建表 / 视图的完整定义语句 +* 流处理模块：Pipe 同步支持排除指定设备 / 测点进行同步 +* 流处理模块：支持在一个 Pipe 中填写多个精确路径的 path +* 流处理模块：Pipe 过滤路径时，支持以逗号分隔，混合使用 source.pattern 与 source.path 参数 +* AI 模块：内置 Chronos-2 模型，支持预测功能 +* AI 模块：Timer-XL、Sundial 内置模型支持并发推理功能 +* 系统模块：新增系统表，用于在表模型中展示 DataNode 节点连接状态 +* 其他：修复安全漏洞 CVE-2025-12183、CVE-2025-66566 及 CVE-2025-11226 + + +## V2.0.7 + +> 发版时间：2026.03.04 + +V2.0.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + + ## V2.0.6 > 发版时间：2026.01.20 @@ -117,6 +150,18 @@ V2.0.1-beta 主要新增了树表双模型配置，并配合表模型支持标 - 脚本与工具：import-data/export-data 脚本迭代，同时兼容 TsFile、CSV 和 SQL 三种类型数据的导入导出 - 生态集成：支持 Kubernetes Operator +## V1.3.7 + +> 发版时间：2026.03.04 + +V1.3.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V1.3.6 > 发版时间：2026.01.20 diff --git a/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md b/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md index d5e203b4f..eacc9610f 100644 --- a/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md +++ b/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual_apache.md @@ -1789,24 +1789,6 @@ IoTDB 配置文件位于 IoTDB 安装目录：`conf`文件夹下。 | 默认值 | -1 | | 改后生效方式 | 重启服务生效 | -* max_object_file_size_in_byte - -| 名字 | max\_object\_file\_size\_in\_byte | -| -------------- |-----------------------------------| -| 描述 | 单对象文件的最大尺寸限制 （V2.0.8-beta 版本起支持） | -| 类型 | long | -| 默认值 | 4294967296 | -| 改后生效方式 | 热加载 | - -* restrict_object_limit - -| 名字 | restrict\_object\_limit | -|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 描述 | 对 OBJECT 类型的表名、列名和设备名称没有特殊限制。（V2.0.8-beta 版本起支持）当设置为 true 且表中包含 OBJECT 列时，需遵循以下限制：
1. 命名规范：TAG 列的值、表名和字段名禁止使用 “.” 或 “..”，且不得包含 “./” 或 “.\” 字符，否则元数据创建将失败。若名称包含文件系统不支持的字符，则会在数据写入时报错。
2. 大小写敏感：如果底层文件系统不区分大小写，则设备标识符（如 'd1' 与 'D1'）将被视为相同。在此情况下，若创建此类名称相似的设备，其 OBJECT 数据文件可能互相覆盖，导致数据错误。
3. 存储路径：OBJECT 类型数据的实际存储路径格式为：`${dataregionid}/${tablename}/${tag1}/${tag2}/.../${field}/${timestamp}.bin`。 | -| 类型 | boolean | -| 默认值 | false | -| 改后生效方式 | 仅允许在第一次启动服务前修改 | - ### 3.20 合并配置 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 44079527f..e1ad8b5f3 100644 --- a/src/zh/UserGuide/latest-Table/Reference/System-Tables_apache.md +++ b/src/zh/UserGuide/latest-Table/Reference/System-Tables_apache.md @@ -370,7 +370,7 @@ IoTDB> select * from information_schema.views ### 2.11 MODELS 表 -> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8-beta 版本开始不再提供 +> 该系统表从 V 2.0.5 版本开始提供，从V 2.0.8 版本开始不再提供 * 包含数据库内所有的模型信息 * 表结构如下表所示： @@ -590,7 +590,7 @@ IoTDB> select * from information_schema.data_nodes ### 2.18 CONNECTIONS 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 包含集群中所有连接。 * 表结构如下表所示： @@ -617,7 +617,7 @@ IoTDB> select * from information_schema.connections; ### 2.19 CURRENT\_QUERIES 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 包含所有执行结束时间在 `[now() - query_cost_stat_window, now())` 范围内的所有查询，也包括当前正在执行的查询。其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： @@ -648,7 +648,7 @@ IoTDB> select * from information_schema.current_queries; ### 2.20 QUERIES\_COSTS\_HISTOGRAM 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 包含过去 `query_cost_stat_window` 时间内的查询耗时的直方图（仅统计已经执行结束的 SQL），其中`query_cost_stat_window `代表查询耗时统计的窗口，默认值为 0 ，可通过配置文件`iotdb-system.properties`进行配置。 * 表结构如下表所示： @@ -681,7 +681,7 @@ IoTDB> select * from information_schema.queries_costs_histogram limit 10 ``` ### 2.21 SERVICES 表 -> 该系统表从 V 2.0.8-beta 版本开始提供 +> 该系统表从 V 2.0.8 版本开始提供 * 可展示所有正常工作（RUNNING 或 READ-ONLY） DN 上的服务（MQTT 服务、REST 服务）。 * 表结构如下表所示： diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md b/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md index a3e47d977..b1c772aac 100644 --- a/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md +++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function_apache.md @@ -1272,7 +1272,7 @@ coalesce(value1, value2[, ...]) #### 8.1.1 cast(value AS type) → type 1. 显式地将一个值转换为指定类型。 -2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型，V2.0.8-beta 版本起支持 OBJECT 类型强转成 STRING 类型。 +2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型 3. 如果转换失败，将抛出运行时错误。 示例： diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md b/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md index e30a96346..20abca659 100644 --- a/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md +++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md @@ -695,44 +695,3 @@ IoTDB> SELECT window_start, window_end, stock_id, avg(price) as avg FROM CUMULAT +-----------------------------+-----------------------------+--------+------------------+ ``` -## 4. Object 类型读取函数 - -描述：用于读取 OBJECT 对象的二进制内容。返回 BLOB 类型（对象的二进制内容）。 -> V2.0.8-beta 版本起支持 - -语法： - -```SQL -READ_OBJECT(object [, offset, length]) -``` - -参数： - -* 必选参数：`object`，类型为 OBJECT -* 可选参数： - * `offset`，类型为 long（int64），为读取的偏移量，缺省值为0。如果 offset 小于 0，或者大于等于全文件长度，则抛异常 - * `length`，类型为 long（int64），为读取的数据长度，缺省值为全文件长度 - * 当长度大于 2^31 - 1 时，报错 - * 当长度大于从 offset 起的剩余文件长度时，会取从 offset 起的文件内容 - * length 小于 0 时，视为读取 offset 开始 object 剩下的所有数据 - -示例： - -```SQL -IoTDB:database1> select READ_OBJECT(s1) from table1 where device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 - - -IoTDB:database1> select READ_OBJECT(s1, 0, 3) from table1 where device_id = 'tag1' -+--------+ -| _col0| -+--------+ -|0x696f74| -+--------+ -Total line number = 1 -``` diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md b/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md index 00efaff14..4793ddd1f 100644 --- a/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md +++ b/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Maintenance-Statements_apache.md @@ -228,7 +228,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md b/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md index 940eddc93..6eb4883c6 100644 --- a/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md +++ b/src/zh/UserGuide/latest-Table/SQL-Manual/SQL-Metadata-Operations_apache.md @@ -212,7 +212,7 @@ CREATE TABLE tableC ( temperature int32 FIELD COMMENT 'temperature' ) with (TTL=DEFAULT); --- 自定义时间列:命名为time_test, 位于表的第二列 (V2.0.8-beta 起支持） +-- 自定义时间列:命名为time_test, 位于表的第二列 (V2.0.8 起支持） CREATE TABLE table1 ( region STRING TAG, time_user_defined TIMESTAMP TIME, diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md b/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md index a1ede9228..ae6473613 100644 --- a/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md +++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause_apache.md @@ -267,37 +267,6 @@ Total line number = 18 It costs 0.189s ``` -#### 3.1.4 Object 类型查询 - -> V2.0.8-beta 版本起支持 - -示例一：直接查询 object 类型数据 - -```SQL -IoTDB:database1> select s1 from table1 where device_id = 'tag1' -+------------+ -| s1| -+------------+ -|(Object) 5 B| -+------------+ -Total line number = 1 -It costs 0.428s -``` - -示例二：通过 read\_object 函数查询 Object 类型数据的真实内容 - -```SQL -IoTDB:database1> select read_object(s1) from table1 where device_id = 'tag1' -+------------+ -| _col0| -+------------+ -|0x696f746462| -+------------+ -Total line number = 1 -It costs 0.188s -``` - - ### 3.2 Columns 函数 1. 不结合表达式 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 36e4119fc..3c80e5238 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 @@ -32,13 +32,13 @@ ### 2.1 公共参数 -| 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | -| ------------ | ---------------------- | ---------------------------------------------------------------------- | -------------- |---------------------------------------------------------------------------| -| -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | -| -p | --port | 端口号 | 否 | 6667 | -| -u | --username | 用户名 | 否 | root | -| -pw | --password | 密码 | 否 | root | +| 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | +| ------------ | ---------------------- | ----------------------------------------------------------------- | -------------- |---------------------------------------------------------------------------| +| -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | +| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -p | --port | 端口号 | 否 | 6667 | +| -u | --username | 用户名 | 否 | root | +| -pw | --password | 密码 | 否 | root | | -sql_dialect | --sql_dialect | 选择 server 是树模型还是表模型，当前支持 tree 和 table 类型 | 否 | tree | | -db | --database | ​将要导出的目标数据库，只在`-sql_dialect`为 table 类型下生效。| `-sql_dialect`为 table 时必填| - | | -table|--table | 将要导出的目标表，只在`-sql_dialect`为 table 类型下生效。如果指定了`-q`参数则此参数不生效，如果导出类型为 tsfile/sql 则此参数必填。| ​ 否 | - | @@ -46,9 +46,9 @@ |-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-beta 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | -| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8-beta 之前)
`Long.MAX_VALUE`(V2.0.8-beta 及之后)
范围：`-1~Long.MAX_VALUE` | -| -help | --help | 显示帮助信息 | 否 | | +| -q | --query | 要执行的查询语句。自 V2.0.8 起，SQL 语句中的分号将被自动移除，查询执行保持正常。 | 否 | 无 | +| -timeout | --query\_timeout | 会话查询的超时时间(ms) | 否 | `-1`(V2.0.8 之前)
`Long.MAX_VALUE`(V2.0.8 及之后)
范围：`-1~Long.MAX_VALUE` | +| -help | --help | 显示帮助信息 | 否 | | ### 2.2 CSV 格式 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md index cb872116b..4eadd15fa 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md @@ -117,7 +117,7 @@ WITH SINK ( **IF NOT EXISTS 语义**：用于创建操作中，确保当指定 Pipe 不存在时，执行创建命令，防止因尝试创建已存在的 Pipe 而导致报错。 -**注意**：V2.0.8-beta 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： +**注意**：V2.0.8 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： * 历史 Pipe：PipeId 为原名称加 _history后缀（如 `alldatapipe_history`），source 参数默认携带 `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` @@ -192,7 +192,7 @@ SHOW PIPE 示例： -在 V2.0.8-beta 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 +在 V2.0.8 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') 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 6dee9a2ec..36b6f61a2 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-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： @@ -370,7 +370,7 @@ IoTDB> SHOW AVAILABLE URLS **含义**：返回当前集群所有正常工作（RUNNING 或 READ-ONLY） DN 上的服务信息（MQTT 服务、REST 服务）。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md b/src/zh/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md index 4465dc555..20a99f346 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Tree-to-Table_apache.md @@ -79,7 +79,7 @@ comment * 若树模型中的设备不包含某些声明的 FIELD 列，或与声明的 FIELD 列的数据类型不一致，则在查询该设备时，该 FIELD 列的值永远为 NULL。 * 若未指定 FIELD 列，则创建时会自动扫描出`prefixPath`子树下所有的测点（包括定义为所有普通序列的测点，以及挂载路径与 `prefixPath `有所重合的所有模板中的测点），列名使用树模型测点名称。 * 不支持树模型存在名称（含小写）相同但类型不同的测点 -* `TIME`：创建视图时可以不指定时间列（TIME），IoTDB 会自动添加该列并命名为"time"， 且顺序上位于第一列。自 V2.0.8-beta 版本起，支持创建视图时**自定义命名时间列**，自定义时间列在视图中的顺序由创建 SQL 中的顺序决定。相关约束如下： +* `TIME`：创建视图时可以不指定时间列（TIME），IoTDB 会自动添加该列并命名为"time"， 且顺序上位于第一列。自 V2.0.8 版本起，支持创建视图时**自定义命名时间列**，自定义时间列在视图中的顺序由创建 SQL 中的顺序决定。相关约束如下： * 当列分类（columnCategory）设为 `TIME` 时，数据类型（dataType）必须为 `TIMESTAMP`。 * 每个视图最多允许定义 1个时间列（columnCategory = TIME）。 * 当未显式定义时间列时，不允许其他列使用 `time` 作为名称，否则会与系统默认时间列命名冲突。 @@ -139,7 +139,7 @@ AS root.db.** with (ttl=604800000) ``` -* 当需要自定义时间列（V2.0.8-beta 起支持）时，SQL 变更如下： +* 当需要自定义时间列（V2.0.8 起支持）时，SQL 变更如下： ```SQL CREATE OR REPLACE VIEW viewdb."风机表" diff --git a/src/zh/UserGuide/latest/API/Programming-Python-Native-API_apache.md b/src/zh/UserGuide/latest/API/Programming-Python-Native-API_apache.md index ac5477cc9..d29f2f00f 100644 --- a/src/zh/UserGuide/latest/API/Programming-Python-Native-API_apache.md +++ b/src/zh/UserGuide/latest/API/Programming-Python-Native-API_apache.md @@ -555,7 +555,7 @@ session.close() df = ... ``` -自 V2.0.8-beta 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： +自 V2.0.8 版本起，SessionDataSet 提供分批获取 DataFrame 的方法，用于高效处理大数据量查询： ```python # 分批获取 DataFrame 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 67c0278cb..7bf4d6d23 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-beta； +* IoTDB 版本：>= V 2.0.8； ## 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 167973563..cee303d62 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-beta； +* TimechoDB 版本：>= V 2.0.8； ## 3. 安装部署及使用 diff --git a/src/zh/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md b/src/zh/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md index b43045517..f303f6b6b 100644 --- a/src/zh/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md +++ b/src/zh/UserGuide/latest/IoTDB-Introduction/Release-history_apache.md @@ -20,6 +20,37 @@ --> # 发布历史 +## V2.0.8 + +> 发版时间：2026.04.14 + +V2.0.8 版本在 AI 模型能力上扩充了对现有主流时序大模型之一 Chronos-2 的支持，同时内置大模型支持并发推理能力。在数据库方面，TIME 列支持自定义命名，优化数据同步路径配置的灵活性，并对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 查询模块：新增可用 DataNode 节点的列表展示功能 +* 查询模块：新增系统表，用于在表模型中统计查询延迟信息 +* 查询模块：Python SessionDataset 支持将 TsBlock 转换为 DataFrame，并批量返回 DataFrame +* 存储模块：支持为 TIME 时间列自定义列名 +* 存储模块：支持通过 SQL 查看已创建表 / 视图的完整定义语句 +* 流处理模块：Pipe 同步支持排除指定设备 / 测点进行同步 +* 流处理模块：支持在一个 Pipe 中填写多个精确路径的 path +* 流处理模块：Pipe 过滤路径时，支持以逗号分隔，混合使用 source.pattern 与 source.path 参数 +* AI 模块：内置 Chronos-2 模型，支持预测功能 +* AI 模块：Timer-XL、Sundial 内置模型支持并发推理功能 +* 系统模块：新增系统表，用于在表模型中展示 DataNode 节点连接状态 +* 其他：修复安全漏洞 CVE-2025-12183、CVE-2025-66566 及 CVE-2025-11226 + +## V2.0.7 + +> 发版时间：2026.03.04 + +V2.0.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V2.0.6 > 发版时间：2026.01.20 @@ -118,6 +149,18 @@ V2.0.1-beta 主要新增了树表双模型配置，并配合表模型支持标 - 脚本与工具：import-data/export-data 脚本迭代，同时兼容 TsFile、CSV 和 SQL 三种类型数据的导入导出 - 生态集成：支持 Kubernetes Operator +## V1.3.7 + +> 发版时间：2026.03.04 + +V1.3.7 版本聚焦安全加固与稳定性优化，删除存在风险的 RPC 接口和 JEXL 函数，强化命名规范校验与服务地址配置逻辑，优化分区表自动删除机制，同时对数据库监控、性能、稳定性进行了全方位提升。具体发布内容如下： + +* 其他：删除存在风险的 RPC 接口 +* 其他：删除 JEXL 函数 +* 其他：创建 Pipe 时校验命名合法性 +* 其他：将客户端 RPC 服务默认地址修改为 127.0.0.1 +* 其他：调整代码逻辑，使内部服务绑定 dn_internal_address 配置的地址，而非默认地址 + ## V1.3.6 > 发版时间：2026.01.20 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 8c9f8b550..7194b2bcb 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 @@ -31,18 +31,18 @@ ### 2.1 公共参数 -| 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | -| ---------- | ---------------------- |----------------------------------------------------| -------------- |-----------------------------------------------------------------------------| -| -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | -| -p | --port | 端口号 | 否 | 6667 | -| -u | --username | 用户名 | 否 | root | -| -pw | --password | 密码 | 否 | root | -| -t | --target | 指定输出文件的目标文件夹，如果路径不存在新建文件夹 | √ | | -| -pfn | --prefix\_file\_name | 指定导出文件的名称。例如：abc,生成的文件是abc\_0.tsfile、abc\_1.tsfile | 否 | dump\_0.tsfile | -| -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 | 显示帮助信息 | 否 | | +| 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | +| ---------- | ---------------------- |---------------------------------------------------| -------------- |---------------------------------------------------------------------------| +| -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | +| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -p | --port | 端口号 | 否 | 6667 | +| -u | --username | 用户名 | 否 | root | +| -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` | +| -help | --help | 显示帮助信息 | 否 | | ### 2.2 Csv 格式 diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md index ffacb90d6..750765fe3 100644 --- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md @@ -122,7 +122,7 @@ WITH SINK ( **IF NOT EXISTS 语义**：用于创建操作中，确保当指定 Pipe 不存在时，执行创建命令，防止因尝试创建已存在的 Pipe 而导致报错。 -**注意**：V2.0.8-beta 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： +**注意**：V2.0.8 起，创建一个全量数据同步 Pipe （例如 Pipeid : `alldatapipe`）时，系统会自动将其拆分为两个独立的 Pipe： * 历史 Pipe：PipeId 为原名称加 _history后缀（如 `alldatapipe_history`），source 参数默认携带 `'realtime.enable'='false', 'inclusion'='data.insert', 'inclusion.exclusion'=''` @@ -198,7 +198,7 @@ SHOW PIPE 示例： -在 V2.0.8-beta 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 +在 V2.0.8 及之后的版本中，创建一个全量数据同步任务，并查看该任务详情 ```sql IoTDB> create pipe alldatapipe with source('inclusion'='all','exclusion'='auth') with sink('node-urls'='127.0.0.1:6668') @@ -511,19 +511,19 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1 ### 5.1 source 参数 -| 参数 | 描述 | value 取值范围 | 是否必填 | 默认取值 | -|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| -------- | -------------- | -| source | iotdb-source | String: iotdb-source | 必填 | - | -| inclusion | 用于指定数据同步任务中需要同步范围，分为数据、元数据和权限 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | data.insert | -| inclusion.exclusion | 用于从 inclusion 指定的同步范围内排除特定的操作，减少同步的数据量 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | 空字符串 | +| 参数 | 描述 | value 取值范围 | 是否必填 | 默认取值 | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| -------- | -------------- | +| source | iotdb-source | String: iotdb-source | 必填 | - | +| inclusion | 用于指定数据同步任务中需要同步范围，分为数据、元数据和权限 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | data.insert | +| inclusion.exclusion | 用于从 inclusion 指定的同步范围内排除特定的操作，减少同步的数据量 | String:all, data(insert,delete), schema(database,timeseries,ttl), auth | 选填 | 空字符串 | | mode.streaming | 此参数指定时序数据写入的捕获来源。适用于 `mode.streaming`为 `false` 模式下的场景，决定`inclusion`中`data.insert`数据的捕获来源。提供两种捕获策略：true： 动态选择捕获的类型。系统将根据下游处理速度，自适应地选择是捕获每个写入请求还是仅捕获 TsFile 文件的封口请求。当下游处理速度快时，优先捕获写入请求以减少延迟；当处理速度慢时，仅捕获文件封口请求以避免处理堆积。这种模式适用于大多数场景，能够实现处理延迟和吞吐量的最优平衡。false：固定按批捕获方式。仅捕获 TsFile 文件的封口请求，适用于资源受限的应用场景，以降低系统负载。注意，pipe 启动时捕获的快照数据只会以文件的方式供下游处理。 | Boolean: true / false | 否 | true | -| mode.strict | 在使用 time / path / database-name / table-name 参数过滤数据时，是否需要严格按照条件筛选：`true`： 严格筛选。系统将完全按照给定条件过滤筛选被捕获的数据，确保只有符合条件的数据被选中。`false`：非严格筛选。系统在筛选被捕获的数据时可能会包含一些额外的数据，适用于性能敏感的场景，可降低 CPU 和 IO 消耗。 | Boolean: true / false | 否 | true | -| mode.snapshot | 此参数决定时序数据的捕获方式，影响`inclusion`中的`data`数据。提供两种模式：`true`：静态数据捕获。启动 pipe 时，会进行一次性的数据快照捕获。当快照数据被完全消费后，**pipe 将自动终止（DROP PIPE SQL 会自动执行）**。`false`：动态数据捕获。除了在 pipe 启动时捕获快照数据外，还会持续捕获后续的数据变更。pipe 将持续运行以处理动态数据流。 | Boolean: true / false | 否 | false | -| path | 当用户连接指定的sql_dialect为tree时可以指定。对于升级上来的用户pipe,默认sql_dialect为tree。此参数决定时序数据的捕获范围,影响 inclusion中的data数据,以及部分序列相关的元数据。当数据的树模型路径能够被path匹配时，数据会被筛选出来进入流处理pipe。
自 V2.0.8-beta 版本起，该参数支持在一个pipe中填写多个精确路径的path , 如 `'path'='root.test.d0,s1,root.test.d0.s2,root.test.d0.s3'` | String:IoTDB标准的树路径模式,可以带通配符 | 选填 | root.** | -| start-time | 同步所有数据的开始 event time，包含 start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MIN_VALUE | -| end-time | 同步所有数据的结束 event time，包含 end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MAX_VALUE | -| forwarding-pipe-requests | 是否转发由其他 Pipe （通常是数据同步）写入的数据 | Boolean: true, false | 选填 | true | -| mods | 同 mods.enable，是否发送 tsfile 的 mods 文件 | Boolean: true / false | 选填 | false | +| mode.strict | 在使用 time / path / database-name / table-name 参数过滤数据时，是否需要严格按照条件筛选：`true`： 严格筛选。系统将完全按照给定条件过滤筛选被捕获的数据，确保只有符合条件的数据被选中。`false`：非严格筛选。系统在筛选被捕获的数据时可能会包含一些额外的数据，适用于性能敏感的场景，可降低 CPU 和 IO 消耗。 | Boolean: true / false | 否 | true | +| mode.snapshot | 此参数决定时序数据的捕获方式，影响`inclusion`中的`data`数据。提供两种模式：`true`：静态数据捕获。启动 pipe 时，会进行一次性的数据快照捕获。当快照数据被完全消费后，**pipe 将自动终止（DROP PIPE SQL 会自动执行）**。`false`：动态数据捕获。除了在 pipe 启动时捕获快照数据外，还会持续捕获后续的数据变更。pipe 将持续运行以处理动态数据流。 | Boolean: true / false | 否 | false | +| path | 当用户连接指定的sql_dialect为tree时可以指定。对于升级上来的用户pipe,默认sql_dialect为tree。此参数决定时序数据的捕获范围,影响 inclusion中的data数据,以及部分序列相关的元数据。当数据的树模型路径能够被path匹配时，数据会被筛选出来进入流处理pipe。
自 V2.0.8 版本起，该参数支持在一个pipe中填写多个精确路径的path , 如 `'path'='root.test.d0,s1,root.test.d0.s2,root.test.d0.s3'` | String:IoTDB标准的树路径模式,可以带通配符 | 选填 | root.** | +| start-time | 同步所有数据的开始 event time，包含 start-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MIN_VALUE | +| end-time | 同步所有数据的结束 event time，包含 end-time | Long: [Long.MIN_VALUE, Long.MAX_VALUE] | 选填 | Long.MAX_VALUE | +| forwarding-pipe-requests | 是否转发由其他 Pipe （通常是数据同步）写入的数据 | Boolean: true, false | 选填 | true | +| mods | 同 mods.enable，是否发送 tsfile 的 mods 文件 | Boolean: true / false | 选填 | false | > 💎 **说明：数据抽取模式 mode.streaming 取值 true 和 false 的差异** > - **true（推荐）**：该取值下，任务将对数据进行实时处理、发送，其特点是高时效、低吞吐 diff --git a/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md index 1cba1564c..012236f2f 100644 --- a/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md @@ -248,7 +248,7 @@ IoTDB> SHOW REGIONS **含义**：返回当前集群所有可用的 DataNode 的 RPC 地址和端口。注意：这里对于“可用”的定义为：处于非 REMOVING 状态的 DN 节点。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法： @@ -278,7 +278,7 @@ IoTDB> SHOW AVAILABLE URLS **含义**：返回当前集群所有正常工作（RUNNING 或 READ-ONLY） DN 上的服务信息（MQTT 服务、REST 服务）。 -> V2.0.8-beta 起支持该功能 +> V2.0.8 起支持该功能 #### 语法：