This is an automated email from the ASF dual-hosted git repository.
critas pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iotdb-docs.git
The following commit(s) were added to refs/heads/main by this push:
new 97baf423 add object datatype from 208 (#990)
97baf423 is described below
commit 97baf4236f9f78a1a503229dd38459ceec0a0527
Author: leto-b <[email protected]>
AuthorDate: Wed Feb 4 12:00:16 2026 +0800
add object datatype from 208 (#990)
---
.../API/Programming-Java-Native-API_apache.md | 25 ++++++-
.../API/Programming-Java-Native-API_timecho.md | 22 ++++++
.../Master/Table/Background-knowledge/Data-Type.md | 13 +++-
.../Basic-Concept/Write-Updata-Data_apache.md | 55 ++++++++++++++-
.../Basic-Concept/Write-Updata-Data_timecho.md | 54 ++++++++++++++-
.../Master/Table/Reference/System-Config-Manual.md | 18 +++++
.../Master/Table/SQL-Manual/Basis-Function.md | 2 +-
.../Table/SQL-Manual/Featured-Functions_apache.md | 41 +++++++++++
.../Table/SQL-Manual/Featured-Functions_timecho.md | 41 +++++++++++
.../Master/Table/SQL-Manual/Fill-Clause.md | 2 +-
.../Master/Table/SQL-Manual/Select-Clause.md | 45 ++++++++++--
.../Table/Tools-System/Data-Export-Tool_apache.md | 1 +
.../Table/Tools-System/Data-Export-Tool_timecho.md | 1 +
.../Table/Tools-System/Data-Import-Tool_apache.md | 2 +
.../Table/Tools-System/Data-Import-Tool_timecho.md | 2 +
.../Master/Table/User-Manual/Data-Sync_apache.md | 1 +
.../Master/Table/User-Manual/Data-Sync_timecho.md | 1 +
.../API/Programming-Java-Native-API_apache.md | 22 ++++++
.../API/Programming-Java-Native-API_timecho.md | 22 ++++++
.../latest-Table/Background-knowledge/Data-Type.md | 13 +++-
.../Basic-Concept/Write-Updata-Data_apache.md | 55 ++++++++++++++-
.../Basic-Concept/Write-Updata-Data_timecho.md | 54 ++++++++++++++-
.../latest-Table/Reference/System-Config-Manual.md | 18 +++++
.../latest-Table/SQL-Manual/Basis-Function.md | 2 +-
.../SQL-Manual/Featured-Functions_apache.md | 41 +++++++++++
.../SQL-Manual/Featured-Functions_timecho.md | 41 +++++++++++
.../latest-Table/SQL-Manual/Fill-Clause.md | 2 +-
.../latest-Table/SQL-Manual/Select-Clause.md | 31 +++++++++
.../Tools-System/Data-Export-Tool_apache.md | 1 +
.../Tools-System/Data-Export-Tool_timecho.md | 1 +
.../Tools-System/Data-Import-Tool_apache.md | 2 +
.../Tools-System/Data-Import-Tool_timecho.md | 2 +
.../latest-Table/User-Manual/Data-Sync_apache.md | 1 +
.../latest-Table/User-Manual/Data-Sync_timecho.md | 1 +
.../API/Programming-Java-Native-API_apache.md | 19 +++++
.../API/Programming-Java-Native-API_timecho.md | 19 +++++
.../Master/Table/Background-knowledge/Data-Type.md | 38 ++++++----
.../Basic-Concept/Write-Updata-Data_apache.md | 55 ++++++++++++++-
.../Basic-Concept/Write-Updata-Data_timecho.md | 81 +++++++++++++++++++++-
.../Master/Table/Reference/System-Config-Manual.md | 19 +++++
.../Master/Table/SQL-Manual/Basis-Function.md | 2 +-
.../Table/SQL-Manual/Featured-Functions_apache.md | 42 +++++++++++
.../Table/SQL-Manual/Featured-Functions_timecho.md | 42 +++++++++++
.../Master/Table/SQL-Manual/Fill-Clause.md | 2 +-
.../Master/Table/SQL-Manual/Select-Clause.md | 53 +++++++++++---
.../Table/Tools-System/Data-Export-Tool_apache.md | 1 +
.../Table/Tools-System/Data-Export-Tool_timecho.md | 1 +
.../Table/Tools-System/Data-Import-Tool_apache.md | 1 +
.../Table/Tools-System/Data-Import-Tool_timecho.md | 1 +
.../Master/Table/User-Manual/Data-Sync_apache.md | 1 +
.../Master/Table/User-Manual/Data-Sync_timecho.md | 1 +
.../API/Programming-Java-Native-API_apache.md | 19 +++++
.../API/Programming-Java-Native-API_timecho.md | 19 +++++
.../latest-Table/Background-knowledge/Data-Type.md | 38 ++++++----
.../Basic-Concept/Write-Updata-Data_apache.md | 55 ++++++++++++++-
.../Basic-Concept/Write-Updata-Data_timecho.md | 81 +++++++++++++++++++++-
.../latest-Table/Reference/System-Config-Manual.md | 19 +++++
.../latest-Table/SQL-Manual/Basis-Function.md | 2 +-
.../SQL-Manual/Featured-Functions_apache.md | 42 +++++++++++
.../SQL-Manual/Featured-Functions_timecho.md | 42 +++++++++++
.../latest-Table/SQL-Manual/Fill-Clause.md | 2 +-
.../latest-Table/SQL-Manual/Select-Clause.md | 31 +++++++++
.../Tools-System/Data-Export-Tool_apache.md | 1 +
.../Tools-System/Data-Export-Tool_timecho.md | 1 +
.../Tools-System/Data-Import-Tool_apache.md | 1 +
.../Tools-System/Data-Import-Tool_timecho.md | 1 +
.../latest-Table/User-Manual/Data-Sync_apache.md | 1 +
.../latest-Table/User-Manual/Data-Sync_timecho.md | 1 +
68 files changed, 1306 insertions(+), 63 deletions(-)
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 1303ae89..07d2cf47 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
@@ -38,7 +38,7 @@ IoTDB provides a Java native client driver and a session pool
management mechani
<dependency>
<groupId>org.apache.iotdb</groupId>
<artifactId>iotdb-session</artifactId>
- <!-- The version number is the same as the database version number -->
+ <!-- The version number is the same as the database version number -->
<version>${project.version}</version>
</dependency>
</dependencies>
@@ -63,6 +63,28 @@ 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
```Java
@@ -345,6 +367,7 @@ public class TableSessionBuilder {
}
```
+
> Note: When creating tables using the native API, if table or column names
> contain special characters or Chinese characters, do not add extra double
> quotes around them. Otherwise, the quotation marks will become part of the
> name itself.
## 4. Session Pool
diff --git
a/src/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
b/src/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
index 874b82f7..eff3f097 100644
--- a/src/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
+++ b/src/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
@@ -63,6 +63,28 @@ 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
```java
diff --git a/src/UserGuide/Master/Table/Background-knowledge/Data-Type.md
b/src/UserGuide/Master/Table/Background-knowledge/Data-Type.md
index 71794dff..3ebd7d16 100644
--- a/src/UserGuide/Master/Table/Background-knowledge/Data-Type.md
+++ b/src/UserGuide/Master/Table/Background-knowledge/Data-Type.md
@@ -33,6 +33,8 @@ IoTDB supports the following ten data types:
- **TEXT** (Text data, suitable for long strings)
- **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)
@@ -41,6 +43,14 @@ The difference between **STRING** and **TEXT**:
- **STRING** stores text data and includes additional statistical information
to optimize value-filtering queries.
- **TEXT** is suitable for storing long text strings without additional query
optimization.
+The differences between **OBJECT** and **BLOB** types are as follows:
+
+| | **OBJECT**
| **BLOB**
|
+|----------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| **Write Amplification** (Lower is better) | Low (Write amplification
factor is always 1)
| High (Write amplification factor = 2 + number of
merges) |
+| **Space Amplification** (Lower is better) | Low (Merge & release on write)
| High (Merge on read and release on compact) |
+| **Query Results** | When querying an OBJECT column by default, returns
metadata like: `(Object) XX.XX KB`. Actual OBJECT data storage path:
`${data_dir}/object_data`. Use `READ_OBJECT` function to retrieve raw content |
Directly returns raw binary content |
+
### 1.1 Floating-Point Precision Configuration
For **FLOAT** and **DOUBLE** series using **RLE** or **TS_2DIFF** encoding,
the number of decimal places can be set via the **MAX_POINT_NUMBER** attribute
during series creation.
@@ -63,7 +73,7 @@ If the written data type does not match the registered data
type of a series:
The compatibility of data types is shown in the table below:
| Registered Data Type | Compatible Write Data Types |
-| :------------------- | :------------------------------------- |
+|:---------------------|:---------------------------------------|
| BOOLEAN | BOOLEAN |
| INT32 | INT32 |
| INT64 | INT32, INT64, TIMESTAMP |
@@ -72,6 +82,7 @@ The compatibility of data types is shown in the table below:
| TEXT | TEXT, STRING |
| STRING | TEXT, STRING |
| BLOB | TEXT, STRING, BLOB |
+| OBJECT | OBJECT |
| TIMESTAMP | INT32, INT64, TIMESTAMP |
| DATE | DATE |
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 8598de7f..193fa718 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
@@ -287,7 +287,7 @@ It costs 0.014s
* The source table in the `query` and the target table `table_name` are
allowed to be the same table, e.g., `INSERT INTO testtb SELECT * FROM testtb`.
* The target table **must already exist**; otherwise, the error message
`550: Table 'xxx.xxx' does not exist` will be thrown.
-* The number and data types of columns returned by the query **must exactly
match** those of the target table. Type conversion between compatible types is
not supported currently. A type mismatch will trigger the error message `701:
Insert query has mismatched column types`.
+* The number and types of query result columns must exactly match those of the
target table. Object type is currently not supported, and no implicit type
conversion is supported. If types mismatch, the error `701: Insert query has
mismatched column types` will be raised.
* You can specify a subset of columns in the target table, provided the
following rules are met:
* The timestamp column must be included; otherwise, the error message `701:
time column can not be null` will be thrown.
* At least one **FIELD** column must be included; otherwise, the error
message `701: No Field column present` will be thrown.
@@ -302,6 +302,59 @@ 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
diff --git
a/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
b/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
index 7d12c6bd..d869ad08 100644
--- a/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
+++ b/src/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
@@ -287,7 +287,7 @@ It costs 0.014s
* The source table in the `query` and the target table `table_name` are
allowed to be the same table, e.g., `INSERT INTO testtb SELECT * FROM testtb`.
* The target table **must already exist**; otherwise, the error message
`550: Table 'xxx.xxx' does not exist` will be thrown.
-* The number and data types of columns returned by the query **must exactly
match** those of the target table. Type conversion between compatible types is
not supported currently. A type mismatch will trigger the error message `701:
Insert query has mismatched column types`.
+* The number and types of query result columns must exactly match those of the
target table. Object type is currently not supported, and no implicit type
conversion is supported. If types mismatch, the error `701: Insert query has
mismatched column types` will be raised.
* You can specify a subset of columns in the target table, provided the
following rules are met:
* The timestamp column must be included; otherwise, the error message `701:
time column can not be null` will be thrown.
* At least one **FIELD** column must be included; otherwise, the error
message `701: No Field column present` will be thrown.
@@ -301,7 +301,59 @@ It costs 0.014s
* The `WRITE` permission on the target table.
* For more details about user permissions, refer to [Authority
Management](../User-Manual/Authority-Management_timecho.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
diff --git a/src/UserGuide/Master/Table/Reference/System-Config-Manual.md
b/src/UserGuide/Master/Table/Reference/System-Config-Manual.md
index 98977ae3..c7006be4 100644
--- a/src/UserGuide/Master/Table/Reference/System-Config-Manual.md
+++ b/src/UserGuide/Master/Table/Reference/System-Config-Manual.md
@@ -1812,6 +1812,24 @@ 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: <br> 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 [...]
+| Type | boolean
[...]
+| Default | false
[...]
+| Effective | Can only be modified before the first service startup.
[...]
+
### 4.20 Compaction Configurations
- enable_seq_space_compaction
diff --git a/src/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
b/src/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
index 1cad9d0c..4b4cdf97 100644
--- a/src/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
+++ b/src/UserGuide/Master/Table/SQL-Manual/Basis-Function.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.
+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.
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 d0b771fe..9980e89f 100644
--- a/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md
+++ b/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_apache.md
@@ -693,3 +693,44 @@ 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/Featured-Functions_timecho.md
b/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_timecho.md
index 83735765..715fcba6 100644
--- a/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_timecho.md
+++ b/src/UserGuide/Master/Table/SQL-Manual/Featured-Functions_timecho.md
@@ -818,3 +818,44 @@ Result:
|1970-01-01T08:00:01.000+08:00| d0| 5| 3|
+-----------------------------+------+----+-----+
```
+
+## 5. 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/Fill-Clause.md
b/src/UserGuide/Master/Table/SQL-Manual/Fill-Clause.md
index bf745bd7..fa7a7f49 100644
--- a/src/UserGuide/Master/Table/SQL-Manual/Fill-Clause.md
+++ b/src/UserGuide/Master/Table/SQL-Manual/Fill-Clause.md
@@ -67,7 +67,7 @@ intervalField
IoTDB supports the following three methods to fill NULL values:
-1. **PREVIOUS Fill:** Uses the most recent non-NULL value from the same column
to fill NULL values.
+1. **PREVIOUS Fill:** Uses the most recent non-NULL value from the same column
to fill NULL values. Starting from V2.0.8-beta, only this method supports the
OBJECT type.
2. **LINEAR Fill:** Applies linear interpolation using the nearest previous
and next non-NULL values in the same column.
3. **CONSTANT Fill:** Fills NULL values with a specified constant.
diff --git a/src/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
b/src/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
index 10737509..57abbe5d 100644
--- a/src/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
+++ b/src/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
@@ -21,7 +21,7 @@
# SELECT Clauses
-**SELECT Clause** specifies the columns included in the query results.
+**SELECT Clause** specifies the columns included in the query results.
## 1. Syntax Overview
@@ -63,12 +63,12 @@ Usage scenarios for DISTINCT:
1. **`COLUMNS(*)`**: Matches all columns and supports combining with
expressions.
2. **`COLUMNS(regexStr) ? AS identifier`**: Regular expression matching
- - Selects columns whose names match the specified regular expression
`(regexStr)` and supports combining with expressions.
- - Allows renaming columns by referencing groups captured by the regular
expression. If `AS` is omitted, the original column name is displayed in the
format `_coln_original_name` (where `n` is the column’s position in the result
table).
- - Renaming Syntax:
- - Use parentheses () in regexStr to define capture groups.
- - Reference captured groups in identifier using `'$index'`.
- - Note: The identifier must be enclosed in double quotes if it contains
special characters like `$`.
+ - Selects columns whose names match the specified regular expression
`(regexStr)` and supports combining with expressions.
+ - Allows renaming columns by referencing groups captured by the regular
expression. If `AS` is omitted, the original column name is displayed in the
format `_coln_original_name` (where `n` is the column’s position in the result
table).
+ - Renaming Syntax:
+ - Use parentheses () in regexStr to define capture groups.
+ - Reference captured groups in identifier using `'$index'`.
+ - Note: The identifier must be enclosed in double quotes if it
contains special characters like `$`.
## 3. Example Data
@@ -274,6 +274,37 @@ 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/Master/Table/Tools-System/Data-Export-Tool_apache.md
b/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
index 87d2ee2e..00474ffb 100644
--- a/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
+++ b/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
@@ -25,6 +25,7 @@ The data export tool `export-data.sh/bat` is located in the
`tools` directory an
</tbody>
</table>
+- Does not support the Object data type.
## 2. Detailed Features
### 2.1 Common Parameters
diff --git
a/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
b/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
index bcc3e8e2..f2c8a7d2 100644
--- a/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
+++ b/src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
@@ -25,6 +25,7 @@ The data export tool `export-data.sh/bat` is located in the
`tools` directory an
</tbody>
</table>
+- Does not support the Object data type.
## 2. Detailed Features
### 2.1 Common Parameters
diff --git a/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
b/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
index 6d04bef3..ef70a407 100644
--- a/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
+++ b/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
@@ -37,6 +37,8 @@ IoTDB supports three methods for data import:
</tbody>
</table>
+- Does not support the Object data type.
+
## 2. Data Import Tool
### 2.1 Common Parameters
diff --git
a/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
b/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
index abbb26ab..695d74d8 100644
--- a/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
+++ b/src/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
@@ -37,6 +37,8 @@ IoTDB supports three methods for data import:
</tbody>
</table>
+- Does not support the Object data type.
+
## 2. Data Import Tool
### 2.1 Common 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 ea7a19f6..e4aa5f98 100644
--- a/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
@@ -82,6 +82,7 @@ By declaratively configuring these three parts in an SQL
statement, flexible dat
- Data synchronization between IoTDB of 1. x series version and IoTDB of 2. x
and above series versions is not supported.
- When performing data synchronization tasks, avoid executing any deletion
operations to prevent inconsistencies between the two ends.
- The `pipe` and `pipe plugins` for tree models and table models are designed
to be isolated from each other. Before creating a `pipe`, it is recommended to
first use the `show` command to query the built-in plugins available under the
current `-sql_dialect` parameter configuration to ensure syntax compatibility
and functional support.
+- Does not support the Object data type.
## 2. Usage Instructions
diff --git a/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
index 73594769..50e289ae 100644
--- a/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
@@ -81,6 +81,7 @@ By declaratively configuring these three parts in an SQL
statement, flexible dat
- Data synchronization between IoTDB of 1. x series version and IoTDB of 2. x
and above series versions is not supported.
- When performing data synchronization tasks, avoid executing any deletion
operations to prevent inconsistencies between the two ends.
- The `pipe` and `pipe plugins` for tree models and table models are designed
to be isolated from each other. Before creating a `pipe`, it is recommended to
first use the `show` command to query the built-in plugins available under the
current `-sql_dialect` parameter configuration to ensure syntax compatibility
and functional support.
+- Does not support the Object data type.
## 2. Usage Instructions
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 df3e249b..07d2cf47 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
@@ -63,6 +63,28 @@ 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
```Java
diff --git
a/src/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
b/src/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
index 874b82f7..eff3f097 100644
--- a/src/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
+++ b/src/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
@@ -63,6 +63,28 @@ 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
```java
diff --git a/src/UserGuide/latest-Table/Background-knowledge/Data-Type.md
b/src/UserGuide/latest-Table/Background-knowledge/Data-Type.md
index 71794dff..3ebd7d16 100644
--- a/src/UserGuide/latest-Table/Background-knowledge/Data-Type.md
+++ b/src/UserGuide/latest-Table/Background-knowledge/Data-Type.md
@@ -33,6 +33,8 @@ IoTDB supports the following ten data types:
- **TEXT** (Text data, suitable for long strings)
- **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)
@@ -41,6 +43,14 @@ The difference between **STRING** and **TEXT**:
- **STRING** stores text data and includes additional statistical information
to optimize value-filtering queries.
- **TEXT** is suitable for storing long text strings without additional query
optimization.
+The differences between **OBJECT** and **BLOB** types are as follows:
+
+| | **OBJECT**
| **BLOB**
|
+|----------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| **Write Amplification** (Lower is better) | Low (Write amplification
factor is always 1)
| High (Write amplification factor = 2 + number of
merges) |
+| **Space Amplification** (Lower is better) | Low (Merge & release on write)
| High (Merge on read and release on compact) |
+| **Query Results** | When querying an OBJECT column by default, returns
metadata like: `(Object) XX.XX KB`. Actual OBJECT data storage path:
`${data_dir}/object_data`. Use `READ_OBJECT` function to retrieve raw content |
Directly returns raw binary content |
+
### 1.1 Floating-Point Precision Configuration
For **FLOAT** and **DOUBLE** series using **RLE** or **TS_2DIFF** encoding,
the number of decimal places can be set via the **MAX_POINT_NUMBER** attribute
during series creation.
@@ -63,7 +73,7 @@ If the written data type does not match the registered data
type of a series:
The compatibility of data types is shown in the table below:
| Registered Data Type | Compatible Write Data Types |
-| :------------------- | :------------------------------------- |
+|:---------------------|:---------------------------------------|
| BOOLEAN | BOOLEAN |
| INT32 | INT32 |
| INT64 | INT32, INT64, TIMESTAMP |
@@ -72,6 +82,7 @@ The compatibility of data types is shown in the table below:
| TEXT | TEXT, STRING |
| STRING | TEXT, STRING |
| BLOB | TEXT, STRING, BLOB |
+| OBJECT | OBJECT |
| TIMESTAMP | INT32, INT64, TIMESTAMP |
| DATE | DATE |
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 8598de7f..193fa718 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
@@ -287,7 +287,7 @@ It costs 0.014s
* The source table in the `query` and the target table `table_name` are
allowed to be the same table, e.g., `INSERT INTO testtb SELECT * FROM testtb`.
* The target table **must already exist**; otherwise, the error message
`550: Table 'xxx.xxx' does not exist` will be thrown.
-* The number and data types of columns returned by the query **must exactly
match** those of the target table. Type conversion between compatible types is
not supported currently. A type mismatch will trigger the error message `701:
Insert query has mismatched column types`.
+* The number and types of query result columns must exactly match those of the
target table. Object type is currently not supported, and no implicit type
conversion is supported. If types mismatch, the error `701: Insert query has
mismatched column types` will be raised.
* You can specify a subset of columns in the target table, provided the
following rules are met:
* The timestamp column must be included; otherwise, the error message `701:
time column can not be null` will be thrown.
* At least one **FIELD** column must be included; otherwise, the error
message `701: No Field column present` will be thrown.
@@ -302,6 +302,59 @@ 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
diff --git
a/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
b/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
index 7d12c6bd..d869ad08 100644
--- a/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
+++ b/src/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
@@ -287,7 +287,7 @@ It costs 0.014s
* The source table in the `query` and the target table `table_name` are
allowed to be the same table, e.g., `INSERT INTO testtb SELECT * FROM testtb`.
* The target table **must already exist**; otherwise, the error message
`550: Table 'xxx.xxx' does not exist` will be thrown.
-* The number and data types of columns returned by the query **must exactly
match** those of the target table. Type conversion between compatible types is
not supported currently. A type mismatch will trigger the error message `701:
Insert query has mismatched column types`.
+* The number and types of query result columns must exactly match those of the
target table. Object type is currently not supported, and no implicit type
conversion is supported. If types mismatch, the error `701: Insert query has
mismatched column types` will be raised.
* You can specify a subset of columns in the target table, provided the
following rules are met:
* The timestamp column must be included; otherwise, the error message `701:
time column can not be null` will be thrown.
* At least one **FIELD** column must be included; otherwise, the error
message `701: No Field column present` will be thrown.
@@ -301,7 +301,59 @@ It costs 0.014s
* The `WRITE` permission on the target table.
* For more details about user permissions, refer to [Authority
Management](../User-Manual/Authority-Management_timecho.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
diff --git a/src/UserGuide/latest-Table/Reference/System-Config-Manual.md
b/src/UserGuide/latest-Table/Reference/System-Config-Manual.md
index 98977ae3..c7006be4 100644
--- a/src/UserGuide/latest-Table/Reference/System-Config-Manual.md
+++ b/src/UserGuide/latest-Table/Reference/System-Config-Manual.md
@@ -1812,6 +1812,24 @@ 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: <br> 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 [...]
+| Type | boolean
[...]
+| Default | false
[...]
+| Effective | Can only be modified before the first service startup.
[...]
+
### 4.20 Compaction Configurations
- enable_seq_space_compaction
diff --git a/src/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
b/src/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
index 1cad9d0c..4b4cdf97 100644
--- a/src/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
+++ b/src/UserGuide/latest-Table/SQL-Manual/Basis-Function.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.
+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.
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 d0b771fe..9980e89f 100644
--- a/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md
+++ b/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_apache.md
@@ -693,3 +693,44 @@ 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/latest-Table/SQL-Manual/Featured-Functions_timecho.md
b/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_timecho.md
index 83735765..715fcba6 100644
--- a/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_timecho.md
+++ b/src/UserGuide/latest-Table/SQL-Manual/Featured-Functions_timecho.md
@@ -818,3 +818,44 @@ Result:
|1970-01-01T08:00:01.000+08:00| d0| 5| 3|
+-----------------------------+------+----+-----+
```
+
+## 5. 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/Fill-Clause.md
b/src/UserGuide/latest-Table/SQL-Manual/Fill-Clause.md
index bf745bd7..fa7a7f49 100644
--- a/src/UserGuide/latest-Table/SQL-Manual/Fill-Clause.md
+++ b/src/UserGuide/latest-Table/SQL-Manual/Fill-Clause.md
@@ -67,7 +67,7 @@ intervalField
IoTDB supports the following three methods to fill NULL values:
-1. **PREVIOUS Fill:** Uses the most recent non-NULL value from the same column
to fill NULL values.
+1. **PREVIOUS Fill:** Uses the most recent non-NULL value from the same column
to fill NULL values. Starting from V2.0.8-beta, only this method supports the
OBJECT type.
2. **LINEAR Fill:** Applies linear interpolation using the nearest previous
and next non-NULL values in the same column.
3. **CONSTANT Fill:** Fills NULL values with a specified constant.
diff --git a/src/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
b/src/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
index 3ca612e9..57abbe5d 100644
--- a/src/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
+++ b/src/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
@@ -274,6 +274,37 @@ 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 87d2ee2e..00474ffb 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
@@ -25,6 +25,7 @@ The data export tool `export-data.sh/bat` is located in the
`tools` directory an
</tbody>
</table>
+- Does not support the Object data type.
## 2. Detailed Features
### 2.1 Common Parameters
diff --git
a/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
b/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
index bcc3e8e2..f2c8a7d2 100644
--- a/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
+++ b/src/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
@@ -25,6 +25,7 @@ The data export tool `export-data.sh/bat` is located in the
`tools` directory an
</tbody>
</table>
+- Does not support the Object data type.
## 2. Detailed Features
### 2.1 Common Parameters
diff --git a/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
b/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
index 6d04bef3..ef70a407 100644
--- a/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
+++ b/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
@@ -37,6 +37,8 @@ IoTDB supports three methods for data import:
</tbody>
</table>
+- Does not support the Object data type.
+
## 2. Data Import Tool
### 2.1 Common Parameters
diff --git
a/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
b/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
index abbb26ab..695d74d8 100644
--- a/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
+++ b/src/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
@@ -37,6 +37,8 @@ IoTDB supports three methods for data import:
</tbody>
</table>
+- Does not support the Object data type.
+
## 2. Data Import Tool
### 2.1 Common Parameters
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 ea7a19f6..e4aa5f98 100644
--- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
@@ -82,6 +82,7 @@ By declaratively configuring these three parts in an SQL
statement, flexible dat
- Data synchronization between IoTDB of 1. x series version and IoTDB of 2. x
and above series versions is not supported.
- When performing data synchronization tasks, avoid executing any deletion
operations to prevent inconsistencies between the two ends.
- The `pipe` and `pipe plugins` for tree models and table models are designed
to be isolated from each other. Before creating a `pipe`, it is recommended to
first use the `show` command to query the built-in plugins available under the
current `-sql_dialect` parameter configuration to ensure syntax compatibility
and functional support.
+- Does not support the Object data type.
## 2. Usage Instructions
diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
index 73594769..50e289ae 100644
--- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
@@ -81,6 +81,7 @@ By declaratively configuring these three parts in an SQL
statement, flexible dat
- Data synchronization between IoTDB of 1. x series version and IoTDB of 2. x
and above series versions is not supported.
- When performing data synchronization tasks, avoid executing any deletion
operations to prevent inconsistencies between the two ends.
- The `pipe` and `pipe plugins` for tree models and table models are designed
to be isolated from each other. Before creating a `pipe`, it is recommended to
first use the `show` command to query the built-in plugins available under the
current `-sql_dialect` parameter configuration to ensure syntax compatibility
and functional support.
+- Does not support the Object data type.
## 2. Usage Instructions
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 c5a35939..ad3fc190 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
@@ -66,6 +66,25 @@ 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 接口展示
``` java
diff --git
a/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
b/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
index 6bc98b93..e71d71f9 100644
--- a/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
+++ b/src/zh/UserGuide/Master/Table/API/Programming-Java-Native-API_timecho.md
@@ -66,6 +66,25 @@ 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 接口展示
``` java
diff --git a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type.md
b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type.md
index 35f8a971..1f2347c2 100644
--- a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type.md
+++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type.md
@@ -33,10 +33,21 @@ IoTDB 支持以下十种数据类型：
* TEXT（长字符串）
* STRING（字符串）
* BLOB（大二进制对象）
+* OBJECT（大二进制对象）
+ > V2.0.8-beta 版本起支持
* TIMESTAMP（时间戳）
* DATE（日期）
-其中，STRING 和 TEXT 类型的区别在于，STRING 类型具有更多的统计信息，能够用于优化值过滤查询。TEXT 类型适合用于存储长字符串。
+其中:
+1. STRING 和 TEXT 类型的区别在于，STRING 类型具有更多的统计信息，能够用于优化值过滤查询。TEXT 类型适合用于存储长字符串。
+2. OBJECT 和 BLOB 类型的区别如下：
+
+ | | **OBJECT**
| **BLOB**
|
+ | ----------------------
|-------------------------------------------------------------------------------------------------------------------------|
-------------------------------------------- |
+ | 写放大（越低越好） | 低（写放大系数永远为 1）
| 高（写放大系数为 2 + 合并次数）
|
+ | 空间放大（越低越好） | 低（merge & release on write）
| 高（merge on read and
release on compact） |
+ | 查询结果 | 默认查询 OBJECT 列时，返回结果如`(Object) XX.XX KB）`。 <br> 真实 OBJECT
数据存储路径位于：`${data_dir}/object_data`，可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
+
### 1.1 浮点数精度配置
@@ -57,18 +68,19 @@ CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT,
ENCODING=RLE, 'MAX_POI
各数据类型的兼容情况如下表所示：
-| 序列数据类型 | 支持的写入数据类型 |
-|--------------|-----------------------------------|
-| BOOLEAN | BOOLEAN |
-| INT32 | INT32 |
-| INT64 | INT32 INT64 TIMESTAMP |
-| FLOAT | INT32 FLOAT |
-| DOUBLE | INT32 INT64 FLOAT DOUBLE TIMESTAMP|
-| TEXT | TEXT STRING |
-| STRING | TEXT STRING |
-| BLOB | TEXT STRING BLOB |
-| TIMESTAMP | INT32 INT64 TIMESTAMP |
-| DATE | DATE |
+| 序列数据类型 | 支持的写入数据类型 |
+|-----------|------------------------------------|
+| BOOLEAN | BOOLEAN |
+| INT32 | INT32 |
+| INT64 | INT32 INT64 TIMESTAMP |
+| FLOAT | INT32 FLOAT |
+| DOUBLE | INT32 INT64 FLOAT DOUBLE TIMESTAMP |
+| TEXT | TEXT STRING |
+| STRING | TEXT STRING |
+| BLOB | TEXT STRING BLOB |
+| OBJECT | OBJECT |
+| TIMESTAMP | INT32 INT64 TIMESTAMP |
+| DATE | DATE |
## 2. 时间戳类型
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 1029cef8..07df3388 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
@@ -274,7 +274,7 @@ It costs 0.014s
* 允许 query 中的源表与目标表 table\_name 是同一个表，例如：`INSERT INTO testtb SELECT * FROM
testtb`。
* 目标表必须已存在，否则提示错误信息`550: Table 'xxx.xxx' does not exist`。
-* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert query has
mismatched column types`。
+* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持 Object 类型，不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert
query has mismatched column types`。
* 允许指定目标表的部分列，指定目标表列名时需符合以下规则：
* 必须包含时间戳列，否则提示错误信息`701: time column can not be null`
* 必须包含至少一个 FIELD 列，否则提示错误信息`701: No Field column present`
@@ -288,6 +288,59 @@ 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/Basic-Concept/Write-Updata-Data_timecho.md
b/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
index 2d4bc304..f5190f8e 100644
--- a/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
+++ b/src/zh/UserGuide/Master/Table/Basic-Concept/Write-Updata-Data_timecho.md
@@ -274,7 +274,7 @@ It costs 0.014s
* 允许 query 中的源表与目标表 table\_name 是同一个表，例如：`INSERT INTO testtb SELECT * FROM
testtb`。
* 目标表必须已存在，否则提示错误信息`550: Table 'xxx.xxx' does not exist`。
-* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert query has
mismatched column types`。
+* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持 Object 类型，不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert
query has mismatched column types`。
* 允许指定目标表的部分列，指定目标表列名时需符合以下规则：
* 必须包含时间戳列，否则提示错误信息`701: time column can not be null`
* 必须包含至少一个 FIELD 列，否则提示错误信息`701: No Field column present`
@@ -289,6 +289,85 @@ It costs 0.014s
* 更多用户权限相关的内容，请参考[权限管理](../User-Manual/Authority-Management_timecho.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. 数据更新
+
+### 2.1 语法
+
+```SQL
+UPDATE <TABLE_NAME> SET updateAssignment (',' updateAssignment)* (WHERE
where=booleanExpression)?
+
+updateAssignment
+ : identifier EQ expression
+ ;
+```
+
+1. `update`语句仅允许修改属性（ATTRIBUTE）列的值。
+2. `WHERE` 的规则：
+ - 范围仅限于标签列（TAG）和属性列（ATTRIBUTE），不允许涉及测点列（FIELD）和时间列（TIME）。
+ - 不允许使用聚合函数
+3. 执行 SET 操作后，赋值表达式的结果应当是字符串类型，且其使用的限制应与 WHERE 子句中的表达式相同。
+4. 属性（ATTRIBUTE）列以及测点（FIELD）列的值也可通过`insert`语句来实现指定行的更新。
+
+**示例：**
+
+```SQL
+update table1 set b = a where substring(a, 1, 1) like '%'
+```
+
## 2. 数据更新
### 2.1 语法
diff --git a/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual.md
b/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual.md
index 67651d8d..67282997 100644
--- a/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual.md
+++ b/src/zh/UserGuide/Master/Table/Reference/System-Config-Manual.md
@@ -1789,6 +1789,25 @@ 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 列时，需遵循以下限制：<br> 1. 命名规范：TAG 列的值、表名和字段名禁止使用 “.” 或 “..”，且不得包含 “./” 或 “.\”
字符，否则元数据创建将失败。若名称包含文件系统不支持的字符，则会在数据写入时报错。<br>2. 大小写敏感：如果底层文件系统不区分大小写，则设备标识符（如
'd1' 与 'D1'）将被视为相同。在此情况下，若创建此类名称相似的设备，其 OBJECT 数据文件可能互相覆盖，导致数据错误。<br>3.
存储路径：OBJECT
类型数据的实际存储路径格式为：`${dataregionid}/${tablename}/${tag1}/${tag2}/.../${field}/${timestamp}.bin`。
|
+| 类型 | boolean
|
+| 默认值 | false
|
+| 改后生效方式 | 仅允许在第一次启动服务前修改
|
+
+
### 3.20 合并配置
- enable_seq_space_compaction
diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
b/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
index b7577844..16a9bc3f 100644
--- a/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
+++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Basis-Function.md
@@ -1272,7 +1272,7 @@ coalesce(value1, value2[, ...])
#### 8.1.1 cast(value AS type) → type
1. 显式地将一个值转换为指定类型。
-2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型。
+2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型，V2.0.8-beta 版本起支持 OBJECT 类型强转成 STRING
类型。
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 e5281a33..e30a9634 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
@@ -694,3 +694,45 @@ 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 类型读取函数
+
+描述：用于读取 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/Featured-Functions_timecho.md
b/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_timecho.md
index 19f58800..d9dd63ca 100644
--- a/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_timecho.md
+++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Featured-Functions_timecho.md
@@ -818,3 +818,45 @@ IoTDB> SELECT *,count(flow) OVER(PARTITION BY device ORDER
BY flow RANGE BETWEEN
|1970-01-01T08:00:01.000+08:00| d0| 5| 3|
+-----------------------------+------+----+-----+
```
+
+## 5. 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/Fill-Clause.md
b/src/zh/UserGuide/Master/Table/SQL-Manual/Fill-Clause.md
index 5bfaa241..7b05473a 100644
--- a/src/zh/UserGuide/Master/Table/SQL-Manual/Fill-Clause.md
+++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Fill-Clause.md
@@ -64,7 +64,7 @@ intervalField
IoTDB 支持以下三种空值填充方式：
-1. **`PREVIOUS`填充**：使用该列前一个非空值进行填充。
+1. **`PREVIOUS`填充**：使用该列前一个非空值进行填充，V2.0.8-beta 版本起仅该方式支持支持 OBJECT 类型。
2. **`LINEAR`填充**：使用该列前一个非空值和下一个非空值的线性插值进行填充。
3. **`Constant`填充**：使用指定的常量值进行填充。
diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
b/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
index 00b31bdb..a1ede922 100644
--- a/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
+++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Select-Clause.md
@@ -38,7 +38,7 @@ setQuantifier
```
- **SELECT 子句**: 指定了查询结果应包含的列，包含聚合函数（如 SUM、AVG、COUNT 等）以及窗口函数，在逻辑上最后执行。
-- **DISTINCT 关键字**: `SELECT DISTINCT column_name` 确保查询结果中的值是唯一的，去除重复项。
+- **DISTINCT 关键字**: `SELECT DISTINCT column_name` 确保查询结果中的值是唯一的，去除重复项。
- **COLUMNS 函数**：SELECT 子句中支持使用 COLUMNS 函数进行列筛选，并支持和表达式结合使用，使表达式的效果对所有筛选出的列生效。
## 2. 语法详释：
@@ -55,16 +55,16 @@ setQuantifier
- **聚合函数**：与聚合函数一起使用时，DISTINCT 只处理输入数据集中的非重复行。
- **GROUP BY 子句**：在 GROUP BY 子句中使用 ALL 和 DISTINCT 量词，决定是否每个重复的分组集产生不同的输出行。
-`COLUMNS` 函数：
-- **`COLUMNS(*)`**: 匹配所有列，支持结合表达式进行使用。
+`COLUMNS` 函数：
+- **`COLUMNS(*)`**: 匹配所有列，支持结合表达式进行使用。
- **`COLUMNS(regexStr) ? AS identifier`**：正则匹配
- - 匹配所有列名满足正则表达式的列，支持结合表达式进行使用。
- - 支持引用正则表达式捕获到的 groups 对列进行重命名，不写 AS 时展示原始列名（即 _coln_原始列名，其中 n 为列在结果表中的
position）。
- - 重命名用法简述：
- - regexStr 中使用圆括号设置要捕获的组；
- - 在 identifier 中使用 `'$index'` 引用捕获到的组。
-
- 注意：使用该功能时，identifier 中会包含特殊字符 '$'，所以整个 identifier 要用双引号引起来。
+ - 匹配所有列名满足正则表达式的列，支持结合表达式进行使用。
+ - 支持引用正则表达式捕获到的 groups 对列进行重命名，不写 AS 时展示原始列名（即 _coln_原始列名，其中 n 为列在结果表中的
position）。
+ - 重命名用法简述：
+ - regexStr 中使用圆括号设置要捕获的组；
+ - 在 identifier 中使用 `'$index'` 引用捕获到的组。
+
+ 注意：使用该功能时，identifier 中会包含特殊字符 '$'，所以整个 identifier 要用双引号引起来。
## 3. 示例数据
@@ -267,6 +267,37 @@ 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. 不结合表达式
@@ -301,7 +332,7 @@ IoTDB:database1> select columns('^m(.*)') AS "series_$0"
from table1 limit 5
| C| 90|
+---------------+------------------+
```
-
+
2. 结合表达式
- 单个 COLUMNS 函数
diff --git
a/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
b/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
index d292c2c1..94a36719 100644
--- a/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
+++ b/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
@@ -26,6 +26,7 @@
</tbody>
</table>
+- 不支持 Object 数据类型。
## 2. 功能详解
diff --git
a/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
b/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
index 6cd128ef..fc709298 100644
--- a/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
+++ b/src/zh/UserGuide/Master/Table/Tools-System/Data-Export-Tool_timecho.md
@@ -26,6 +26,7 @@
</tbody>
</table>
+- 不支持 Object 数据类型。
## 2. 功能详解
diff --git
a/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
b/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
index 57c7217f..38b09f2f 100644
--- a/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
+++ b/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_apache.md
@@ -38,6 +38,7 @@ IoTDB 支持三种方式进行数据导入：
</table>
- **表模型 TsFile 导入暂时只支持本地导入。**
+- 不支持 Object 数据类型。
## 2. 数据导入工具
diff --git
a/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
b/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
index eeaabf87..6d2f6a69 100644
--- a/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
+++ b/src/zh/UserGuide/Master/Table/Tools-System/Data-Import-Tool_timecho.md
@@ -38,6 +38,7 @@ IoTDB 支持三种方式进行数据导入：
</table>
- **表模型 TsFile 导入暂时只支持本地导入。**
+- 不支持 Object 数据类型。
## 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 1a25595b..71ab0447 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
@@ -81,6 +81,7 @@
- 不支持 1.x 系列版本 IoTDB 与 2.x 以及以上系列版本的 IoTDB 之间进行数据同步。
- 在进行数据同步任务时，请避免执行任何删除操作，防止两端状态不一致。
- 树模型与表模型的`pipe`及`pipe
plugins`在设计上相互隔离，建议在创建`pipe`前先通过`show`命令查询当前`-sql_dialect`参数配置下可用的内置插件，以确保语法兼容性和功能支持。
+- 不支持 Object 数据类型。
## 2. 使用说明
diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
index 8d145a69..0de1d835 100644
--- a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
@@ -81,6 +81,7 @@
- 不支持 1.x 系列版本 IoTDB 与 2.x 以及以上系列版本的 IoTDB 之间进行数据同步。
- 在进行数据同步任务时，请避免执行任何删除操作，防止两端状态不一致。
- 树模型与表模型的`pipe`及`pipe
plugins`在设计上相互隔离，建议在创建`pipe`前先通过`show`命令查询当前`-sql_dialect`参数配置下可用的内置插件，以确保语法兼容性和功能支持。
+- 不支持 Object 数据类型。
## 2. 使用说明
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 c5a35939..ad3fc190 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
@@ -66,6 +66,25 @@ 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 接口展示
``` java
diff --git
a/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
b/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
index 6bc98b93..e71d71f9 100644
--- a/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
+++ b/src/zh/UserGuide/latest-Table/API/Programming-Java-Native-API_timecho.md
@@ -66,6 +66,25 @@ 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 接口展示
``` java
diff --git a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type.md
b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type.md
index 35f8a971..1f2347c2 100644
--- a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type.md
+++ b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type.md
@@ -33,10 +33,21 @@ IoTDB 支持以下十种数据类型：
* TEXT（长字符串）
* STRING（字符串）
* BLOB（大二进制对象）
+* OBJECT（大二进制对象）
+ > V2.0.8-beta 版本起支持
* TIMESTAMP（时间戳）
* DATE（日期）
-其中，STRING 和 TEXT 类型的区别在于，STRING 类型具有更多的统计信息，能够用于优化值过滤查询。TEXT 类型适合用于存储长字符串。
+其中:
+1. STRING 和 TEXT 类型的区别在于，STRING 类型具有更多的统计信息，能够用于优化值过滤查询。TEXT 类型适合用于存储长字符串。
+2. OBJECT 和 BLOB 类型的区别如下：
+
+ | | **OBJECT**
| **BLOB**
|
+ | ----------------------
|-------------------------------------------------------------------------------------------------------------------------|
-------------------------------------------- |
+ | 写放大（越低越好） | 低（写放大系数永远为 1）
| 高（写放大系数为 2 + 合并次数）
|
+ | 空间放大（越低越好） | 低（merge & release on write）
| 高（merge on read and
release on compact） |
+ | 查询结果 | 默认查询 OBJECT 列时，返回结果如`(Object) XX.XX KB）`。 <br> 真实 OBJECT
数据存储路径位于：`${data_dir}/object_data`，可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
+
### 1.1 浮点数精度配置
@@ -57,18 +68,19 @@ CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT,
ENCODING=RLE, 'MAX_POI
各数据类型的兼容情况如下表所示：
-| 序列数据类型 | 支持的写入数据类型 |
-|--------------|-----------------------------------|
-| BOOLEAN | BOOLEAN |
-| INT32 | INT32 |
-| INT64 | INT32 INT64 TIMESTAMP |
-| FLOAT | INT32 FLOAT |
-| DOUBLE | INT32 INT64 FLOAT DOUBLE TIMESTAMP|
-| TEXT | TEXT STRING |
-| STRING | TEXT STRING |
-| BLOB | TEXT STRING BLOB |
-| TIMESTAMP | INT32 INT64 TIMESTAMP |
-| DATE | DATE |
+| 序列数据类型 | 支持的写入数据类型 |
+|-----------|------------------------------------|
+| BOOLEAN | BOOLEAN |
+| INT32 | INT32 |
+| INT64 | INT32 INT64 TIMESTAMP |
+| FLOAT | INT32 FLOAT |
+| DOUBLE | INT32 INT64 FLOAT DOUBLE TIMESTAMP |
+| TEXT | TEXT STRING |
+| STRING | TEXT STRING |
+| BLOB | TEXT STRING BLOB |
+| OBJECT | OBJECT |
+| TIMESTAMP | INT32 INT64 TIMESTAMP |
+| DATE | DATE |
## 2. 时间戳类型
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 1029cef8..07df3388 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
@@ -274,7 +274,7 @@ It costs 0.014s
* 允许 query 中的源表与目标表 table\_name 是同一个表，例如：`INSERT INTO testtb SELECT * FROM
testtb`。
* 目标表必须已存在，否则提示错误信息`550: Table 'xxx.xxx' does not exist`。
-* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert query has
mismatched column types`。
+* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持 Object 类型，不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert
query has mismatched column types`。
* 允许指定目标表的部分列，指定目标表列名时需符合以下规则：
* 必须包含时间戳列，否则提示错误信息`701: time column can not be null`
* 必须包含至少一个 FIELD 列，否则提示错误信息`701: No Field column present`
@@ -288,6 +288,59 @@ 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/Basic-Concept/Write-Updata-Data_timecho.md
b/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
index 2d4bc304..f5190f8e 100644
--- a/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
+++ b/src/zh/UserGuide/latest-Table/Basic-Concept/Write-Updata-Data_timecho.md
@@ -274,7 +274,7 @@ It costs 0.014s
* 允许 query 中的源表与目标表 table\_name 是同一个表，例如：`INSERT INTO testtb SELECT * FROM
testtb`。
* 目标表必须已存在，否则提示错误信息`550: Table 'xxx.xxx' does not exist`。
-* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert query has
mismatched column types`。
+* 查询返回列和目标表列的数量和类型需完全匹配，目前不支持 Object 类型，不支持兼容类型的转换，若类型不匹配则提示错误信息 `701: Insert
query has mismatched column types`。
* 允许指定目标表的部分列，指定目标表列名时需符合以下规则：
* 必须包含时间戳列，否则提示错误信息`701: time column can not be null`
* 必须包含至少一个 FIELD 列，否则提示错误信息`701: No Field column present`
@@ -289,6 +289,85 @@ It costs 0.014s
* 更多用户权限相关的内容，请参考[权限管理](../User-Manual/Authority-Management_timecho.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. 数据更新
+
+### 2.1 语法
+
+```SQL
+UPDATE <TABLE_NAME> SET updateAssignment (',' updateAssignment)* (WHERE
where=booleanExpression)?
+
+updateAssignment
+ : identifier EQ expression
+ ;
+```
+
+1. `update`语句仅允许修改属性（ATTRIBUTE）列的值。
+2. `WHERE` 的规则：
+ - 范围仅限于标签列（TAG）和属性列（ATTRIBUTE），不允许涉及测点列（FIELD）和时间列（TIME）。
+ - 不允许使用聚合函数
+3. 执行 SET 操作后，赋值表达式的结果应当是字符串类型，且其使用的限制应与 WHERE 子句中的表达式相同。
+4. 属性（ATTRIBUTE）列以及测点（FIELD）列的值也可通过`insert`语句来实现指定行的更新。
+
+**示例：**
+
+```SQL
+update table1 set b = a where substring(a, 1, 1) like '%'
+```
+
## 2. 数据更新
### 2.1 语法
diff --git a/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual.md
b/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual.md
index 67651d8d..67282997 100644
--- a/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual.md
+++ b/src/zh/UserGuide/latest-Table/Reference/System-Config-Manual.md
@@ -1789,6 +1789,25 @@ 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 列时，需遵循以下限制：<br> 1. 命名规范：TAG 列的值、表名和字段名禁止使用 “.” 或 “..”，且不得包含 “./” 或 “.\”
字符，否则元数据创建将失败。若名称包含文件系统不支持的字符，则会在数据写入时报错。<br>2. 大小写敏感：如果底层文件系统不区分大小写，则设备标识符（如
'd1' 与 'D1'）将被视为相同。在此情况下，若创建此类名称相似的设备，其 OBJECT 数据文件可能互相覆盖，导致数据错误。<br>3.
存储路径：OBJECT
类型数据的实际存储路径格式为：`${dataregionid}/${tablename}/${tag1}/${tag2}/.../${field}/${timestamp}.bin`。
|
+| 类型 | boolean
|
+| 默认值 | false
|
+| 改后生效方式 | 仅允许在第一次启动服务前修改
|
+
+
### 3.20 合并配置
- enable_seq_space_compaction
diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
b/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
index b7577844..16a9bc3f 100644
--- a/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
+++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Basis-Function.md
@@ -1272,7 +1272,7 @@ coalesce(value1, value2[, ...])
#### 8.1.1 cast(value AS type) → type
1. 显式地将一个值转换为指定类型。
-2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型。
+2. 可以用于将字符串（varchar）转换为数值类型，或数值转换为字符串类型，V2.0.8-beta 版本起支持 OBJECT 类型强转成 STRING
类型。
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 e5281a33..e30a9634 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
@@ -694,3 +694,45 @@ 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 类型读取函数
+
+描述：用于读取 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/Featured-Functions_timecho.md
b/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_timecho.md
index 19f58800..d9dd63ca 100644
--- a/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_timecho.md
+++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Featured-Functions_timecho.md
@@ -818,3 +818,45 @@ IoTDB> SELECT *,count(flow) OVER(PARTITION BY device ORDER
BY flow RANGE BETWEEN
|1970-01-01T08:00:01.000+08:00| d0| 5| 3|
+-----------------------------+------+----+-----+
```
+
+## 5. 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/Fill-Clause.md
b/src/zh/UserGuide/latest-Table/SQL-Manual/Fill-Clause.md
index 5bfaa241..7b05473a 100644
--- a/src/zh/UserGuide/latest-Table/SQL-Manual/Fill-Clause.md
+++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Fill-Clause.md
@@ -64,7 +64,7 @@ intervalField
IoTDB 支持以下三种空值填充方式：
-1. **`PREVIOUS`填充**：使用该列前一个非空值进行填充。
+1. **`PREVIOUS`填充**：使用该列前一个非空值进行填充，V2.0.8-beta 版本起仅该方式支持支持 OBJECT 类型。
2. **`LINEAR`填充**：使用该列前一个非空值和下一个非空值的线性插值进行填充。
3. **`Constant`填充**：使用指定的常量值进行填充。
diff --git a/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
b/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
index ae647361..a1ede922 100644
--- a/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
+++ b/src/zh/UserGuide/latest-Table/SQL-Manual/Select-Clause.md
@@ -267,6 +267,37 @@ 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 c6c81161..569da995 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
@@ -26,6 +26,7 @@
</tbody>
</table>
+- 不支持 Object 数据类型。
## 2. 功能详解
diff --git
a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
index 72da2a6f..e6b5aae1 100644
--- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
+++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md
@@ -26,6 +26,7 @@
</tbody>
</table>
+- 不支持 Object 数据类型。
## 2. 功能详解
diff --git
a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
index 57c7217f..38b09f2f 100644
--- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
+++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md
@@ -38,6 +38,7 @@ IoTDB 支持三种方式进行数据导入：
</table>
- **表模型 TsFile 导入暂时只支持本地导入。**
+- 不支持 Object 数据类型。
## 2. 数据导入工具
diff --git
a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
index eeaabf87..6d2f6a69 100644
--- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
+++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md
@@ -38,6 +38,7 @@ IoTDB 支持三种方式进行数据导入：
</table>
- **表模型 TsFile 导入暂时只支持本地导入。**
+- 不支持 Object 数据类型。
## 2. 数据导入工具
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 1a25595b..71ab0447 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
@@ -81,6 +81,7 @@
- 不支持 1.x 系列版本 IoTDB 与 2.x 以及以上系列版本的 IoTDB 之间进行数据同步。
- 在进行数据同步任务时，请避免执行任何删除操作，防止两端状态不一致。
- 树模型与表模型的`pipe`及`pipe
plugins`在设计上相互隔离，建议在创建`pipe`前先通过`show`命令查询当前`-sql_dialect`参数配置下可用的内置插件，以确保语法兼容性和功能支持。
+- 不支持 Object 数据类型。
## 2. 使用说明
diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
index 8d145a69..0de1d835 100644
--- a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
@@ -81,6 +81,7 @@
- 不支持 1.x 系列版本 IoTDB 与 2.x 以及以上系列版本的 IoTDB 之间进行数据同步。
- 在进行数据同步任务时，请避免执行任何删除操作，防止两端状态不一致。
- 树模型与表模型的`pipe`及`pipe
plugins`在设计上相互隔离，建议在创建`pipe`前先通过`show`命令查询当前`-sql_dialect`参数配置下可用的内置插件，以确保语法兼容性和功能支持。
+- 不支持 Object 数据类型。
## 2. 使用说明
