This is an automated email from the ASF dual-hosted git repository.
haonan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iotdb.git
The following commit(s) were added to refs/heads/master by this push:
new fd301c3 [DOCUMENTATION] fix bold syntax error (#4092)
fd301c3 is described below
commit fd301c3d5ad20f15671729d06306e68cda4d7ab6
Author: Qian.Sun <[email protected]>
AuthorDate: Fri Oct 8 21:06:02 2021 +0800
[DOCUMENTATION] fix bold syntax error (#4092)
---
docs/UserGuide/Data-Concept/Data-Type.md | 12 +++++++++---
docs/UserGuide/Data-Concept/Encoding.md | 4 +++-
.../DML-Data-Manipulation-Language.md | 20 +++++++++++++++-----
docs/UserGuide/System-Tools/Monitor-and-Log-Tools.md | 6 ++++--
docs/zh/UserGuide/Advanced-Features/Triggers.md | 2 +-
docs/zh/UserGuide/Data-Concept/Data-Type.md | 14 ++++++++++----
docs/zh/UserGuide/Data-Concept/Encoding.md | 4 +++-
.../DML-Data-Manipulation-Language.md | 16 ++++++++++++----
.../UserGuide/System-Tools/Monitor-and-Log-Tools.md | 4 +++-
9 files changed, 60 insertions(+), 22 deletions(-)
diff --git a/docs/UserGuide/Data-Concept/Data-Type.md
b/docs/UserGuide/Data-Concept/Data-Type.md
index 6406f2c..2e309c0 100644
--- a/docs/UserGuide/Data-Concept/Data-Type.md
+++ b/docs/UserGuide/Data-Concept/Data-Type.md
@@ -53,7 +53,9 @@ The timestamp is the time point at which data is produced. It
includes absolute
Absolute timestamps in IoTDB are divided into two types: LONG and DATETIME
(including DATETIME-INPUT and DATETIME-DISPLAY). When a user inputs a
timestamp, he can use a LONG type timestamp or a DATETIME-INPUT type timestamp,
and the supported formats of the DATETIME-INPUT type timestamp are shown in the
table below:
-<center>**Supported formats of DATETIME-INPUT type timestamp**
+<center>
+
+**Supported formats of DATETIME-INPUT type timestamp**
@@ -78,7 +80,9 @@ Absolute timestamps in IoTDB are divided into two types: LONG
and DATETIME (incl
IoTDB can support LONG types and DATETIME-DISPLAY types when displaying
timestamps. The DATETIME-DISPLAY type can support user-defined time formats.
The syntax of the custom time format is shown in the table below:
-<center>**The syntax of the custom time format**
+<center>
+
+**The syntax of the custom time format**
| Symbol | Meaning | Presentation | Examples
|
@@ -127,7 +131,9 @@ Relative time refers to the time relative to the server
time ```now()``` and ```
```
- <center>**The syntax of the duration unit**
+ <center>
+
+**The syntax of the duration unit**
| Symbol | Meaning | Presentation | Examples |
diff --git a/docs/UserGuide/Data-Concept/Encoding.md
b/docs/UserGuide/Data-Concept/Encoding.md
index 61dd4ec..ae94bb4 100644
--- a/docs/UserGuide/Data-Concept/Encoding.md
+++ b/docs/UserGuide/Data-Concept/Encoding.md
@@ -54,7 +54,9 @@ DICTIONARY encoding is lossless. It is suitable for TEXT data
with low cardinali
The five encodings described in the previous sections are applicable to
different data types. If the correspondence is wrong, the time series cannot be
created correctly. The correspondence between the data type and its supported
encodings is summarized in the Table below.
-<center> **The correspondence between the data type and its supported
encodings**
+<center>
+
+**The correspondence between the data type and its supported encodings**
|Data Type |Supported Encoding|
|:---:|:---:|
diff --git
a/docs/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
b/docs/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
index 116f185..6f038e3 100644
--- a/docs/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
+++ b/docs/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
@@ -995,7 +995,9 @@ select <path> from <prefixPath> where time = <T>
fill(<data_type>[previous, <bef
Detailed descriptions of all parameters are given in Table 3-4.
-<center>**Table 3-4 Previous fill paramter list**
+<center>
+
+**Table 3-4 Previous fill paramter list**
|Parameter name (case insensitive)|Interpretation|
|:---|:---|
@@ -1048,7 +1050,9 @@ select <path> from <prefixPath> where time = <T>
fill(<data_type>[linear, <befor
```
Detailed descriptions of all parameters are given in Table 3-5.
-<center>**Table 3-5 Linear fill paramter list**
+<center>
+
+**Table 3-5 Linear fill paramter list**
|Parameter name (case insensitive)|Interpretation|
|:---|:---|
@@ -1091,7 +1095,9 @@ select <path> from <prefixPath> where time = <T>
fill(<data_type>[constant]…)
```
Detailed descriptions of all parameters are given in Table 3-6.
-<center>**Table 3-6 Specific value fill paramter list**
+<center>
+
+**Table 3-6 Specific value fill paramter list**
|Parameter name (case insensitive)|Interpretation|
|:---|:---|
@@ -1128,7 +1134,9 @@ It costs 0.007s
Data types and the supported fill methods are shown in Table 3-6.
-<center>**Table 3-6 Data types and the supported fill methods**
+<center>
+
+**Table 3-6 Data types and the supported fill methods**
|Data Type|Supported Fill Methods|
|:---|:---|
@@ -1142,7 +1150,9 @@ Data types and the supported fill methods are shown in
Table 3-6.
When the fill method is not specified, each data type bears its own default
fill methods and parameters. The corresponding relationship is shown in Table
3-7.
-<center>**Table 3-7 Default fill methods and parameters for various data
types**
+<center>
+
+**Table 3-7 Default fill methods and parameters for various data types**
|Data Type|Default Fill Methods and Parameters|
|:---|:---|
diff --git a/docs/UserGuide/System-Tools/Monitor-and-Log-Tools.md
b/docs/UserGuide/System-Tools/Monitor-and-Log-Tools.md
index 9975505..3c70de4 100644
--- a/docs/UserGuide/System-Tools/Monitor-and-Log-Tools.md
+++ b/docs/UserGuide/System-Tools/Monitor-and-Log-Tools.md
@@ -87,7 +87,7 @@ The data can also be written as some time series on disk. To
enable it, set `ena
At present, the monitor system can be divided into two modules: global writing
statistics and storage group writing statistics. The global statistics records
the number of total points and requests, and the storage group statistics
counts the write data of each storage group.
-The system sets the collection granularity of the monitoring module to
**update the statistical information once one data file is flushed into the
disk **, so the data accuracy may be different from the actual situation. To
obtain accurate information, **Please call the `flush` method before querying
**.
+The system sets the collection granularity of the monitoring module to
**update the statistical information once one data file is flushed into the
disk**, so the data accuracy may be different from the actual situation. To
obtain accurate information, **Please call the `flush` method before
querying**.
Here are the writing data statistics (the range supported is shown in
brackets):
@@ -151,7 +151,9 @@ To grasp the performance of iotdb, this module is added to
count the time-consum
location：conf/iotdb-engine.properties
-<center>**Table -parameter and description**
+<center>
+
+**Table -parameter and description**
|Parameter|Default Value|Description|
|:---|:---|:---|
diff --git a/docs/zh/UserGuide/Advanced-Features/Triggers.md
b/docs/zh/UserGuide/Advanced-Features/Triggers.md
index 673dbbc..d2a5126 100644
--- a/docs/zh/UserGuide/Advanced-Features/Triggers.md
+++ b/docs/zh/UserGuide/Advanced-Features/Triggers.md
@@ -616,7 +616,7 @@ alertManagerHandler.onEvent(new
AlertManagerEvent(alertName, extraLabels, annota
## 完整的 Maven 示例项目
-如果您使用 [Maven](http://search.maven.org/)，可以参考我们编写的示例项目** trigger-example**。
+如果您使用 [Maven](http://search.maven.org/)，可以参考我们编写的示例项目 **trigger-example**。
您可以在 [这里](https://github.com/apache/iotdb/tree/master/example/trigger) 找到它。
diff --git a/docs/zh/UserGuide/Data-Concept/Data-Type.md
b/docs/zh/UserGuide/Data-Concept/Data-Type.md
index 3fde98d..5f90527 100644
--- a/docs/zh/UserGuide/Data-Concept/Data-Type.md
+++ b/docs/zh/UserGuide/Data-Concept/Data-Type.md
@@ -32,7 +32,7 @@ IoTDB 支持：
一共六种数据类型。
-其中** FLOAT **与** DOUBLE **类型的序列，如果编码方式采用 [RLE](Encoding.md) 或
[TS_2DIFF](Encoding.md) 可以指定
MAX_POINT_NUMBER，该项为浮点数的小数点后位数，若不指定则系统会根据配置文件`iotdb-engine.properties`文件中的
[float_precision 项](../Appendix/Config-Manual.md) 配置。
+其中 **FLOAT** 与 **DOUBLE** 类型的序列，如果编码方式采用 [RLE](Encoding.md) 或
[TS_2DIFF](Encoding.md) 可以指定
MAX_POINT_NUMBER，该项为浮点数的小数点后位数，若不指定则系统会根据配置文件`iotdb-engine.properties`文件中的
[float_precision 项](../Appendix/Config-Manual.md) 配置。
当系统中用户输入的数据类型与该时间序列的数据类型不对应时，系统会提醒类型错误，如下所示，二阶差分编码不支持布尔类型：
@@ -53,7 +53,9 @@ IOTDB 中绝对时间戳分为二种，一种为 LONG 类型，一种为 DATETIM
在用户在输入时间戳时，可以使用 LONG 类型的时间戳或 DATETIME-INPUT 类型的时间戳，其中 DATETIME-INPUT
类型的时间戳支持格式如表所示：
-<center>**DATETIME-INPUT 类型支持格式**
+<center>
+
+**DATETIME-INPUT 类型支持格式**
| format |
@@ -76,7 +78,9 @@ IOTDB 中绝对时间戳分为二种，一种为 LONG 类型，一种为 DATETIM
IoTDB 在显示时间戳时可以支持 LONG 类型以及 DATETIME-DISPLAY 类型，其中 DATETIME-DISPLAY
类型可以支持用户自定义时间格式。自定义时间格式的语法如表所示：
-<center>**DATETIME-DISPLAY 自定义时间格式的语法**
+<center>
+
+**DATETIME-DISPLAY 自定义时间格式的语法**
| Symbol | Meaning | Presentation | Examples
|
@@ -123,7 +127,9 @@ IoTDB 在显示时间戳时可以支持 LONG 类型以及 DATETIME-DISPLAY 类
RelativeTime = (now() | DATETIME) ((+|-) Duration)+
```
- <center>**The syntax of the duration unit**
+ <center>
+
+ **The syntax of the duration unit**
| Symbol | Meaning | Presentation | Examples |
diff --git a/docs/zh/UserGuide/Data-Concept/Encoding.md
b/docs/zh/UserGuide/Data-Concept/Encoding.md
index e010821..87e7f2e 100644
--- a/docs/zh/UserGuide/Data-Concept/Encoding.md
+++ b/docs/zh/UserGuide/Data-Concept/Encoding.md
@@ -55,7 +55,9 @@ GORILLA 编码是一种无损编码，它比较适合编码前后值比较接近
前文介绍的五种编码适用于不同的数据类型，若对应关系错误，则无法正确创建时间序列。数据类型与支持其编码的编码方式对应关系总结如表格 2-3。
-<div style="text-align: center;"> **表格 2-3 数据类型与支持其编码的对应关系**
+<div style="text-align: center;">
+
+**表格 2-3 数据类型与支持其编码的对应关系**
|数据类型 |支持的编码|
|:---:|:---:|
diff --git
a/docs/zh/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
b/docs/zh/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
index 275f54c..e3bc114 100644
--- a/docs/zh/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
+++ b/docs/zh/UserGuide/IoTDB-SQL-Language/DML-Data-Manipulation-Language.md
@@ -997,7 +997,9 @@ select <path> from <prefixPath> where time = <T>
fill(<data_type>[previous, <bef
表 3-4 给出了所有参数的详细说明。
-<center>**表 3-4previous 填充参数列表**
+<center>
+
+**表 3-4previous 填充参数列表**
| 参数名称（不区分大小写） | 解释 |
| :----------------------- |
:----------------------------------------------------------- |
@@ -1053,7 +1055,9 @@ select <path> from <prefixPath> where time = <T>
fill(<data_type>[linear, <befor
表 3-5 中给出了所有参数的详细说明。
-<center>**表 3-5 线性填充参数列表**
+<center>
+
+**表 3-5 线性填充参数列表**
| 参数名称（不区分大小写） | 解释
|
| :-------------------------- |
:----------------------------------------------------------- |
@@ -1101,7 +1105,9 @@ select <path> from <prefixPath> where time = <T>
fill(<data_type>[constant]…)
表3-6中给出了所有参数的详细说明。
-<center>**表3-6特定值填充参数列表**
+<center>
+
+**表3-6特定值填充参数列表**
| 参数名称（不区分大小写） | 解释
|
| :-------------------------- |
:----------------------------------------------------------- |
@@ -1141,7 +1147,9 @@ It costs 0.007s
数据类型和支持的填充方法如表 3-6 所示。
-<center>**表 3-6 数据类型和支持的填充方法**
+<center>
+
+**表 3-6 数据类型和支持的填充方法**
| 数据类型 | 支持的填充方法 |
| :------- | :--------------------- |
diff --git a/docs/zh/UserGuide/System-Tools/Monitor-and-Log-Tools.md
b/docs/zh/UserGuide/System-Tools/Monitor-and-Log-Tools.md
index 56150dc..443b156 100644
--- a/docs/zh/UserGuide/System-Tools/Monitor-and-Log-Tools.md
+++ b/docs/zh/UserGuide/System-Tools/Monitor-and-Log-Tools.md
@@ -180,7 +180,9 @@ select last TOTAL_POINTS from root.stats."global"
配置文件位置：conf/iotdb-engine.properties
-<center>**表 -配置参数以及描述项**
+<center>
+
+**表 -配置参数以及描述项**
|参数|默认值|描述|
|:---|:---|:---|
