This is an automated email from the ASF dual-hosted git repository.
CritasWang 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 4996d7ef Update data model diagrams in Apache docs (#1172)
4996d7ef is described below
commit 4996d7ef9be4e39d27b912222aec5a1ef07be029
Author: leto-bbq <[email protected]>
AuthorDate: Thu Jun 25 16:33:21 2026 +0800
Update data model diagrams in Apache docs (#1172)
---
src/.vuepress/public/img/data-modeling-new-1-en.png | Bin 0 -> 429133 bytes
src/.vuepress/public/img/data-modeling-new-1.png | Bin 0 -> 327818 bytes
src/.vuepress/public/img/data-modeling-new-10-en.png | Bin 0 -> 746353 bytes
src/.vuepress/public/img/data-modeling-new-10.png | Bin 0 -> 590505 bytes
src/.vuepress/public/img/data-modeling-new-2-en.png | Bin 0 -> 681220 bytes
src/.vuepress/public/img/data-modeling-new-2.png | Bin 0 -> 506561 bytes
src/.vuepress/public/img/data-modeling-new-3.png | Bin 0 -> 233297 bytes
src/.vuepress/public/img/data-modeling-new-4-en.png | Bin 0 -> 751887 bytes
src/.vuepress/public/img/data-modeling-new-4.png | Bin 0 -> 591230 bytes
src/.vuepress/public/img/data-modeling-new-5-en.png | Bin 0 -> 299574 bytes
src/.vuepress/public/img/data-modeling-new-5.png | Bin 0 -> 256152 bytes
src/.vuepress/public/img/data-modeling-new-6-en.png | Bin 0 -> 163143 bytes
src/.vuepress/public/img/data-modeling-new-6.png | Bin 0 -> 154249 bytes
src/.vuepress/public/img/data-modeling-new-7-en.png | Bin 0 -> 891373 bytes
src/.vuepress/public/img/data-modeling-new-7.png | Bin 0 -> 670052 bytes
src/.vuepress/public/img/data-modeling-new-8-en.png | Bin 0 -> 414641 bytes
src/.vuepress/public/img/data-modeling-new-8.png | Bin 0 -> 345134 bytes
src/.vuepress/public/img/data-modeling-new-9-en.png | Bin 0 -> 535028 bytes
src/.vuepress/public/img/data-modeling-new-9.png | Bin 0 -> 523789 bytes
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
.../Data-Model-and-Terminology_apache.md | 14 +++++++-------
27 files changed, 56 insertions(+), 56 deletions(-)
diff --git a/src/.vuepress/public/img/data-modeling-new-1-en.png
b/src/.vuepress/public/img/data-modeling-new-1-en.png
new file mode 100644
index 00000000..76fc329d
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-1-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-1.png
b/src/.vuepress/public/img/data-modeling-new-1.png
new file mode 100644
index 00000000..146a417a
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-1.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-10-en.png
b/src/.vuepress/public/img/data-modeling-new-10-en.png
new file mode 100644
index 00000000..6660b794
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-10-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-10.png
b/src/.vuepress/public/img/data-modeling-new-10.png
new file mode 100644
index 00000000..a08206e5
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-10.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-2-en.png
b/src/.vuepress/public/img/data-modeling-new-2-en.png
new file mode 100644
index 00000000..e5272403
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-2-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-2.png
b/src/.vuepress/public/img/data-modeling-new-2.png
new file mode 100644
index 00000000..b32ccb94
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-2.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-3.png
b/src/.vuepress/public/img/data-modeling-new-3.png
new file mode 100644
index 00000000..f6f35fad
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-3.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-4-en.png
b/src/.vuepress/public/img/data-modeling-new-4-en.png
new file mode 100644
index 00000000..c740dc69
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-4-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-4.png
b/src/.vuepress/public/img/data-modeling-new-4.png
new file mode 100644
index 00000000..7c227d72
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-4.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-5-en.png
b/src/.vuepress/public/img/data-modeling-new-5-en.png
new file mode 100644
index 00000000..1d77f181
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-5-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-5.png
b/src/.vuepress/public/img/data-modeling-new-5.png
new file mode 100644
index 00000000..04911476
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-5.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-6-en.png
b/src/.vuepress/public/img/data-modeling-new-6-en.png
new file mode 100644
index 00000000..43ae3193
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-6-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-6.png
b/src/.vuepress/public/img/data-modeling-new-6.png
new file mode 100644
index 00000000..784d0102
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-6.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-7-en.png
b/src/.vuepress/public/img/data-modeling-new-7-en.png
new file mode 100644
index 00000000..eac2a224
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-7-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-7.png
b/src/.vuepress/public/img/data-modeling-new-7.png
new file mode 100644
index 00000000..d6f9d011
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-7.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-8-en.png
b/src/.vuepress/public/img/data-modeling-new-8-en.png
new file mode 100644
index 00000000..e7da7f84
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-8-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-8.png
b/src/.vuepress/public/img/data-modeling-new-8.png
new file mode 100644
index 00000000..0b622443
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-8.png
differ
diff --git a/src/.vuepress/public/img/data-modeling-new-9-en.png
b/src/.vuepress/public/img/data-modeling-new-9-en.png
new file mode 100644
index 00000000..9156936d
Binary files /dev/null and
b/src/.vuepress/public/img/data-modeling-new-9-en.png differ
diff --git a/src/.vuepress/public/img/data-modeling-new-9.png
b/src/.vuepress/public/img/data-modeling-new-9.png
new file mode 100644
index 00000000..0f289e8c
Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-9.png
differ
diff --git
a/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
index 0d2124dc..ddf1626c 100644
---
a/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
IoTDB supports **tree-to-table conversion**, as shown in the figure below:
-
+
This feature allows existing tree-model data to be transformed into table
views. Users can then query the same dataset using either model. Detailed
instructions are available in [Tree-to-Table
View](../User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for
creating tree-to-table views **must be executed in table mode**.
@@ -273,7 +273,7 @@ The application scenarios mainly include two categories:
- If different types of devices in the scenario have different hierarchical
paths and data point sets, create branches under the database node by device
type. Each device type can have a different data point structure.
<div style="text-align: center;">
- <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 How to mode when there are no devices, only data points?
@@ -281,7 +281,7 @@ The application scenarios mainly include two categories:
- For example, in a monitoring system for a station, each data point has a
unique number but does not correspond to any specific device.
<div style="text-align: center;">
- <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
@@ -289,7 +289,7 @@ The application scenarios mainly include two categories:
- For example, in an energy storage scenario, each layer of the structure
monitors its voltage and current. The following mode approach can be used.
<div style="text-align: center;">
- <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
</div>
@@ -325,7 +325,7 @@ The application scenarios mainly include two categories:
- Even if devices are related or have hierarchical relationships, it is
recommended to create a table for each type of device.
<div style="text-align: center;">
- <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 How to mode when there are no device identifier columns or
attribute columns?
@@ -333,7 +333,7 @@ The application scenarios mainly include two categories:
- There is no limit to the number of columns; it can reach hundreds of
thousands.
<div style="text-align: center;">
- <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
@@ -341,5 +341,5 @@ The application scenarios mainly include two categories:
- Each device has multiple sub-devices and data point information. It is
recommended to create a table for each type of device for management.
<div style="text-align: center;">
- <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
index ef9510cf..b98bd598 100644
---
a/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection(
IoTDB supports **tree-to-table conversion**, as shown in the figure below:
-
+
This feature allows existing tree-model data to be transformed into table
views. Users can then query the same dataset using either model. Detailed
instructions are available in [Tree-to-Table
View](../../latest-Table/User-Manual/Tree-to-Table_apache.md). **Note**: SQL
statements for creating tree-to-table views **must be executed in table mode**.
@@ -278,7 +278,7 @@ The application scenarios mainly include two categories:
- If different types of devices in the scenario have different hierarchical
paths and data point sets, create branches under the database node by device
type. Each device type can have a different data point structure.
<div style="text-align: center;">
- <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 How to when there are no devices, only data points?
@@ -286,7 +286,7 @@ The application scenarios mainly include two categories:
- For example, in a monitoring system for a station, each data point has a
unique number but does not correspond to any specific device.
<div style="text-align: center;">
- <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
@@ -294,7 +294,7 @@ The application scenarios mainly include two categories:
- For example, in an energy storage scenario, each layer of the structure
monitors its voltage and current. The following mode approach can be used.
<div style="text-align: center;">
- <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
</div>
@@ -330,7 +330,7 @@ The application scenarios mainly include two categories:
- Even if devices are related or have hierarchical relationships, it is
recommended to create a table for each type of device.
<div style="text-align: center;">
- <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 How to mode when there are no device identifier columns or
attribute columns?
@@ -338,7 +338,7 @@ The application scenarios mainly include two categories:
- There is no limit to the number of columns; it can reach hundreds of
thousands.
<div style="text-align: center;">
- <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
@@ -346,5 +346,5 @@ The application scenarios mainly include two categories:
- Each device has multiple sub-devices and data point information. It is
recommended to create a table for each type of device for management.
<div style="text-align: center;">
- <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
index 0d2124dc..ddf1626c 100644
---
a/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
IoTDB supports **tree-to-table conversion**, as shown in the figure below:
-
+
This feature allows existing tree-model data to be transformed into table
views. Users can then query the same dataset using either model. Detailed
instructions are available in [Tree-to-Table
View](../User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for
creating tree-to-table views **must be executed in table mode**.
@@ -273,7 +273,7 @@ The application scenarios mainly include two categories:
- If different types of devices in the scenario have different hierarchical
paths and data point sets, create branches under the database node by device
type. Each device type can have a different data point structure.
<div style="text-align: center;">
- <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 How to mode when there are no devices, only data points?
@@ -281,7 +281,7 @@ The application scenarios mainly include two categories:
- For example, in a monitoring system for a station, each data point has a
unique number but does not correspond to any specific device.
<div style="text-align: center;">
- <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
@@ -289,7 +289,7 @@ The application scenarios mainly include two categories:
- For example, in an energy storage scenario, each layer of the structure
monitors its voltage and current. The following mode approach can be used.
<div style="text-align: center;">
- <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
</div>
@@ -325,7 +325,7 @@ The application scenarios mainly include two categories:
- Even if devices are related or have hierarchical relationships, it is
recommended to create a table for each type of device.
<div style="text-align: center;">
- <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 How to mode when there are no device identifier columns or
attribute columns?
@@ -333,7 +333,7 @@ The application scenarios mainly include two categories:
- There is no limit to the number of columns; it can reach hundreds of
thousands.
<div style="text-align: center;">
- <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
@@ -341,5 +341,5 @@ The application scenarios mainly include two categories:
- Each device has multiple sub-devices and data point information. It is
recommended to create a table for each type of device for management.
<div style="text-align: center;">
- <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
index ef9510cf..b98bd598 100644
---
a/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection(
IoTDB supports **tree-to-table conversion**, as shown in the figure below:
-
+
This feature allows existing tree-model data to be transformed into table
views. Users can then query the same dataset using either model. Detailed
instructions are available in [Tree-to-Table
View](../../latest-Table/User-Manual/Tree-to-Table_apache.md). **Note**: SQL
statements for creating tree-to-table views **must be executed in table mode**.
@@ -278,7 +278,7 @@ The application scenarios mainly include two categories:
- If different types of devices in the scenario have different hierarchical
paths and data point sets, create branches under the database node by device
type. Each device type can have a different data point structure.
<div style="text-align: center;">
- <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 How to when there are no devices, only data points?
@@ -286,7 +286,7 @@ The application scenarios mainly include two categories:
- For example, in a monitoring system for a station, each data point has a
unique number but does not correspond to any specific device.
<div style="text-align: center;">
- <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
@@ -294,7 +294,7 @@ The application scenarios mainly include two categories:
- For example, in an energy storage scenario, each layer of the structure
monitors its voltage and current. The following mode approach can be used.
<div style="text-align: center;">
- <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
</div>
@@ -330,7 +330,7 @@ The application scenarios mainly include two categories:
- Even if devices are related or have hierarchical relationships, it is
recommended to create a table for each type of device.
<div style="text-align: center;">
- <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 How to mode when there are no device identifier columns or
attribute columns?
@@ -338,7 +338,7 @@ The application scenarios mainly include two categories:
- There is no limit to the number of columns; it can reach hundreds of
thousands.
<div style="text-align: center;">
- <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
@@ -346,5 +346,5 @@ The application scenarios mainly include two categories:
- Each device has multiple sub-devices and data point information. It is
recommended to create a table for each type of device for management.
<div style="text-align: center;">
- <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
index c951dcf6..594884a2 100644
---
a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
IoTDB 提供了树转表功能，如下图所示：
-
+
该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_apache.md)，需要注意的是：**创建树转表视图的
SQL 语句只允许在表模型下执行**。
@@ -274,7 +274,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
<div style="text-align: center;">
- <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
@@ -282,7 +282,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
<div style="text-align: center;">
- <img src="/img/data-modeling04.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -290,7 +290,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
<div style="text-align: center;">
- <img src="/img/Modeling-scheme05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4.png" alt="" style="width: 70%;"/>
</div>
@@ -326,7 +326,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
<div style="text-align: center;">
- <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
@@ -334,7 +334,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 列数没有数量限制，可以达到数十万以上。
<div style="text-align: center;">
- <img src="/img/data-modeling07.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -342,5 +342,5 @@ IoTDB 提供了树转表功能，如下图所示：
- 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
<div style="text-align: center;">
- <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
index fb63d7fe..911a612f 100644
---
a/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection(
IoTDB 提供了树转表功能，如下图所示：
-
+
该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_apache.md)，需要注意的是：**创建树转表视图的
SQL 语句只允许在表模型下执行**。
@@ -278,7 +278,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
<div style="text-align: center;">
- <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
@@ -286,7 +286,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
<div style="text-align: center;">
- <img src="/img/data-modeling04.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -294,7 +294,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
<div style="text-align: center;">
- <img src="/img/Modeling-scheme05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4.png" alt="" style="width: 70%;"/>
</div>
@@ -330,7 +330,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
<div style="text-align: center;">
- <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
@@ -338,7 +338,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 列数没有数量限制，可以达到数十万以上。
<div style="text-align: center;">
- <img src="/img/data-modeling07.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -346,5 +346,5 @@ IoTDB 提供了树转表功能，如下图所示：
- 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
<div style="text-align: center;">
- <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
index c951dcf6..594884a2 100644
---
a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
IoTDB 提供了树转表功能，如下图所示：
-
+
该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_apache.md)，需要注意的是：**创建树转表视图的
SQL 语句只允许在表模型下执行**。
@@ -274,7 +274,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
<div style="text-align: center;">
- <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
@@ -282,7 +282,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
<div style="text-align: center;">
- <img src="/img/data-modeling04.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -290,7 +290,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
<div style="text-align: center;">
- <img src="/img/Modeling-scheme05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4.png" alt="" style="width: 70%;"/>
</div>
@@ -326,7 +326,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
<div style="text-align: center;">
- <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
@@ -334,7 +334,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 列数没有数量限制，可以达到数十万以上。
<div style="text-align: center;">
- <img src="/img/data-modeling07.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -342,5 +342,5 @@ IoTDB 提供了树转表功能，如下图所示：
- 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
<div style="text-align: center;">
- <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7.png" alt="" style="width: 70%;"/>
</div>
diff --git
a/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
b/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
index fb63d7fe..911a612f 100644
---
a/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
+++
b/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md
@@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection(
IoTDB 提供了树转表功能，如下图所示：
-
+
该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_apache.md)，需要注意的是：**创建树转表视图的
SQL 语句只允许在表模型下执行**。
@@ -278,7 +278,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
<div style="text-align: center;">
- <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-2.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
@@ -286,7 +286,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
<div style="text-align: center;">
- <img src="/img/data-modeling04.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
</div>
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -294,7 +294,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
<div style="text-align: center;">
- <img src="/img/Modeling-scheme05.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-4.png" alt="" style="width: 70%;"/>
</div>
@@ -330,7 +330,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
<div style="text-align: center;">
- <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-5.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
@@ -338,7 +338,7 @@ IoTDB 提供了树转表功能，如下图所示：
- 列数没有数量限制，可以达到数十万以上。
<div style="text-align: center;">
- <img src="/img/data-modeling07.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-6.png" alt="" style="width: 70%;"/>
</div>
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
@@ -346,5 +346,5 @@ IoTDB 提供了树转表功能，如下图所示：
- 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
<div style="text-align: center;">
- <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
+ <img src="/img/data-modeling-new-7.png" alt="" style="width: 70%;"/>
</div>
