You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/API/Programming-Java-Native-API_apache.md
-21Lines changed: 0 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,27 +64,6 @@ The `ITableSession` interface defines basic operations for interacting with IoTD
64
64
| 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`|
65
65
| close() | Closes the session and releases resources. | None | None | IoTDBConnectionException |
66
66
67
-
**Description of Object Data Type:**
68
-
69
-
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:
70
-
71
-
```Java
72
-
/*
73
-
rowIndex: row position in the tablet
74
-
columnIndex: column position in the tablet
75
-
isEOF: whether the current write operation contains the last segment of the Object file
76
-
offset: starting offset of the current write content within the Object file
77
-
content: byte array of the current write content
78
-
Note: When writing, ensure the total length of all segmented byte[] arrays equals the original Object size,
79
-
otherwise it will cause incorrect data size.
80
-
*/
81
-
void addValue(int rowIndex, int columnIndex, boolean isEOF, long offset, byte[] content)
82
-
```
83
-
84
-
During queries, the following four methods are supported to retrieve values:
85
-
`Field.getStringValue`, `Field.getObjectValue`, `SessionDataSet.DataIterator.getObject`, and `SessionDataSet.DataIterator.getString`.
86
-
All these methods return a String containing metadata in the format:
87
-
`(Object) XX.XX KB` (where XX.XX KB represents the actual object size).
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_apache.md
-54Lines changed: 0 additions & 54 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -316,60 +316,6 @@ It costs 0.014s
316
316
* For more details about user permissions, refer to [Authority Management](../User-Manual/Authority-Management_apache.md).
317
317
318
318
319
-
### 1.7 Writing Object Type
320
-
321
-
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.
322
-
323
-
> Supported since V2.0.8-beta
324
-
325
-
**Syntax:**
326
-
327
-
```SQL
328
-
INSERT INTO tableName(time, columnName) VALUES(timeValue, TO_OBJECT(isEOF, offset, content));
| isEOF | BOOLEAN | Whether the current write contains the last segment of the Object |
336
-
| offset | INT64 | Starting offset of the current segment within the Object |
337
-
| content | Hexadecimal (HEX) | Content of the current segment |
338
-
339
-
**Examples:**
340
-
341
-
Add an Object-type column `s1` to table `table1`:
342
-
343
-
```SQL
344
-
ALTERTABLE table1 ADD COLUMN IF NOT EXISTS s1 OBJECT FIELD COMMENT 'object type';
345
-
```
346
-
347
-
1.**Non-segmented write**
348
-
349
-
```SQL
350
-
INSERT INTO table1(time, device_id, s1) VALUES(NOW(), 'tag1', TO_OBJECT(TRUE, 0, X'696F746462'));
351
-
```
352
-
353
-
2.**Segmented write**
354
-
355
-
```SQL
356
-
-- First write: TO_OBJECT(FALSE, 0, X'696F');
357
-
INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(FALSE, 0, X'696F'));
358
-
359
-
-- Second write: TO_OBJECT(FALSE, 2, X'7464');
360
-
INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(FALSE, 2, X'7464'));
361
-
362
-
-- Third write: TO_OBJECT(TRUE, 4, X'62');
363
-
INSERT INTO table1(time, device_id, s1) VALUES(1, 'tag1', TO_OBJECT(TRUE, 4, X'62'));
364
-
```
365
-
366
-
**Notes:**
367
-
368
-
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.
369
-
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.
370
-
3. If `offset=0` is used after partial writes, the existing content will be overwritten with new data.
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md
+48-2Lines changed: 48 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,11 +20,43 @@
20
20
-->
21
21
# Release History
22
22
23
+
## V2.0.8
24
+
25
+
> Release Date: 2026.04.14
26
+
27
+
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:
28
+
29
+
***Query Module**: Added functionality to display the list of available DataNode nodes
30
+
***Query Module**: Added system table for统计查询延迟信息 in the table model
31
+
***Query Module**: Python SessionDataset now supports converting TsBlock to DataFrame and returning DataFrames in batches
32
+
***Storage Module**: TIME column now supports custom column naming
33
+
***Storage Module**: Added SQL support for viewing the complete definition statements of created tables/views
34
+
***Stream Processing Module**: Pipe synchronization now supports excluding specified devices/measurement points from synchronization
35
+
***Stream Processing Module**: Multiple exact paths can now be specified in a single Pipe
36
+
***Stream Processing Module**: When filtering paths in Pipe, `source.pattern` and `source.path` parameters can now be used together with comma separation
37
+
***AI Module**: Built-in Chronos-2 model with prediction support
38
+
***AI Module**: Timer-XL and Sundial built-in models now support concurrent inference
39
+
***System Module**: Added system table for displaying DataNode node connection status in the table model
40
+
***Miscellaneous**: Fixed security vulnerabilities CVE-2025-12183, CVE-2025-66566, and CVE-2025-11226
41
+
42
+
## V2.0.7
43
+
44
+
> Release Date: 2026.03.04
45
+
46
+
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**: Added naming合法性校验 when creating Pipe
51
+
***Miscellaneous**: Changed the default client RPC service address to 127.0.0.1
52
+
***Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address
53
+
54
+
23
55
## V2.0.6
24
56
25
57
> Release Date: 2026.01.20
26
58
27
-
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:
59
+
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:
28
60
29
61
***Query Module**: Added support for query-writeback functionality in the table model.
30
62
***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.
37
69
38
70
> Release Date: 2025.08.21
39
71
40
-
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:
72
+
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:
41
73
42
74
***Query Module**: Supports manual creation of tree-to-table views
43
75
***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
134
166
* **Ecosystem Integration**:
135
167
* Kubernetes Operator support
136
168
169
+
## V1.3.7
170
+
171
+
> Release Date: 2026.03.04
172
+
173
+
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**: Added naming合法性校验 when creating Pipe
178
+
***Miscellaneous**: Changed the default client RPC service address to 127.0.0.1
179
+
***Miscellaneous**: Adjusted code logic so that internal services bind to the address configured by `dn_internal_address` instead of the default address
0 commit comments