Both the modeling and writing chapters have added explanations for no…

src/UserGuide/Master/Tree/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/Master/Tree/Basic-Concept/Write-Delete-Data.md

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md#insert-data) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Basic-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V0.13.x/Data-Concept/Data-Model-and-Terminology.md

@@ -53,6 +53,8 @@ After a storage group is set, the ancestral layers, children and descendant laye
 
 The Layer Name of storage group can only consist of characters, numbers and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically identified and registered in the storage group, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V0.13.x/Write-And-Delete-Data/Write-Data.md

@@ -29,6 +29,8 @@ This section mainly introduces the use of [INSERT SQL statement](../Reference/SQ
 
 The [INSERT SQL statement](../Reference/SQL-Reference.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Data-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Data-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically identified and registered in the storage group, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.0.x/Data-Concept/Data-Model-and-Terminology.md

@@ -55,6 +55,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.0.x/Write-Data/Write-Data.md

@@ -31,6 +31,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../Reference/SQL-Reference.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Data-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Data-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.1.x/Data-Concept/Data-Model-and-Terminology.md

@@ -55,6 +55,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.1.x/Write-Data/Write-Data.md

@@ -31,6 +31,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../Reference/SQL-Reference.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Data-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Data-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.2.x/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ The Layer Name of database can only consist of characters, numbers, and undersco
 
 > Note ：Database name do not support enclosing * in back quotes, e.g., root.\ ` * \ `, but the rest of the level is free of this restriction.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.2.x/User-Manual/Write-Delete-Data.md

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Basic-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.3.0-2/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.3.0-2/User-Manual/Write-Delete-Data.md

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md#insert-data) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Basic-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V2.0.1/Tree/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V2.0.1/Tree/Basic-Concept/Write-Delete-Data.md

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md#insert-data) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Basic-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/latest/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/latest/Basic-Concept/Write-Delete-Data.md

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md#insert-data) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Basic-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/Data-Type.md)).
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/zh/UserGuide/Master/Tree/Basic-Concept/Data-Model-and-Terminology.md

@@ -49,6 +49,8 @@ IoTDB 模型结构涉及的基本概念在下文将做详细叙述。
 
 Database 节点名只支持中英文字符、数字和下划线的组合。例如`root.数据库_1` 。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 ## 设备（Device）
 
 **一个物理设备**，也称实体（Entity），是在实际场景中拥有物理量的设备或装置。在 IoTDB 当中，所有的物理量都有其对应的归属实体。实体无需手动创建，默认为倒数第二层。实体是管理的一组时间序列的组合，可以是一个物理设备、测量装置、传感器集合等。

src/zh/UserGuide/Master/Tree/Basic-Concept/Write-Delete-Data.md

@@ -33,6 +33,8 @@ IoTDB 为用户提供多种插入实时数据的方式，例如在 [Cli/Shell 
 
 使用 INSERT 语句可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的时间戳和一个数值或布尔值、字符串类型的传感器采集值组成。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例 ，它们的数据类型分别为 BOOLEAN 和 TEXT。
 
 单列数据插入示例代码如下：

src/zh/UserGuide/V0.13.x/Data-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ IoTDB 模型结构涉及的基本概念在下文将做详细叙述。
 
 存储组节点名只支持中英文字符、数字、和下划线的组合。例如`root. 存储组_1` 。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，存储组中将自动识别并注册所需的元数据，实现自动建模。
+
 #### 路径（Path）
 
 路径（`path`）是指符合以下约束的表达式：

src/zh/UserGuide/V0.13.x/Write-And-Delete-Data/Write-Data.md

@@ -30,6 +30,8 @@ IoTDB 为用户提供多种插入实时数据的方式，例如在 [Cli/Shell 
 
 使用 INSERT 语句可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的时间戳和一个数值或布尔值、字符串类型的传感器采集值组成。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，存储组中将自动识别并注册所需的元数据，实现自动建模。
+
 在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例 ，它们的数据类型分别为 BOOLEAN 和 TEXT。
 
 单列数据插入示例代码如下：

src/zh/UserGuide/V1.0.x/Data-Concept/Data-Model-and-Terminology.md

@@ -59,6 +59,8 @@ IoTDB 模型结构涉及的基本概念在下文将做详细叙述。
 
 Database 节点名只支持中英文字符、数字和下划线的组合。例如`root.数据库_1` 。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 ### 路径（Path）
 
 路径（`path`）是指符合以下约束的表达式：

src/zh/UserGuide/V1.0.x/Write-Data/Write-Data.md

@@ -32,6 +32,8 @@ IoTDB 为用户提供多种插入实时数据的方式，例如在 [Cli/Shell 
 
 使用 INSERT 语句可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的时间戳和一个数值或布尔值、字符串类型的传感器采集值组成。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例 ，它们的数据类型分别为 BOOLEAN 和 TEXT。
 
 单列数据插入示例代码如下：

src/zh/UserGuide/V1.1.x/Data-Concept/Data-Model-and-Terminology.md

@@ -59,6 +59,8 @@ IoTDB 模型结构涉及的基本概念在下文将做详细叙述。
 
 Database 节点名只支持中英文字符、数字和下划线的组合。例如`root.数据库_1` 。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 ### 路径（Path）
 
 路径（`path`）是指符合以下约束的表达式：

src/zh/UserGuide/V1.1.x/Write-Data/Write-Data.md

@@ -32,6 +32,8 @@ IoTDB 为用户提供多种插入实时数据的方式，例如在 [Cli/Shell 
 
 使用 INSERT 语句可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的时间戳和一个数值或布尔值、字符串类型的传感器采集值组成。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例 ，它们的数据类型分别为 BOOLEAN 和 TEXT。
 
 单列数据插入示例代码如下：

src/zh/UserGuide/V1.2.x/Basic-Concept/Data-Model-and-Terminology.md

@@ -51,6 +51,8 @@ Database 节点名只支持中英文字符、数字和下划线的组合。例
 
 > 注意 ：Database 节点名不支持将*用反引号括起来，如root.\` * \`,其余层级则无此限制。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 ## 设备（Device）
 
 **一个物理设备**，也称实体（Entity），是在实际场景中拥有物理量的设备或装置。在 IoTDB 当中，所有的物理量都有其对应的归属实体。实体无需手动创建，默认为倒数第二层。实体是管理的一组时间序列的组合，可以是一个物理设备、测量装置、传感器集合等。

src/zh/UserGuide/V1.2.x/User-Manual/Write-Delete-Data.md

@@ -33,6 +33,8 @@ IoTDB 为用户提供多种插入实时数据的方式，例如在 [Cli/Shell 
 
 使用 INSERT 语句可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的时间戳和一个数值或布尔值、字符串类型的传感器采集值组成。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例 ，它们的数据类型分别为 BOOLEAN 和 TEXT。
 
 单列数据插入示例代码如下：

src/zh/UserGuide/V1.3.0-2/Basic-Concept/Data-Model-and-Terminology.md

@@ -49,6 +49,8 @@ IoTDB 模型结构涉及的基本概念在下文将做详细叙述。
 
 Database 节点名只支持中英文字符、数字和下划线的组合。例如`root.数据库_1` 。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 ## 设备（Device）
 
 **一个物理设备**，也称实体（Entity），是在实际场景中拥有物理量的设备或装置。在 IoTDB 当中，所有的物理量都有其对应的归属实体。实体无需手动创建，默认为倒数第二层。实体是管理的一组时间序列的组合，可以是一个物理设备、测量装置、传感器集合等。

src/zh/UserGuide/V1.3.0-2/User-Manual/Write-Delete-Data.md

@@ -33,6 +33,8 @@ IoTDB 为用户提供多种插入实时数据的方式，例如在 [Cli/Shell 
 
 使用 INSERT 语句可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的时间戳和一个数值或布尔值、字符串类型的传感器采集值组成。
 
+**无模式写入**：可以在未定义元数据时， 通过 insert 语句直接写入数据，数据库中将自动识别并注册所需的元数据，实现自动建模。
+
 在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例 ，它们的数据类型分别为 BOOLEAN 和 TEXT。
 
 单列数据插入示例代码如下：