Skip to content

Commit ddb3b4f

Browse files
authored
remove float precision from table (#1040)
1 parent edb6a35 commit ddb3b4f

File tree

8 files changed

+8
-98
lines changed

8 files changed

+8
-98
lines changed

src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,7 @@ The differences between **OBJECT** and **BLOB** types are as follows:
5151
| **Space Amplification** (Lower is better) | Low (Merge & release on write) | High (Merge on read and release on compact) |
5252
| **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 |
5353

54-
### 1.1 Floating-Point Precision Configuration
55-
56-
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.
57-
58-
For example:
59-
60-
```SQL
61-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
62-
```
63-
64-
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).
65-
66-
### 1.2 Data Type Compatibility
54+
### 1.1 Data Type Compatibility
6755

6856
If the written data type does not match the registered data type of a series:
6957

src/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,8 @@ The differences between **OBJECT** and **BLOB** types are as follows:
5151
| **Space Amplification** (Lower is better) | Low (Merge & release on write) | High (Merge on read and release on compact) |
5252
| **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 |
5353

54-
### 1.1 Floating-Point Precision Configuration
5554

56-
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.
57-
58-
For example:
59-
60-
```SQL
61-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
62-
```
63-
64-
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).
65-
66-
### 1.2 Data Type Compatibility
55+
### 1.1 Data Type Compatibility
6756

6857
If the written data type does not match the registered data type of a series:
6958

src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,7 @@ The differences between **OBJECT** and **BLOB** types are as follows:
5151
| **Space Amplification** (Lower is better) | Low (Merge & release on write) | High (Merge on read and release on compact) |
5252
| **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 |
5353

54-
### 1.1 Floating-Point Precision Configuration
55-
56-
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.
57-
58-
For example:
59-
60-
```SQL
61-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
62-
```
63-
64-
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).
65-
66-
### 1.2 Data Type Compatibility
54+
### 1.1 Data Type Compatibility
6755

6856
If the written data type does not match the registered data type of a series:
6957

src/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,8 @@ The differences between **OBJECT** and **BLOB** types are as follows:
5151
| **Space Amplification** (Lower is better) | Low (Merge & release on write) | High (Merge on read and release on compact) |
5252
| **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 |
5353

54-
### 1.1 Floating-Point Precision Configuration
5554

56-
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.
57-
58-
For example:
59-
60-
```SQL
61-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
62-
```
63-
64-
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).
65-
66-
### 1.2 Data Type Compatibility
55+
### 1.1 Data Type Compatibility
6756

6857
If the written data type does not match the registered data type of a series:
6958

src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
4949
| 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
5050

5151

52-
### 1.1 浮点数精度配置
53-
54-
对于 **FLOAT****DOUBLE** 类型的序列,如果编码方式采用 `RLE``TS_2DIFF`,可以在创建序列时通过 `MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
55-
56-
例如,
57-
```sql
58-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
59-
```
60-
61-
若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 [float_precision](../Reference/System-Config-Manual_apache.md) 项配置(默认为 2 位)。
62-
63-
### 1.2 数据类型兼容性
52+
### 1.1 数据类型兼容性
6453

6554
当写入数据的类型与序列注册的数据类型不一致时,
6655
- 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。

src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
4949
| 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
5050

5151

52-
### 1.1 浮点数精度配置
53-
54-
对于 **FLOAT****DOUBLE** 类型的序列,如果编码方式采用 `RLE``TS_2DIFF`,可以在创建序列时通过 `MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
55-
56-
例如,
57-
```sql
58-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
59-
```
60-
61-
若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 [float_precision](../Reference/System-Config-Manual_timecho.md) 项配置(默认为 2 位)。
62-
63-
### 1.2 数据类型兼容性
52+
### 1.1 数据类型兼容性
6453

6554
当写入数据的类型与序列注册的数据类型不一致时,
6655
- 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。

src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
4949
| 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
5050

5151

52-
### 1.1 浮点数精度配置
53-
54-
对于 **FLOAT****DOUBLE** 类型的序列,如果编码方式采用 `RLE``TS_2DIFF`,可以在创建序列时通过 `MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
55-
56-
例如,
57-
```sql
58-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
59-
```
60-
61-
若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 [float_precision](../Reference/System-Config-Manual_apache.md) 项配置(默认为 2 位)。
62-
63-
### 1.2 数据类型兼容性
52+
### 1.1 数据类型兼容性
6453

6554
当写入数据的类型与序列注册的数据类型不一致时,
6655
- 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。

src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -49,18 +49,7 @@ IoTDB 支持以下十种数据类型:
4949
| 查询结果 | 默认查询 OBJECT 列时,返回结果如`(Object) XX.XX KB)`。 <br> 真实 OBJECT 数据存储路径位于:`${data_dir}/object_data`,可通过 `READ_OBJECT` 函数读取其真实内容 | 直接返回真实的二进制内容 |
5050

5151

52-
### 1.1 浮点数精度配置
53-
54-
对于 **FLOAT****DOUBLE** 类型的序列,如果编码方式采用 `RLE``TS_2DIFF`,可以在创建序列时通过 `MAX_POINT_NUMBER` 属性指定浮点数的小数点后位数。
55-
56-
例如,
57-
```sql
58-
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2';
59-
```
60-
61-
若不指定,系统会按照配置文件 `iotdb-system.properties` 中的 [float_precision](../Reference/System-Config-Manual_timecho.md) 项配置(默认为 2 位)。
62-
63-
### 1.2 数据类型兼容性
52+
### 1.1 数据类型兼容性
6453

6554
当写入数据的类型与序列注册的数据类型不一致时,
6655
- 如果序列数据类型不兼容写入数据类型,系统会给出错误提示。

0 commit comments

Comments
 (0)