Skip to content

remove float precision from table #1040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
leto-b wants to merge 1 commit into
base: main
Choose a base branch
from
Open

remove float precision from table #1040

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 1 addition & 13 deletions src/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
13 changes: 1 addition & 12 deletions src/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
14 changes: 1 addition & 13 deletions src/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
13 changes: 1 addition & 12 deletions src/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
13 changes: 1 addition & 12 deletions src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 数据类型兼容性

当写入数据的类型与序列注册的数据类型不一致时，
- 如果序列数据类型不兼容写入数据类型，系统会给出错误提示。
Expand Down
13 changes: 1 addition & 12 deletions src/zh/UserGuide/Master/Table/Background-knowledge/Data-Type_timecho.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 数据类型兼容性

当写入数据的类型与序列注册的数据类型不一致时，
- 如果序列数据类型不兼容写入数据类型，系统会给出错误提示。
Expand Down
13 changes: 1 addition & 12 deletions src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 数据类型兼容性

当写入数据的类型与序列注册的数据类型不一致时，
- 如果序列数据类型不兼容写入数据类型，系统会给出错误提示。
Expand Down
13 changes: 1 addition & 12 deletions src/zh/UserGuide/latest-Table/Background-knowledge/Data-Type_timecho.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 数据类型兼容性

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