This is an automated email from the ASF dual-hosted git repository.

zhangzhengming 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 ddb3b4fd remove float precision from table (#1040)
ddb3b4fd is described below

commit ddb3b4fd0e18ec36dd07cec9330f11d053d73fbd
Author: leto-b <[email protected]>
AuthorDate: Wed Apr 1 11:47:27 2026 +0800

    remove float precision from table (#1040)
---
 .../Master/Table/Background-knowledge/Data-Type_apache.md  | 14 +-------------
 .../Master/Table/Background-knowledge/Data-Type_timecho.md | 13 +------------
 .../latest-Table/Background-knowledge/Data-Type_apache.md  | 14 +-------------
 .../latest-Table/Background-knowledge/Data-Type_timecho.md | 13 +------------
 .../Master/Table/Background-knowledge/Data-Type_apache.md  | 13 +------------
 .../Master/Table/Background-knowledge/Data-Type_timecho.md | 13 +------------
 .../latest-Table/Background-knowledge/Data-Type_apache.md  | 13 +------------
 .../latest-Table/Background-knowledge/Data-Type_timecho.md | 13 +------------
 8 files changed, 8 insertions(+), 98 deletions(-)

diff --git 
a/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md 
b/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
index 533d8326..955960d6 100644
--- a/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
+++ b/src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
@@ -51,19 +51,7 @@ The differences between **OBJECT** and **BLOB** types are as 
follows:
 | **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.
-
-For example:  
-
-```SQL
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-If not specified, the system will use the configuration in the 
`iotdb-system.properties` file under the `float_precision` item (default is 2 
decimal places).  
-
-### 1.2 Data Type Compatibility
+### 1.1 Data Type Compatibility
 
 If the written data type does not match the registered data type of a series:  
 
diff --git 
a/src/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md 
b/src/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
index 15b21207..3461a7a9 100644
--- a/src/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
+++ b/src/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
@@ -51,19 +51,8 @@ The differences between **OBJECT** and **BLOB** types are as 
follows:
 | **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.
-
-For example:  
-
-```SQL
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-If not specified, the system will use the configuration in the 
`iotdb-system.properties` file under the `float_precision` item (default is 2 
decimal places).  
-
-### 1.2 Data Type Compatibility
+### 1.1 Data Type Compatibility
 
 If the written data type does not match the registered data type of a series:  
 
diff --git 
a/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md 
b/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
index 533d8326..955960d6 100644
--- a/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
+++ b/src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
@@ -51,19 +51,7 @@ The differences between **OBJECT** and **BLOB** types are as 
follows:
 | **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.
-
-For example:  
-
-```SQL
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-If not specified, the system will use the configuration in the 
`iotdb-system.properties` file under the `float_precision` item (default is 2 
decimal places).  
-
-### 1.2 Data Type Compatibility
+### 1.1 Data Type Compatibility
 
 If the written data type does not match the registered data type of a series:  
 
diff --git 
a/src/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md 
b/src/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
index 15b21207..3461a7a9 100644
--- a/src/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
+++ b/src/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
@@ -51,19 +51,8 @@ The differences between **OBJECT** and **BLOB** types are as 
follows:
 | **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.
-
-For example:  
-
-```SQL
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-If not specified, the system will use the configuration in the 
`iotdb-system.properties` file under the `float_precision` item (default is 2 
decimal places).  
-
-### 1.2 Data Type Compatibility
+### 1.1 Data Type Compatibility
 
 If the written data type does not match the registered data type of a series:  
 
diff --git 
a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md 
b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
index 65eb49d7..0a2ab436 100644
--- a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
+++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
  | 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 
数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
 
 
-### 1.1 浮点数精度配置
-
-对于 **FLOAT** 与 **DOUBLE** 类型的序列,如果编码方式采用 `RLE`或 `TS_2DIFF`,可以在创建序列时通过 
`MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
-
-例如,
-```sql
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 
[float_precision](../Reference/System-Config-Manual_apache.md) 项配置(默认为 2 位)。
-
-### 1.2 数据类型兼容性
+### 1.1 数据类型兼容性
 
 当写入数据的类型与序列注册的数据类型不一致时,
 - 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。
diff --git 
a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md 
b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
index d995b6de..c0af2749 100644
--- a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
+++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
  | 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 
数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
 
 
-### 1.1 浮点数精度配置
-
-对于 **FLOAT** 与 **DOUBLE** 类型的序列,如果编码方式采用 `RLE`或 `TS_2DIFF`,可以在创建序列时通过 
`MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
-
-例如,
-```sql
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 
[float_precision](../Reference/System-Config-Manual_timecho.md) 项配置(默认为 2 位)。
-
-### 1.2 数据类型兼容性
+### 1.1 数据类型兼容性
 
 当写入数据的类型与序列注册的数据类型不一致时,
 - 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。
diff --git 
a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md 
b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
index 65eb49d7..0a2ab436 100644
--- a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
+++ b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
  | 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 
数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
 
 
-### 1.1 浮点数精度配置
-
-对于 **FLOAT** 与 **DOUBLE** 类型的序列,如果编码方式采用 `RLE`或 `TS_2DIFF`,可以在创建序列时通过 
`MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
-
-例如,
-```sql
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 
[float_precision](../Reference/System-Config-Manual_apache.md) 项配置(默认为 2 位)。
-
-### 1.2 数据类型兼容性
+### 1.1 数据类型兼容性
 
 当写入数据的类型与序列注册的数据类型不一致时,
 - 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。
diff --git 
a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md 
b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
index d995b6de..c0af2749 100644
--- a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
+++ b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
  | 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 
数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
 
 
-### 1.1 浮点数精度配置
-
-对于 **FLOAT** 与 **DOUBLE** 类型的序列,如果编码方式采用 `RLE`或 `TS_2DIFF`,可以在创建序列时通过 
`MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
-
-例如,
-```sql
-CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 
'MAX_POINT_NUMBER'='2';
-```
-
-若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 
[float_precision](../Reference/System-Config-Manual_timecho.md) 项配置(默认为 2 位)。
-
-### 1.2 数据类型兼容性
+### 1.1 数据类型兼容性
 
 当写入数据的类型与序列注册的数据类型不一致时,
 - 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。

Reply via email to