This is an automated email from the ASF dual-hosted git repository.
qiaojialin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-iotdb.git
The following commit(s) were added to refs/heads/master by this push:
new fcff4ee Fix latest url (#292)
fcff4ee is described below
commit fcff4eec6422e4a7ceb04e1400ec9ea9191e7b01
Author: Jialin Qiao <[email protected]>
AuthorDate: Tue Jul 23 14:56:24 2019 +0800
Fix latest url (#292)
* Fix 'latest' in documents link url to version number
---
README.md | 6 +++---
.../1-Key Concepts and Terminology.md | 2 +-
.../2-Concept Key Concepts and Terminology/2-Data Type.md | 2 +-
.../2-Concept Key Concepts and Terminology/3-Encoding.md | 4 ++--
.../4-Compression.md | 2 +-
.../UserGuide/3-Operation Manual/2-Data Model Selection.md | 10 +++++-----
.../UserGuide/3-Operation Manual/3-Data Import.md | 6 +++---
.../UserGuide/3-Operation Manual/4-Data Query.md | 14 +++++++-------
.../UserGuide/3-Operation Manual/5-Data Maintenance.md | 10 +++++-----
.../3-Operation Manual/6-Priviledge Management.md | 4 ++--
.../UserGuide/4-Deployment and Management/1-Deployment.md | 2 +-
.../4-Deployment and Management/3-System Monitor.md | 6 +++---
.../UserGuide/4-Deployment and Management/5-System log.md | 2 +-
.../4-Deployment and Management/6-Data Management.md | 8 ++++----
.../Documentation-CHN/UserGuide/7-TsFile/1-Installation.md | 2 +-
docs/Documentation-CHN/UserGuide/7-TsFile/2-Usage.md | 2 +-
.../7-TsFile/{1-Installation.md => 3-Hierarchy.md} | 2 +-
.../1-Key Concepts and Terminology.md | 2 +-
.../2-Concept Key Concepts and Terminology/2-Data Type.md | 2 +-
.../2-Concept Key Concepts and Terminology/3-Encoding.md | 4 ++--
.../4-Compression.md | 2 +-
.../UserGuide/3-Operation Manual/2-Data Model Selection.md | 10 +++++-----
.../UserGuide/3-Operation Manual/3-Data Import.md | 6 +++---
.../UserGuide/3-Operation Manual/4-Data Query.md | 12 ++++++------
.../UserGuide/3-Operation Manual/5-Data Maintenance.md | 10 +++++-----
.../3-Operation Manual/6-Priviledge Management.md | 4 ++--
.../UserGuide/4-Deployment and Management/1-Deployment.md | 2 +-
.../4-Deployment and Management/2-Configuration.md | 2 +-
.../4-Deployment and Management/3-System Monitor.md | 6 +++---
.../UserGuide/4-Deployment and Management/5-System log.md | 2 +-
.../4-Deployment and Management/6-Data Management.md | 8 ++++----
docs/Documentation/UserGuide/8-System Tools/1-Sync.md | 2 +-
.../UserGuide/8-System Tools/2-Memory Estimation Tool.md | 2 ++
33 files changed, 81 insertions(+), 79 deletions(-)
diff --git a/README.md b/README.md
index d412168..b975f08 100644
--- a/README.md
+++ b/README.md
@@ -59,7 +59,7 @@ If you want to use Hadoop or Spark to analyze IoTDB data file
(called as TsFile)
# Quick Start
-This short guide will walk you through the basic process of using IoTDB. For a
more-complete guide, please visit our website's [User
Guide](https://iotdb.apache.org/#/Documents/latest/sec1).
+This short guide will walk you through the basic process of using IoTDB. For a
more-complete guide, please visit our website's [User
Guide](https://iotdb.apache.org/#/Documents/0.8.0/sec1).
## Installation from source code
@@ -161,7 +161,7 @@ Before starting to use IoTDB, you need to config the
configuration files first.
In total, we provide users three kinds of configurations module: environment
config module (iotdb-env.bat, iotdb-env.sh), system config module
(tsfile-format.properties, iotdb-engine.properties) and log config module
(logback.xml). All of these kinds of configuration files are put in
iotdb/config folder.
-For more, you are advised to check our documentation [Chapter4: Deployment and
Management](https://iotdb.apache.org/#/Documents/latest/sec4) in detail.
+For more, you are advised to check our documentation [Chapter4: Deployment and
Management](https://iotdb.apache.org/#/Documents/0.8.0/sec4) in detail.
## Start
@@ -275,7 +275,7 @@ execute successfully.
If your session looks similar to what's above, congrats, your IoTDB is
operational!
-For more on what commands are supported by IoTDB SQL, see our documentation
[Chapter 5: IoTDB SQL
Documentation](https://iotdb.apache.org/#/Documents/latest/sec5).
+For more on what commands are supported by IoTDB SQL, see our documentation
[Chapter 5: IoTDB SQL
Documentation](https://iotdb.apache.org/#/Documents/0.8.0/sec5).
# Usage of import-csv.sh
diff --git a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/1-Key Concepts and Terminology.md
b/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and Terminology/1-Key
Concepts and Terminology.md
index 1eb060e..6ae2489 100644
--- a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/1-Key Concepts and Terminology.md
+++ b/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/1-Key Concepts and Terminology.md
@@ -168,7 +168,7 @@ IoTDB在显示时间戳时可以支持LONG类型以及DATETIME-DISPLAY类型，
* 值
-一个时间序列的值是由实际中的传感器向IoTDB发送的数值。这个值可以按照数据类型被IoTDB存储，同时用户也可以针对这个值的数据类型选择压缩方式，以及对应的编码方式。数据类型与对应编码的详细信息请参见本文[数据类型](/#/Documents/latest/chap2/sec2)与[编码方式](/#/Documents/latest/chap2/sec3)节。
+一个时间序列的值是由实际中的传感器向IoTDB发送的数值。这个值可以按照数据类型被IoTDB存储，同时用户也可以针对这个值的数据类型选择压缩方式，以及对应的编码方式。数据类型与对应编码的详细信息请参见本文[数据类型](/#/Documents/0.8.0/chap2/sec2)与[编码方式](/#/Documents/latest/chap2/sec3)节。
* 数据点
diff --git a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/2-Data Type.md b/docs/Documentation-CHN/UserGuide/2-Concept Key
Concepts and Terminology/2-Data Type.md
index edb449e..2bf7287 100644
--- a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/2-Data Type.md
+++ b/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/2-Data Type.md
@@ -32,7 +32,7 @@ IoTDB支持:
一共六种数据类型。
-其中**FLOAT**与**DOUBLE**类型的序列，如果编码方式采用[RLE](/#/Documents/latest/chap2/sec3)或[TS_2DIFF](/#/Documents/latest/chap2/sec3)可以指定MAX_POINT_NUMBER，该项为浮点数的小数点后位数，具体指定方式请参见本文[第5.1节](/#/Documents/latest/chap5/sec1)，若不指定则系统会根据配置文件tsfile-format.properties文件中的[float_precision项](/#/Documents/latest/chap4/sec2)配置。
+其中**FLOAT**与**DOUBLE**类型的序列，如果编码方式采用[RLE](/#/Documents/0.8.0/chap2/sec3)或[TS_2DIFF](/#/Documents/0.8.0/chap2/sec3)可以指定MAX_POINT_NUMBER，该项为浮点数的小数点后位数，具体指定方式请参见本文[第5.1节](/#/Documents/0.8.0/chap5/sec1)，若不指定则系统会根据配置文件tsfile-format.properties文件中的[float_precision项](/#/Documents/0.8.0/chap4/sec2)配置。
当系统中用户输入的数据类型与该时间序列的数据类型不对应时，系统会提醒类型错误，如下所示，二阶差分不支持布尔类型的编码：
diff --git a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/3-Encoding.md b/docs/Documentation-CHN/UserGuide/2-Concept Key
Concepts and Terminology/3-Encoding.md
index 8b0130e..28dca2f 100644
--- a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/3-Encoding.md
+++ b/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/3-Encoding.md
@@ -33,13 +33,13 @@ PLAIN编码，默认的编码方式，即不编码，支持多种数据类型，
二阶差分编码，比较适合编码单调递增或者递减的序列数据，不适合编码波动较大的数据。
-二阶差分编码也可用于对浮点数进行编码，但在创建时间序列的时候需指定保留小数位数（MAX_POINT_NUMBER，具体指定方式参见本文[第5.1节](/#/Documents/latest/chap5/sec1)）。比较适合存储某些浮点数值连续出现、单调调递增或者递减的序列数据，不适合存储对小数点后精度要求较高以及前后波动较大的序列数据。
+二阶差分编码也可用于对浮点数进行编码，但在创建时间序列的时候需指定保留小数位数（MAX_POINT_NUMBER，具体指定方式参见本文[第5.1节](/#/Documents/0.8.0/chap5/sec1)）。比较适合存储某些浮点数值连续出现、单调调递增或者递减的序列数据，不适合存储对小数点后精度要求较高以及前后波动较大的序列数据。
* 游程编码（RLE）
游程编码，比较适合存储某些整数值连续出现的序列，不适合编码大部分情况下前后值不一样的序列数据。
-游程编码也可用于对浮点数进行编码，，但在创建时间序列的时候需指定保留小数位数（MAX_POINT_NUMBER，具体指定方式参见本文本文[第5.1节](/#/Documents/latest/chap5/sec1)）。比较适合存储某些浮点数值连续出现的序列数据，不适合存储对小数点后精度要求较高以及前后波动较大的序列数据。
+游程编码也可用于对浮点数进行编码，，但在创建时间序列的时候需指定保留小数位数（MAX_POINT_NUMBER，具体指定方式参见本文本文[第5.1节](/#/Documents/0.8.0/chap5/sec1)）。比较适合存储某些浮点数值连续出现的序列数据，不适合存储对小数点后精度要求较高以及前后波动较大的序列数据。
* GORILLA编码（GORILLA）
diff --git a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/4-Compression.md b/docs/Documentation-CHN/UserGuide/2-Concept Key
Concepts and Terminology/4-Compression.md
index bec0531..5944831 100644
--- a/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/4-Compression.md
+++ b/docs/Documentation-CHN/UserGuide/2-Concept Key Concepts and
Terminology/4-Compression.md
@@ -25,4 +25,4 @@
当时间序列写入并按照指定的类型编码为二进制数据后，IoTDB会使用压缩技术对该数据进行压缩，进一步提升空间存储效率。虽然编码和压缩都旨在提升存储效率，但编码技术通常只适合特定的数据类型（如二阶差分编码只适合与INT32或者INT64编码，存储浮点数需要先将他们乘以10m以转换为整数），然后将它们转换为二进制流。压缩方式（SNAPPY）针对二进制流进行压缩，因此压缩方式的使用不再受数据类型的限制。
-IoTDB允许在创建一个时间序列的时候指定该列的压缩方式。现阶段IoTDB现在支持的压缩方式有两种：UNCOMPRESSOR（不压缩）和SNAPPY压缩。压缩方式的指定语法详见本文[5.1节](/#/Documents/latest/chap5/sec1)。
+IoTDB允许在创建一个时间序列的时候指定该列的压缩方式。现阶段IoTDB现在支持的压缩方式有两种：UNCOMPRESSOR（不压缩）和SNAPPY压缩。压缩方式的指定语法详见本文[5.1节](/#/Documents/0.8.0/chap5/sec1)。
diff --git a/docs/Documentation-CHN/UserGuide/3-Operation Manual/2-Data Model
Selection.md b/docs/Documentation-CHN/UserGuide/3-Operation Manual/2-Data Model
Selection.md
index 814fbb9..1b9afcd 100644
--- a/docs/Documentation-CHN/UserGuide/3-Operation Manual/2-Data Model
Selection.md
+++ b/docs/Documentation-CHN/UserGuide/3-Operation Manual/2-Data Model
Selection.md
@@ -23,11 +23,11 @@
## 数据模型选用与创建
-在向IoTDB导入数据之前，首先要根据[样例数据](/#/Documents/latest/chap3/sec1)选择合适的数据存储模型，然后使用[SET
STORAGE GROUP](/#/Documents/latest/chap5/sec1)语句和[CREATE
TIMESERIES](/#/Documents/latest/chap5/sec1)语句设置存储组，并创建时间序列。
+在向IoTDB导入数据之前，首先要根据[样例数据](/#/Documents/0.8.0/chap3/sec1)选择合适的数据存储模型，然后使用[SET
STORAGE GROUP](/#/Documents/0.8.0/chap5/sec1)语句和[CREATE
TIMESERIES](/#/Documents/0.8.0/chap5/sec1)语句设置存储组，并创建时间序列。
### 选用存储模型
-根据本文描述的[数据](/#/Documents/latest/chap3/sec1)属性层级，按照属性涵盖范围以及它们之间的从属关系，我们可将其表示为如下图3.1的属性层级组织结构，其层级关系为：集团层-电场层-设备层-传感器层。其中ROOT为根节点，传感器层的每一个节点称为叶子节点。在使用IoTDB的过程中，您可以直接将由ROOT节点到每一个叶子节点路径上的属性用“.”连接，将其作为一个IoTDB的时间序列的名称。图3.1中最左侧的路径可以生成一个名为`ROOT.ln.wf01.wt01.status`的时间序列。
+根据本文描述的[数据](/#/Documents/0.8.0/chap3/sec1)属性层级，按照属性涵盖范围以及它们之间的从属关系，我们可将其表示为如下图3.1的属性层级组织结构，其层级关系为：集团层-电场层-设备层-传感器层。其中ROOT为根节点，传感器层的每一个节点称为叶子节点。在使用IoTDB的过程中，您可以直接将由ROOT节点到每一个叶子节点路径上的属性用“.”连接，将其作为一个IoTDB的时间序列的名称。图3.1中最左侧的路径可以生成一个名为`ROOT.ln.wf01.wt01.status`的时间序列。
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577327-7aa50780-1ef4-11e9-9d75-cadabb62444e.jpg";>
@@ -55,7 +55,7 @@ Msg: org.apache.iotdb.exception.MetadataErrorException:
org.apache.iotdb.excepti
### 查看存储组
-在存储组创建后，我们可以使用[SHOW STORAGE
GROUP](/#/Documents/latest/chap5/sec1)语句来查看所有的存储组，SQL语句如下所示：
+在存储组创建后，我们可以使用[SHOW STORAGE
GROUP](/#/Documents/0.8.0/chap5/sec1)语句来查看所有的存储组，SQL语句如下所示：
```
IoTDB> show storage group
@@ -83,7 +83,7 @@ IoTDB> create timeseries root.ln.wf02.wt02.status WITH
DATATYPE=BOOLEAN, ENCODIN
error: encoding TS_2DIFF does not support BOOLEAN
```
-详细的数据类型与编码方式的对应列表请参见[编码方式](/#/Documents/latest/chap2/sec3)。
+详细的数据类型与编码方式的对应列表请参见[编码方式](/#/Documents/0.8.0/chap2/sec3)。
### 查看时间序列
@@ -109,6 +109,6 @@ IoTDB> show timeseries root.ln
0.7.0版本对用户操作的数据规模进行一些限制：
-限制1：假设运行时IoTDB分配到的JVM内存大小为p，用户自定义的每次将内存中的数据写入到磁盘时的大小（[group_size_in_byte](/#/Documents/latest/chap4/sec2)）为q。存储组的数量不能超过p/q。
+限制1：假设运行时IoTDB分配到的JVM内存大小为p，用户自定义的每次将内存中的数据写入到磁盘时的大小（[group_size_in_byte](/#/Documents/0.8.0/chap4/sec2)）为q。存储组的数量不能超过p/q。
限制2：时间序列的数量不超过运行时IoTDB分配到的JVM内存与20KB的比值。
diff --git a/docs/Documentation-CHN/UserGuide/3-Operation Manual/3-Data
Import.md b/docs/Documentation-CHN/UserGuide/3-Operation Manual/3-Data Import.md
index 89e11e2..f8cd7b8 100644
--- a/docs/Documentation-CHN/UserGuide/3-Operation Manual/3-Data Import.md
+++ b/docs/Documentation-CHN/UserGuide/3-Operation Manual/3-Data Import.md
@@ -28,12 +28,12 @@
### 实时数据接入
-IoTDB为用户提供多种插入实时数据的方式，例如在[Cli/Shell工具](/#/Tools/Cli)中直接输入插入数据的[INSERT语句](/#/Documents/latest/chap5/sec1)，或使用Java
API（标准[Java
JDBC](/#/Documents/latest/chap6/sec1)接口）单条或批量执行插入数据的[INSERT语句](/#/Documents/latest/chap5/sec1)。
+IoTDB为用户提供多种插入实时数据的方式，例如在[Cli/Shell工具](/#/Tools/Cli)中直接输入插入数据的[INSERT语句](/#/Documents/0.8.0/chap5/sec1)，或使用Java
API（标准[Java
JDBC](/#/Documents/0.8.0/chap6/sec1)接口）单条或批量执行插入数据的[INSERT语句](/#/Documents/0.8.0/chap5/sec1)。
-本节主要为您介绍实时数据接入的[INSERT语句](/#/Documents/latest/chap5/sec1)在场景中的实际使用示例，有关INSERT
SQL语句的详细语法请参见本文[INSERT语句](/#/Documents/latest/chap5/sec1)节。
+本节主要为您介绍实时数据接入的[INSERT语句](/#/Documents/0.8.0/chap5/sec1)在场景中的实际使用示例，有关INSERT
SQL语句的详细语法请参见本文[INSERT语句](/#/Documents/0.8.0/chap5/sec1)节。
#### 使用INSERT语句
-使用[INSERT语句](/#/Documents/latest/chap5/sec1)可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的[时间戳](/#/Documents/latest/chap2/sec1)和一个[数值类型](/#/Documents/latest/chap2/sec2)的传感器采集值组成。
+使用[INSERT语句](/#/Documents/0.8.0/chap5/sec1)可以向指定的已经创建的一条或多条时间序列中插入数据。对于每一条数据，均由一个时间戳类型的[时间戳](/#/Documents/0.8.0/chap2/sec1)和一个[数值类型](/#/Documents/0.8.0/chap2/sec2)的传感器采集值组成。
在本节的场景实例下，以其中的两个时间序列`root.ln.wf02.wt02.status`和`root.ln.wf02.wt02.hardware`为例
，它们的数据类型分别为BOOLEAN和TEXT。
diff --git a/docs/Documentation-CHN/UserGuide/3-Operation Manual/4-Data
Query.md b/docs/Documentation-CHN/UserGuide/3-Operation Manual/4-Data Query.md
index e65cd93..8e43ac2 100644
--- a/docs/Documentation-CHN/UserGuide/3-Operation Manual/4-Data Query.md
+++ b/docs/Documentation-CHN/UserGuide/3-Operation Manual/4-Data Query.md
@@ -24,7 +24,7 @@
## 数据查询
### 时间切片查询
-本章节主要介绍时间切片查询的相关示例，主要使用的是[IoTDB
SELECT语句](/#/Documents/latest/chap5/sec1)。同时，您也可以使用[Java
JDBC](/#/Documents/latest/chap6/sec1)标准接口来执行相关的查询语句。
+本章节主要介绍时间切片查询的相关示例，主要使用的是[IoTDB
SELECT语句](/#/Documents/0.8.0/chap5/sec1)。同时，您也可以使用[Java
JDBC](/#/Documents/0.8.0/chap6/sec1)标准接口来执行相关的查询语句。
#### 根据一个时间区间选择一列数据
@@ -35,7 +35,7 @@ select temperature from root.ln.wf01.wt01 where time <
2017-11-01T00:08:00.000
```
其含义为：
-被选择的设备为ln集团wf01子站wt01设备；被选择的时间序列为温度传感器（temperature）；该语句要求选择出该设备在“2017-11-01T00:08:00.000”（此处可以使用多种时间格式，详情可参看[2.1节](/#/Documents/latest/chap2/sec1)）时间点以前的所有温度传感器的值。
+被选择的设备为ln集团wf01子站wt01设备；被选择的时间序列为温度传感器（temperature）；该语句要求选择出该设备在“2017-11-01T00:08:00.000”（此处可以使用多种时间格式，详情可参看[2.1节](/#/Documents/0.8.0/chap2/sec1)）时间点以前的所有温度传感器的值。
该SQL语句的执行结果如下：
@@ -89,7 +89,7 @@ select wf01.wt01.status,wf02.wt02.hardware from root.ln where
(time > 2017-11-01
### 降频聚合查询
-本章节主要介绍降频聚合查询的相关示例，主要使用的是IoTDB SELECT语句的[GROUP
BY子句](/#/Documents/latest/chap5/sec1)，该子句是IoTDB中用于根据用户给定划分条件对结果集进行划分，并对已划分的结果集进行聚合计算的语句。IoTDB支持根据时间间隔对结果集进行划分，默认结果按照时间升序排列。同时，您也可以使用[Java
JDBC](/#/Documents/latest/chap6/sec1)标准接口来执行相关的查询语句。
+本章节主要介绍降频聚合查询的相关示例，主要使用的是IoTDB SELECT语句的[GROUP
BY子句](/#/Documents/0.8.0/chap5/sec1)，该子句是IoTDB中用于根据用户给定划分条件对结果集进行划分，并对已划分的结果集进行聚合计算的语句。IoTDB支持根据时间间隔对结果集进行划分，默认结果按照时间升序排列。同时，您也可以使用[Java
JDBC](/#/Documents/0.8.0/chap6/sec1)标准接口来执行相关的查询语句。
GROUP BY语句为用户提供三类指定参数：
@@ -209,7 +209,7 @@ select temperature from root.sgcc.wf03.wt01 where time =
2017-11-01T16:37:50.000
由于2017-11-01T16:37:50.000时刻，时间序列`root.sgcc.wf03.wt01.temperature`结果为空值，系统采用2017-11-01T16:37:50.000时刻的前一个时间戳（且该时间戳在[2017-11-01T16:36:50.000,
2017-11-01T16:37:50.000]时间范围内）的值进行补值并显示。
-在本文的[样例数据集](/#/Documents/latest/chap3/sec1)上，该语句的执行结果如图所示：
+在本文的[样例数据集](/#/Documents/0.8.0/chap3/sec1)上，该语句的执行结果如图所示：
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577616-67df0280-1ef5-11e9-9dff-2eb8342074eb.jpg";></center>
值得说明的是，如果在填充指定的有效时间内没有数值，则系统不会进行填充，返回为空，如图所示：
@@ -243,7 +243,7 @@ select temperature from root.sgcc.wf03.wt01 where time =
2017-11-01T16:37:50.000
由于2017-11-01T16:37:50.000时刻，时间序列`root.sgcc.wf03.wt01.temperature`结果为空值，系统采用2017-11-01T16:37:50.000时刻的前一个时间戳（且该时间戳在[2017-11-01T16:36:50.000,
2017-11-01T16:37:50.000]时间范围内）2017-11-01T16:37:00.000及其值21.927326、2017-11-01T16:37:50.000时刻的后一个时间戳（且该时间戳在[2017-11-01T16:37:50.000,
2017-11-01T16:38:50.000]时间范围内）2017-11-01T16:39:00.000及其值25.311783进行线性计算得到结果为21.927326
+ (25.311783-21.927326)/60s*50s = 24.747707。
-在本文的[样例数据集](/#/Documents/latest/chap3/sec1)上，该语句的执行结果如图所示：
+在本文的[样例数据集](/#/Documents/0.8.0/chap3/sec1)上，该语句的执行结果如图所示：
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577727-d4f29800-1ef5-11e9-8ff3-3bb519da3993.jpg";></center>
#### 数据类型与填充方法对应关系
@@ -282,11 +282,11 @@ select temperature from root.sgcc.wf03.wt01 where time =
2017-11-01T16:37:50.000
> 注意: 0.7.0版本中Fill语句内至少指定一种填充类型。
### 查询结果的分页控制
-为方便用户在对IoTDB进行查询时更好的进行结果阅读，IoTDB为用户提供了[LIMIT/SLIMIT](/#/Documents/latest/chap5/sec1)子句以及[OFFSET/SOFFSET](/#/Documents/latest/chap5/sec1)子句。使用LIMIT和SLIMIT子句可以允许用户对查询结果的行数和列数进行控制，使用OFFSET和SOFFSET子句可以允许用户设定结果展示的起始位置。
+为方便用户在对IoTDB进行查询时更好的进行结果阅读，IoTDB为用户提供了[LIMIT/SLIMIT](/#/Documents/0.8.0/chap5/sec1)子句以及[OFFSET/SOFFSET](/#/Documents/0.8.0/chap5/sec1)子句。使用LIMIT和SLIMIT子句可以允许用户对查询结果的行数和列数进行控制，使用OFFSET和SOFFSET子句可以允许用户设定结果展示的起始位置。
值得说明的是，LIMIT/SLIMIT子句以及OFFSET/SOFFSET子句均不改变查询的实际执行过程，仅对查询返回的结果进行约束。
-本章节主要介绍查询结果分页控制的相关示例。同时你也可以使用[Java
JDBC](/#/Documents/latest/chap6/sec1)标准接口来执行相关的查询语句。
+本章节主要介绍查询结果分页控制的相关示例。同时你也可以使用[Java
JDBC](/#/Documents/0.8.0/chap6/sec1)标准接口来执行相关的查询语句。
#### 查询结果的行数控制
diff --git a/docs/Documentation-CHN/UserGuide/3-Operation Manual/5-Data
Maintenance.md b/docs/Documentation-CHN/UserGuide/3-Operation Manual/5-Data
Maintenance.md
index d247860..bbb4715 100644
--- a/docs/Documentation-CHN/UserGuide/3-Operation Manual/5-Data Maintenance.md
+++ b/docs/Documentation-CHN/UserGuide/3-Operation Manual/5-Data Maintenance.md
@@ -27,9 +27,9 @@
### 数据更新
-用户使用[UPDATE语句](/#/Documents/latest/chap5/sec1)可以更新指定的时间序列中一段时间的数据。在更新数据时，用户可以选择需要更新的一个时间序列（0.7.0版本暂不支持多个时间序列的更新）并指定更新某个时间点或时间段的数据（0.7.0版本必须有时间过滤条件）。
+用户使用[UPDATE语句](/#/Documents/0.8.0/chap5/sec1)可以更新指定的时间序列中一段时间的数据。在更新数据时，用户可以选择需要更新的一个时间序列（0.8.0版本暂不支持多个时间序列的更新）并指定更新某个时间点或时间段的数据（0.8.0版本必须有时间过滤条件）。
-在JAVA编程环境中，您可以使用[JDBC API](/#/Documents/latest/chap6/sec1)单条或批量执行UPDATE语句。
+在JAVA编程环境中，您可以使用[JDBC API](/#/Documents/0.8.0/chap6/sec1)单条或批量执行UPDATE语句。
#### 单传感器时间序列值更新
@@ -54,9 +54,9 @@ Msg: do not select any existing series
### 数据删除
-用户使用[DELETE语句](/#/Documents/latest/chap5/sec1)可以删除指定的时间序列中符合时间删除条件的数据。在删除数据时，用户可以选择需要删除的一个或多个时间序列、时间序列的前缀、时间序列带*路径对某时间之前的数据进行删除（0.7.0版本暂不支持删除某一闭时间区间范围内的数据）。
+用户使用[DELETE语句](/#/Documents/0.8.0/chap5/sec1)可以删除指定的时间序列中符合时间删除条件的数据。在删除数据时，用户可以选择需要删除的一个或多个时间序列、时间序列的前缀、时间序列带*路径对某时间之前的数据进行删除（0.8.0版本暂不支持删除某一闭时间区间范围内的数据）。
-在JAVA编程环境中，您可以使用[JDBC API](/#/Documents/latest/chap6/sec1)单条或批量执行UPDATE语句。
+在JAVA编程环境中，您可以使用[JDBC API](/#/Documents/0.8.0/chap6/sec1)单条或批量执行UPDATE语句。
#### 单传感器时间序列值删除
@@ -70,7 +70,7 @@ delete from root.ln.wf02.wt02.status where
time<=2017-11-01T16:26:00;
#### 多传感器时间序列值删除
-当ln集团wf02子站的wt02设备在2017-11-01
16:26:00之前的供电状态和设备硬件版本都需要删除，此时可以使用含义更广的[前缀路径或带`*`路径](/#/Documents/latest/chap2/sec1)进行删除操作，进行此操作的SQL语句为：
+当ln集团wf02子站的wt02设备在2017-11-01
16:26:00之前的供电状态和设备硬件版本都需要删除，此时可以使用含义更广的[前缀路径或带`*`路径](/#/Documents/0.8.0/chap2/sec1)进行删除操作，进行此操作的SQL语句为：
```
delete from root.ln.wf02.wt02 where time <= 2017-11-01T16:26:00;
diff --git a/docs/Documentation-CHN/UserGuide/3-Operation Manual/6-Priviledge
Management.md b/docs/Documentation-CHN/UserGuide/3-Operation
Manual/6-Priviledge Management.md
index d2c7af5..aec185e 100644
--- a/docs/Documentation-CHN/UserGuide/3-Operation Manual/6-Priviledge
Management.md
+++ b/docs/Documentation-CHN/UserGuide/3-Operation Manual/6-Priviledge
Management.md
@@ -25,7 +25,7 @@
IoTDB为用户提供了权限管理操作，从而为用户提供对于数据的权限管理功能，保障数据的安全。
-我们将通过以下几个具体的例子为您示范基本的用户权限操作，详细的SQL语句及使用方式详情请参见本文[第5.1节](/#/Documents/latest/chap5/sec1)。同时，在JAVA编程环境中，您可以使用[JDBC
API](/#/Documents/latest/chap6/sec1)单条或批量执行权限管理类语句。
+我们将通过以下几个具体的例子为您示范基本的用户权限操作，详细的SQL语句及使用方式详情请参见本文[第5.1节](/#/Documents/0.8.0/chap5/sec1)。同时，在JAVA编程环境中，您可以使用[JDBC
API](/#/Documents/0.8.0/chap6/sec1)单条或批量执行权限管理类语句。
### 基本概念
#### 用户
@@ -46,7 +46,7 @@ IoTDB为用户提供了权限管理操作，从而为用户提供对于数据的
### 权限操作示例
-根据本文中描述的[样例数据](/#/Documents/latest/chap3/sec1)内容，IoTDB的样例数据可能同时属于ln,
sgcc等不同发电集团，不同的发电集团不希望其他发电集团获取自己的数据库数据，因此我们需要将不同的数据在集团层进行权限隔离。
+根据本文中描述的[样例数据](/#/Documents/0.8.0/chap3/sec1)内容，IoTDB的样例数据可能同时属于ln,
sgcc等不同发电集团，不同的发电集团不希望其他发电集团获取自己的数据库数据，因此我们需要将不同的数据在集团层进行权限隔离。
#### 创建用户
diff --git a/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/1-Deployment.md b/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/1-Deployment.md
index 8a17d2f..36e9f43 100644
--- a/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/1-Deployment.md
+++ b/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/1-Deployment.md
@@ -130,4 +130,4 @@ $IOTDB_HOME/
### 通过Docker安装 (Dockerfile)
-你可以通过[这份指南](/#/Documents/latest/chap4/sec7)编译并运行一个IoTDB docker image。
+你可以通过[这份指南](/#/Documents/0.8.0/chap4/sec7)编译并运行一个IoTDB docker image。
diff --git a/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/3-System Monitor.md b/docs/Documentation-CHN/UserGuide/4-Deployment
and Management/3-System Monitor.md
index f611441..10c8a45 100644
--- a/docs/Documentation-CHN/UserGuide/4-Deployment and Management/3-System
Monitor.md
+++ b/docs/Documentation-CHN/UserGuide/4-Deployment and Management/3-System
Monitor.md
@@ -33,13 +33,13 @@
本模块是IoTDB为用户提供的对其中存储数据信息的数据统计监控方式，我们会在系统中为您记录各个模块的数据统计信息，并将其汇总存入数据库中。当前0.7.0版本的IoTDB提供IoTDB写入数据的统计功能。
-用户可以选择开启或关闭数据统计监控功能（您可以设定配置文件中的`enable_stat_monitor`项，详细信息参见[第4.2节](/#/Documents/latest/chap4/sec2)）。
+用户可以选择开启或关闭数据统计监控功能（您可以设定配置文件中的`enable_stat_monitor`项，详细信息参见[第4.2节](/#/Documents/0.8.0/chap4/sec2)）。
#### 写入数据统计
-系统目前对写入数据的统计可分为两大模块： 全局（Global） 写入数据统计和存储组（Storage Group） 写入数据统计。
全局统计量记录了所有写入数据的点数、请求数统计，存储组统计量对某一个存储组的写入数据进行了统计，系统默认设定每 5 秒
（若需更改统计频率，您可以设定配置文件中的`back_loop_period_in_second`项，详细信息参见本文[4.2节](/#/Documents/latest/chap4/sec2)）
将统计量写入 IoTDB 中，并以系统指定的命名方式存储。系统刷新或者重启后， IoTDB 不对统计量做恢复处理，统计量从零值重新开始计算。
+系统目前对写入数据的统计可分为两大模块： 全局（Global） 写入数据统计和存储组（Storage Group） 写入数据统计。
全局统计量记录了所有写入数据的点数、请求数统计，存储组统计量对某一个存储组的写入数据进行了统计，系统默认设定每 5 秒
（若需更改统计频率，您可以设定配置文件中的`back_loop_period_in_second`项，详细信息参见本文[4.2节](/#/Documents/0.8.0/chap4/sec2)）
将统计量写入 IoTDB 中，并以系统指定的命名方式存储。系统刷新或者重启后， IoTDB 不对统计量做恢复处理，统计量从零值重新开始计算。
-为了避免统计信息占用过多空间，我们为统计信息加入定期清除无效数据的机制。系统将每隔一段时间删除无效数据。用户可以通过设置删除机制触发频率（`stat_monitor_retain_interval_in_second`项，默认为600s，详细信息参见本文[4.2节](/#/Documents/latest/chap4/sec2)）配置删除数据的频率，通过设置有效数据的期限（`stat_monitor_detect_freq_in_second`项，默认为600s，详细信息参见本文[4.2节](/#/Documents/latest/chap4/sec2)）设置有效数据的范围，即距离清除操作触发时间为`stat_monitor_detect_freq_in_second`以内的数据为有效数据。为了保证系统的稳定，不允许频繁地删除统计量，因此如果配置参数的时间小于默认值，系统不采用配置参数而使用默认参数。
+为了避免统计信息占用过多空间，我们为统计信息加入定期清除无效数据的机制。系统将每隔一段时间删除无效数据。用户可以通过设置删除机制触发频率（`stat_monitor_retain_interval_in_second`项，默认为600s，详细信息参见本文[4.2节](/#/Documents/0.8.0/chap4/sec2)）配置删除数据的频率，通过设置有效数据的期限（`stat_monitor_detect_freq_in_second`项，默认为600s，详细信息参见本文[4.2节](/#/Documents/0.8.0/chap4/sec2)）设置有效数据的范围，即距离清除操作触发时间为`stat_monitor_detect_freq_in_second`以内的数据为有效数据。为了保证系统的稳定，不允许频繁地删除统计量，因此如果配置参数的时间小于默认值，系统不采用配置参数而使用默认参数。
注：当前 0.7.0 版本统计的写入数据统计信息会同时统计用户写入的数据与系统内部监控数据。
diff --git a/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/5-System log.md b/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/5-System log.md
index 63e578b..1b4fd4d 100644
--- a/docs/Documentation-CHN/UserGuide/4-Deployment and Management/5-System
log.md
+++ b/docs/Documentation-CHN/UserGuide/4-Deployment and Management/5-System
log.md
@@ -25,7 +25,7 @@
IoTDB支持用户通过修改日志配置文件的方式对IoTDB系统日志（如日志输出级别等）进行配置，系统日志配置文件默认位置在$IOTDB_HOME/conf文件夹下，默认的日志配置文件名为logback.xml。用户可以通过增加或更改其中的xml树型节点参数对系统运行日志的相关配置进行修改。需要说明的是，使用日志配置文件对系统日志进行配置并非修改完文件立刻生效，而是重启IoTDB系统后生效。详细配置说明参看本文第5.4.2节日志文件配置说明。
-同时，为了方便在系统运行过程中运维人员对系统的调试，我们为系统运维人员提供了动态修改日志配置的JMX接口，能够在系统不重启的前提下实时对系统的Log模块进行配置。详细使用方法参看[动态系统日志配置说明](/#/Documents/latest/chap4/sec4)。
+同时，为了方便在系统运行过程中运维人员对系统的调试，我们为系统运维人员提供了动态修改日志配置的JMX接口，能够在系统不重启的前提下实时对系统的Log模块进行配置。详细使用方法参看[动态系统日志配置说明](/#/Documents/0.8.0/chap4/sec4)。
### 动态系统日志配置说明
diff --git a/docs/Documentation-CHN/UserGuide/4-Deployment and
Management/6-Data Management.md b/docs/Documentation-CHN/UserGuide/4-Deployment
and Management/6-Data Management.md
index 40e1bae..869da1a 100644
--- a/docs/Documentation-CHN/UserGuide/4-Deployment and Management/6-Data
Management.md
+++ b/docs/Documentation-CHN/UserGuide/4-Deployment and Management/6-Data
Management.md
@@ -30,17 +30,17 @@ IoTDB需要存储的数据分为三类，分别为数据文件、系统文件以
### 数据文件
-数据文件存储了用户写入IoTDB系统的所有数据。包含TsFile文件和其他文件，其中，TsFile文件可以通过配置项`tsfile_dir`配置存储路径（详情见[tsfile_dir配置项](/#/Documents/latest/chap4/sec2)），其他文件可通过[data_dir配置项](/#/Documents/latest/chap4/sec2)进行配置。
+数据文件存储了用户写入IoTDB系统的所有数据。包含TsFile文件和其他文件，其中，TsFile文件可以通过配置项`tsfile_dir`配置存储路径（详情见[tsfile_dir配置项](/#/Documents/0.8.0/chap4/sec2)），其他文件可通过[data_dir配置项](/#/Documents/0.8.0/chap4/sec2)进行配置。
-为了更好的支持用户对于磁盘空间扩展等存储需求，IoTDB为TsFile的存储配置增加了多文件目录的存储方式，用户可自主配置多个存储路径作为数据的持久化位置（详情见[tsfile_dir配置项](/#/Documents/latest/chap4/sec2)），并可以指定或自定义目录选择策略（详情见[mult_dir_strategy配置项](/#/Documents/latest/chap4/sec2)）。
+为了更好的支持用户对于磁盘空间扩展等存储需求，IoTDB为TsFile的存储配置增加了多文件目录的存储方式，用户可自主配置多个存储路径作为数据的持久化位置（详情见[tsfile_dir配置项](/#/Documents/0.8.0/chap4/sec2)），并可以指定或自定义目录选择策略（详情见[mult_dir_strategy配置项](/#/Documents/0.8.0/chap4/sec2)）。
### 系统文件
-系统文件包括Restore文件和Schema文件，存储了数据文件的元数据信息。可通过sys_dir配置项进行配置（详情见[sys_dir配置项](/#/Documents/latest/chap4/sec2)）。
+系统文件包括Restore文件和Schema文件，存储了数据文件的元数据信息。可通过sys_dir配置项进行配置（详情见[sys_dir配置项](/#/Documents/0.8.0/chap4/sec2)）。
### 写前日志文件
-写前日志文件存储了系统的写前日志。可通过`wal_dir`配置项进行配置（详情见[wal_dir配置项](/#/Documents/latest/chap4/sec2)）。
+写前日志文件存储了系统的写前日志。可通过`wal_dir`配置项进行配置（详情见[wal_dir配置项](/#/Documents/0.8.0/chap4/sec2)）。
### 数据存储目录设置举例
diff --git a/docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
b/docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
index eac3d37..1813bb6 100644
--- a/docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
+++ b/docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
@@ -19,6 +19,6 @@
-->
-# Chaper7: TsFile
+# Chaper 7: TsFile
Coming Soon.
\ No newline at end of file
diff --git a/docs/Documentation-CHN/UserGuide/7-TsFile/2-Usage.md
b/docs/Documentation-CHN/UserGuide/7-TsFile/2-Usage.md
index eac3d37..1813bb6 100644
--- a/docs/Documentation-CHN/UserGuide/7-TsFile/2-Usage.md
+++ b/docs/Documentation-CHN/UserGuide/7-TsFile/2-Usage.md
@@ -19,6 +19,6 @@
-->
-# Chaper7: TsFile
+# Chaper 7: TsFile
Coming Soon.
\ No newline at end of file
diff --git a/docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
b/docs/Documentation-CHN/UserGuide/7-TsFile/3-Hierarchy.md
similarity index 96%
copy from docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
copy to docs/Documentation-CHN/UserGuide/7-TsFile/3-Hierarchy.md
index eac3d37..1813bb6 100644
--- a/docs/Documentation-CHN/UserGuide/7-TsFile/1-Installation.md
+++ b/docs/Documentation-CHN/UserGuide/7-TsFile/3-Hierarchy.md
@@ -19,6 +19,6 @@
-->
-# Chaper7: TsFile
+# Chaper 7: TsFile
Coming Soon.
\ No newline at end of file
diff --git a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/1-Key Concepts and Terminology.md
b/docs/Documentation/UserGuide/2-Concept Key Concepts and Terminology/1-Key
Concepts and Terminology.md
index cbad77e..89f56df 100644
--- a/docs/Documentation/UserGuide/2-Concept Key Concepts and Terminology/1-Key
Concepts and Terminology.md
+++ b/docs/Documentation/UserGuide/2-Concept Key Concepts and Terminology/1-Key
Concepts and Terminology.md
@@ -169,7 +169,7 @@ IoTDB can support LONG types and DATETIME-DISPLAY types
when displaying timestam
* Value
-The value of a time series is actually the value sent by a sensor to IoTDB.
This value can be stored by IoTDB according to the data type. At the same time,
users can select the compression mode and the corresponding encoding mode
according to the data type of this value. See [Data
Type](/#/Documents/latest/chap2/sec2) and
[Encoding](/#/Documents/latest/chap2/sec3) of this document for details on data
type and corresponding encoding.
+The value of a time series is actually the value sent by a sensor to IoTDB.
This value can be stored by IoTDB according to the data type. At the same time,
users can select the compression mode and the corresponding encoding mode
according to the data type of this value. See [Data
Type](/#/Documents/0.8.0/chap2/sec2) and
[Encoding](/#/Documents/0.8.0/chap2/sec3) of this document for details on data
type and corresponding encoding.
* Point
diff --git a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/2-Data Type.md b/docs/Documentation/UserGuide/2-Concept Key
Concepts and Terminology/2-Data Type.md
index 4a39d76..ffd1e80 100644
--- a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/2-Data Type.md
+++ b/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/2-Data Type.md
@@ -31,7 +31,7 @@ IoTDB supports six data types in total:
* TEXT (String).
-The time series of **FLOAT** and **DOUBLE** type can specify
(MAX\_POINT\_NUMBER, see [this page](/#/Documents/latest/chap5/sec1) for more
information on how to specify), which is the number of digits after the decimal
point of the floating point number, if the encoding method is
[RLE](/#/Documents/latest/chap2/sec3) or
[TS\_2DIFF](/#/Documents/latest/chap2/sec3) (Refer to [Create Timeseries
Statement](/#/Documents/latest/chap5/sec1) for more information on how to
specify). If MAX\_POINT [...]
+The time series of **FLOAT** and **DOUBLE** type can specify
(MAX\_POINT\_NUMBER, see [this page](/#/Documents/0.8.0/chap5/sec1) for more
information on how to specify), which is the number of digits after the decimal
point of the floating point number, if the encoding method is
[RLE](/#/Documents/0.8.0/chap2/sec3) or
[TS\_2DIFF](/#/Documents/0.8.0/chap2/sec3) (Refer to [Create Timeseries
Statement](/#/Documents/0.8.0/chap5/sec1) for more information on how to
specify). If MAX\_POINT\_NU [...]
* For Float data value, The data range is (-Integer.MAX_VALUE,
Integer.MAX_VALUE), rather than Float.MAX_VALUE, and the max_point_number is
19, it is because of the limition of function Math.round(float) in Java.
* For Double data value, The data range is (-Long.MAX_VALUE, Long.MAX_VALUE),
rather than Double.MAX_VALUE, and the max_point_number is 19, it is because of
the limition of function Math.round(double) in Java (Long.MAX_VALUE=9.22E18).
diff --git a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/3-Encoding.md b/docs/Documentation/UserGuide/2-Concept Key Concepts
and Terminology/3-Encoding.md
index c9fdc3c..695d2ac 100644
--- a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/3-Encoding.md
+++ b/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/3-Encoding.md
@@ -32,13 +32,13 @@ PLAIN encoding, the default encoding mode, i.e, no
encoding, supports multiple d
Second-order differential encoding is more suitable for encoding monotonically
increasing or decreasing sequence data, and is not recommended for sequence
data with large fluctuations.
-Second-order differential encoding can also be used to encode floating-point
numbers, but it is necessary to specify reserved decimal digits
(MAX\_POINT\_NUMBER, see [this page](/#/Documents/latest/chap5/sec1) for more
information on how to specify) when creating time series. It is more suitable
for storing sequence data where floating-point values appear continuously,
monotonously increase or decrease, and it is not suitable for storing sequence
data with high precision requirements aft [...]
+Second-order differential encoding can also be used to encode floating-point
numbers, but it is necessary to specify reserved decimal digits
(MAX\_POINT\_NUMBER, see [this page](/#/Documents/0.8.0/chap5/sec1) for more
information on how to specify) when creating time series. It is more suitable
for storing sequence data where floating-point values appear continuously,
monotonously increase or decrease, and it is not suitable for storing sequence
data with high precision requirements afte [...]
* RLE
Run-length encoding is more suitable for storing sequence with continuous
integer values, and is not recommended for sequence data with most of the time
different values.
-Run-length encoding can also be used to encode floating-point numbers, but it
is necessary to specify reserved decimal digits (MAX\_POINT\_NUMBER, see [this
page](/#/Documents/latest/chap5/sec1) for more information on how to specify)
when creating time series. It is more suitable for storing sequence data where
floating-point values appear continuously, monotonously increase or decrease,
and it is not suitable for storing sequence data with high precision
requirements after the decimal [...]
+Run-length encoding can also be used to encode floating-point numbers, but it
is necessary to specify reserved decimal digits (MAX\_POINT\_NUMBER, see [this
page](/#/Documents/0.8.0/chap5/sec1) for more information on how to specify)
when creating time series. It is more suitable for storing sequence data where
floating-point values appear continuously, monotonously increase or decrease,
and it is not suitable for storing sequence data with high precision
requirements after the decimal p [...]
* GORILLA
diff --git a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/4-Compression.md b/docs/Documentation/UserGuide/2-Concept Key
Concepts and Terminology/4-Compression.md
index d66ac48..ec9e643 100644
--- a/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/4-Compression.md
+++ b/docs/Documentation/UserGuide/2-Concept Key Concepts and
Terminology/4-Compression.md
@@ -25,4 +25,4 @@
When the time series is written and encoded as binary data according to the
specified type, IoTDB compresses the data using compression technology to
further improve space storage efficiency. Although both encoding and
compression are designed to improve storage efficiency, encoding techniques are
usually only available for specific data types (e.g., second-order differential
encoding is only suitable for INT32 or INT64 data type, and storing
floating-point numbers requires multiplying t [...]
-IoTDB allows you to specify the compression method of the column when creating
a time series. IoTDB now supports two kinds of compression: UNCOMPRESSED (no
compression) and SNAPPY compression. The specified syntax for compression is
detailed in [Create Timeseries Statement](/#/Documents/latest/chap5/sec1).
\ No newline at end of file
+IoTDB allows you to specify the compression method of the column when creating
a time series. IoTDB now supports two kinds of compression: UNCOMPRESSED (no
compression) and SNAPPY compression. The specified syntax for compression is
detailed in [Create Timeseries Statement](/#/Documents/0.8.0/chap5/sec1).
\ No newline at end of file
diff --git a/docs/Documentation/UserGuide/3-Operation Manual/2-Data Model
Selection.md b/docs/Documentation/UserGuide/3-Operation Manual/2-Data Model
Selection.md
index 4545305..9681d45 100644
--- a/docs/Documentation/UserGuide/3-Operation Manual/2-Data Model Selection.md
+++ b/docs/Documentation/UserGuide/3-Operation Manual/2-Data Model Selection.md
@@ -23,10 +23,10 @@
## Data Model Selection
-Before importing data to IoTDB, we first select the appropriate data storage
model according to the [sample data](/#/Documents/latest/chap3/sec1), and then
create the storage group and timeseries using [SET STORAGE
GROUP](/#/Documents/latest/chap5/sec1) statement and [CREATE
TIMESERIES](/#/Documents/latest/chap5/sec1) statement respectively.
+Before importing data to IoTDB, we first select the appropriate data storage
model according to the [sample data](/#/Documents/0.8.0/chap3/sec1), and then
create the storage group and timeseries using [SET STORAGE
GROUP](/#/Documents/0.8.0/chap5/sec1) statement and [CREATE
TIMESERIES](/#/Documents/0.8.0/chap5/sec1) statement respectively.
### Storage Model Selection
-According to the data attribute layers described in [sample
data](/#/Documents/latest/chap3/sec1), we can express it as an attribute
hierarchy structure based on the coverage of attributes and the subordinate
relationship between them, as shown in Figure 3.1 below. Its hierarchical
relationship is: power group layer - power plant layer - device layer - sensor
layer. ROOT is the root node, and each node of sensor layer is called a leaf
node. In the process of using IoTDB, you can directly [...]
+According to the data attribute layers described in [sample
data](/#/Documents/0.8.0/chap3/sec1), we can express it as an attribute
hierarchy structure based on the coverage of attributes and the subordinate
relationship between them, as shown in Figure 3.1 below. Its hierarchical
relationship is: power group layer - power plant layer - device layer - sensor
layer. ROOT is the root node, and each node of sensor layer is called a leaf
node. In the process of using IoTDB, you can directly [...]
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577327-7aa50780-1ef4-11e9-9d75-cadabb62444e.jpg";>
@@ -52,7 +52,7 @@ Msg: org.apache.iotdb.exception.MetadataErrorException:
org.apache.iotdb.excepti
```
### Show Storage Group
-After the storage group is created, we can use the [SHOW STORAGE
GROUP](/#/Documents/latest/chap5/sec1) statement to view all the storage
groups. The SQL statement is as follows:
+After the storage group is created, we can use the [SHOW STORAGE
GROUP](/#/Documents/0.8.0/chap5/sec1) statement to view all the storage groups.
The SQL statement is as follows:
```
IoTDB> show storage group
@@ -80,7 +80,7 @@ IoTDB> create timeseries root.ln.wf02.wt02.status WITH
DATATYPE=BOOLEAN, ENCODIN
error: encoding TS_2DIFF does not support BOOLEAN
```
-Please refer to [Encoding](/#/Documents/latest/chap2/sec3) for correspondence
between data type and encoding.
+Please refer to [Encoding](/#/Documents/0.8.0/chap2/sec3) for correspondence
between data type and encoding.
### Show Timeseries
@@ -105,6 +105,6 @@ It is worth noting that when the queried path does not
exist, the system will re
Version 0.7.0 imposes some limitations on the scale of data that users can
operate:
-Limit 1: Assuming that the JVM memory allocated to IoTDB at runtime is p and
the user-defined size of data in memory written to disk
([group\_size\_in\_byte](/#/Documents/latest/chap4/sec2)) is Q, then the number
of storage groups should not exceed p/q.
+Limit 1: Assuming that the JVM memory allocated to IoTDB at runtime is p and
the user-defined size of data in memory written to disk
([group\_size\_in\_byte](/#/Documents/0.8.0/chap4/sec2)) is Q, then the number
of storage groups should not exceed p/q.
Limit 2: The number of timeseries should not exceed the ratio of JVM memory
allocated to IoTDB at run time to 20KB.
diff --git a/docs/Documentation/UserGuide/3-Operation Manual/3-Data Import.md
b/docs/Documentation/UserGuide/3-Operation Manual/3-Data Import.md
index 8c942b9..7874016 100644
--- a/docs/Documentation/UserGuide/3-Operation Manual/3-Data Import.md
+++ b/docs/Documentation/UserGuide/3-Operation Manual/3-Data Import.md
@@ -28,12 +28,12 @@ This feature is not supported in version 0.7.0.
### Import Real-time Data
-IoTDB provides users with a variety of ways to insert real-time data, such as
directly inputting [INSERT SQL statement](/#/Documents/latest/chap5/sec1) in
[Cli/Shell tools](/#/Tools/Cli), or using [Java
JDBC](/#/Documents/latest/chap6/sec1) to perform single or batch execution of
[INSERT SQL statement](/#/Documents/latest/chap5/sec1).
+IoTDB provides users with a variety of ways to insert real-time data, such as
directly inputting [INSERT SQL statement](/#/Documents/0.8.0/chap5/sec1) in
[Cli/Shell tools](/#/Tools/Cli), or using [Java
JDBC](/#/Documents/0.8.0/chap6/sec1) to perform single or batch execution of
[INSERT SQL statement](/#/Documents/0.8.0/chap5/sec1).
-This section mainly introduces the use of [INSERT SQL
statement](/#/Documents/latest/chap5/sec1) for real-time data import in the
scenario. See Section 5.1 for a detailed syntax of [INSERT SQL
statement](/#/Documents/latest/chap5/sec1).
+This section mainly introduces the use of [INSERT SQL
statement](/#/Documents/0.8.0/chap5/sec1) for real-time data import in the
scenario. See Section 5.1 for a detailed syntax of [INSERT SQL
statement](/#/Documents/0.8.0/chap5/sec1).
#### Use of INSERT Statements
-The [INSERT SQL statement](/#/Documents/latest/chap5/sec1) statement can be
used to insert data into one or more specified timeseries that have been
created. For each point of data inserted, it consists of a
[timestamp](/#/Documents/latest/chap2/sec1) and a sensor acquisition value of a
numerical type (see [Data Type](/#/Documents/latest/chap2/sec2)).
+The [INSERT SQL statement](/#/Documents/0.8.0/chap5/sec1) statement can be
used to insert data into one or more specified timeseries that have been
created. For each point of data inserted, it consists of a
[timestamp](/#/Documents/0.8.0/chap2/sec1) and a sensor acquisition value of a
numerical type (see [Data Type](/#/Documents/0.8.0/chap2/sec2)).
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.
diff --git a/docs/Documentation/UserGuide/3-Operation Manual/4-Data Query.md
b/docs/Documentation/UserGuide/3-Operation Manual/4-Data Query.md
index 8a6dbf8..0f96feb 100644
--- a/docs/Documentation/UserGuide/3-Operation Manual/4-Data Query.md
+++ b/docs/Documentation/UserGuide/3-Operation Manual/4-Data Query.md
@@ -24,7 +24,7 @@
## Data Query
### Time Slice Query
-This chapter mainly introduces the relevant examples of time slice query using
IoTDB SELECT statements. Detailed SQL syntax and usage specifications can be
found in [SQL Documentation](/#/Documents/latest/chap5/sec1). You can also use
the [Java JDBC](/#/Documents/latest/chap6/sec1) standard interface to execute
related queries.
+This chapter mainly introduces the relevant examples of time slice query using
IoTDB SELECT statements. Detailed SQL syntax and usage specifications can be
found in [SQL Documentation](/#/Documents/0.8.0/chap5/sec1). You can also use
the [Java JDBC](/#/Documents/0.8.0/chap6/sec1) standard interface to execute
related queries.
#### Select a Column of Data Based on a Time Interval
@@ -83,7 +83,7 @@ The execution result of this SQL statement is as follows:
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577450-dcfe0800-1ef4-11e9-9399-4ba2b2b7fb73.jpg";></center>
### Down-Frequency Aggregate Query
-This section mainly introduces the related examples of down-frequency
aggregation query, using the [GROUP BY clause](/#/Documents/latest/chap5/sec1),
which is used to partition the result set according to the user's given
partitioning conditions and aggregate the partitioned result set. IoTDB
supports partitioning result sets according to time intervals, and by default
results are sorted by time in ascending order. You can also use the [Java
JDBC](/#/Documents/latest/chap6/sec1) standard [...]
+This section mainly introduces the related examples of down-frequency
aggregation query, using the [GROUP BY clause](/#/Documents/0.8.0/chap5/sec1),
which is used to partition the result set according to the user's given
partitioning conditions and aggregate the partitioned result set. IoTDB
supports partitioning result sets according to time intervals, and by default
results are sorted by time in ascending order. You can also use the [Java
JDBC](/#/Documents/0.8.0/chap6/sec1) standard i [...]
The GROUP BY statement provides users with three types of specified parameters:
@@ -199,7 +199,7 @@ which means:
Because the timeseries root.sgcc.wf03.wt01.temperature is null at
2017-11-01T16:37:50.000, the system uses the previous timestamp of
2017-11-01T16:37:50.000 (and the timestamp is in the [2017-11-01T16:36:50.000,
2017-11-01T16:37:50.000] time range) for fill and display.
-On the [sample data](/#/Documents/latest/chap3/sec1), the execution result of
this statement is shown below:
+On the [sample data](/#/Documents/0.8.0/chap3/sec1), the execution result of
this statement is shown below:
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577616-67df0280-1ef5-11e9-9dff-2eb8342074eb.jpg";></center>
It is worth noting that if there is no value in the specified valid time
range, the system will not fill the null value, as shown below:
@@ -233,7 +233,7 @@ which means:
Because the timeseries root.sgcc.wf03.wt01.temperature is null at
2017-11-01T16:37:50.000, the system uses the previous timestamp
2017-11-01T16:37:00.000 (and the timestamp is in the [2017-11-01T16:36:50.000,
2017-11-01T16:37:50.000] time range) and its value 21.927326, the next
timestamp 2017-11-01T16:39:00.000 (and the timestamp is in the
[2017-11-01T16:36:50.000, 2017-11-01T16:37:50.000] time range) and its value
25.311783 to perform linear fitting calculation: 21.927326 + (25.311783- [...]
-On the [sample data](/#/Documents/latest/chap3/sec1), the execution result of
this statement is shown below:
+On the [sample data](/#/Documents/0.8.0/chap3/sec1), the execution result of
this statement is shown below:
<center><img style="width:100%; max-width:800px; max-height:600px;
margin-left:auto; margin-right:auto; display:block;"
src="https://user-images.githubusercontent.com/13203019/51577727-d4f29800-1ef5-11e9-8ff3-3bb519da3993.jpg";></center>
#### Correspondence between Data Type and Fill Method
@@ -273,9 +273,9 @@ When the fill method is not specified, each data type bears
its own default fill
### Row and Column Control over Query Results
-IoTDB provides [LIMIT/SLIMIT](/#/Documents/latest/chap5/sec1) clause and
[OFFSET/SOFFSET](/#/Documents/latest/chap5/sec1) clause in order to make users
have more control over query results. The use of LIMIT and SLIMIT clauses
allows users to control the number of rows and columns of query results, and
the use of OFFSET and SOFSET clauses allows users to set the starting position
of the results for display.
+IoTDB provides [LIMIT/SLIMIT](/#/Documents/0.8.0/chap5/sec1) clause and
[OFFSET/SOFFSET](/#/Documents/0.8.0/chap5/sec1) clause in order to make users
have more control over query results. The use of LIMIT and SLIMIT clauses
allows users to control the number of rows and columns of query results, and
the use of OFFSET and SOFSET clauses allows users to set the starting position
of the results for display.
-This chapter mainly introduces related examples of row and column control of
query results. You can also use the [Java JDBC](/#/Documents/latest/chap6/sec1)
standard interface to execute queries.
+This chapter mainly introduces related examples of row and column control of
query results. You can also use the [Java JDBC](/#/Documents/0.8.0/chap6/sec1)
standard interface to execute queries.
#### Row Control over Query Results
By using LIMIT and OFFSET clauses, users can control the query results in a
row-related manner. We will demonstrate how to use LIMIT and OFFSET clauses
through the following examples.
diff --git a/docs/Documentation/UserGuide/3-Operation Manual/5-Data
Maintenance.md b/docs/Documentation/UserGuide/3-Operation Manual/5-Data
Maintenance.md
index 669868f..8496aad 100644
--- a/docs/Documentation/UserGuide/3-Operation Manual/5-Data Maintenance.md
+++ b/docs/Documentation/UserGuide/3-Operation Manual/5-Data Maintenance.md
@@ -26,9 +26,9 @@
<!-- >
### Data Update
-Users can use [UPDATE statements](/#/Documents/latest/chap5/sec1) to update
data over a period of time in a specified timeseries. When updating data, users
can select a timeseries to be updated (version 0.7.0 does not support multiple
timeseries updates) and specify a time point or period to be updated (version
0.7.0 must have time filtering conditions).
+Users can use [UPDATE statements](/#/Documents/0.8.0/chap5/sec1) to update
data over a period of time in a specified timeseries. When updating data, users
can select a timeseries to be updated (version 0.8.0 does not support multiple
timeseries updates) and specify a time point or period to be updated (version
0.8.0 must have time filtering conditions).
-In a JAVA programming environment, you can use the [Java
JDBC](/#/Documents/latest/chap6/sec1) to execute single or batch UPDATE
statements.
+In a JAVA programming environment, you can use the [Java
JDBC](/#/Documents/0.8.0/chap6/sec1) to execute single or batch UPDATE
statements.
#### Update Single Timeseries
Taking the power supply status of ln group wf02 plant wt02 device as an
example, there exists such a usage scenario:
@@ -54,9 +54,9 @@ Msg: do not select any existing series
### Data Deletion
-Users can delete data that meet the deletion condition in the specified
timeseries by using the [DELETE statement](/#/Documents/latest/chap5/sec1).
When deleting data, users can select one or more timeseries paths, prefix
paths, or paths with star to delete data before a certain time (version 0.7.0
does not support the deletion of data within a closed time interval).
+Users can delete data that meet the deletion condition in the specified
timeseries by using the [DELETE statement](/#/Documents/0.8.0/chap5/sec1). When
deleting data, users can select one or more timeseries paths, prefix paths, or
paths with star to delete data before a certain time (version 0.8.0 does not
support the deletion of data within a closed time interval).
-In a JAVA programming environment, you can use the [Java
JDBC](/#/Documents/latest/chap6/sec1) to execute single or batch UPDATE
statements.
+In a JAVA programming environment, you can use the [Java
JDBC](/#/Documents/0.8.0/chap6/sec1) to execute single or batch UPDATE
statements.
#### Delete Single Timeseries
Taking ln Group as an example, there exists such a usage scenario:
@@ -68,7 +68,7 @@ delete from root.ln.wf02.wt02.status where
time<=2017-11-01T16:26:00;
```
#### Delete Multiple Timeseries
-When both the power supply status and hardware version of the ln group wf02
plant wt02 device before 2017-11-01 16:26:00 need to be deleted, [the prefix
path with broader meaning or the path with
star](/#/Documents/latest/chap2/sec1) can be used to delete the data. The SQL
statement for this operation is:
+When both the power supply status and hardware version of the ln group wf02
plant wt02 device before 2017-11-01 16:26:00 need to be deleted, [the prefix
path with broader meaning or the path with star](/#/Documents/0.8.0/chap2/sec1)
can be used to delete the data. The SQL statement for this operation is:
```
delete from root.ln.wf02.wt02 where time <= 2017-11-01T16:26:00;
diff --git a/docs/Documentation/UserGuide/3-Operation Manual/6-Priviledge
Management.md b/docs/Documentation/UserGuide/3-Operation Manual/6-Priviledge
Management.md
index 2004436..38b21d4 100644
--- a/docs/Documentation/UserGuide/3-Operation Manual/6-Priviledge
Management.md
+++ b/docs/Documentation/UserGuide/3-Operation Manual/6-Priviledge
Management.md
@@ -24,7 +24,7 @@
## Priviledge Management
IoTDB provides users with priviledge management operations, so as to ensure
data security.
-We will show you basic user priviledge management operations through the
following specific examples. Detailed SQL syntax and usage details can be found
in [Chapter 5: SQL Documentation](/#/Documents/latest/chap5/sec1). At the same
time, in the JAVA programming environment, you can use the [Java
JDBC](/#/Documents/latest/chap6/sec1) to execute priviledge management
statements in a single or batch mode.
+We will show you basic user priviledge management operations through the
following specific examples. Detailed SQL syntax and usage details can be found
in [Chapter 5: SQL Documentation](/#/Documents/0.8.0/chap5/sec1). At the same
time, in the JAVA programming environment, you can use the [Java
JDBC](/#/Documents/0.8.0/chap6/sec1) to execute priviledge management
statements in a single or batch mode.
### Basic Concepts
#### User
@@ -40,7 +40,7 @@ A role is a set of priviledges and has a unique role name as
an identifier. A us
There is a default user in IoTDB after the initial installation: root, and the
default password is root. This user is an administrator user, who cannot be
deleted and has all the priviledges. Neither can new priviledges be granted to
the root user nor can priviledges owned by the root user be deleted.
### Priviledge Management Operation Examples
-According to the [sample data](/#/Documents/latest/chap3/sec1), the sample
data of IoTDB may belong to different power generation groups such as ln, sgcc,
etc. Different power generation groups do not want others to obtain their own
database data, so we need to have data priviledge isolated at the group layer.
+According to the [sample data](/#/Documents/0.8.0/chap3/sec1), the sample data
of IoTDB may belong to different power generation groups such as ln, sgcc, etc.
Different power generation groups do not want others to obtain their own
database data, so we need to have data priviledge isolated at the group layer.
#### Create User
diff --git a/docs/Documentation/UserGuide/4-Deployment and
Management/1-Deployment.md b/docs/Documentation/UserGuide/4-Deployment and
Management/1-Deployment.md
index 15d73c2..336f0c6 100644
--- a/docs/Documentation/UserGuide/4-Deployment and Management/1-Deployment.md
+++ b/docs/Documentation/UserGuide/4-Deployment and Management/1-Deployment.md
@@ -166,4 +166,4 @@ $IOTDB_HOME/
### Installation by Docker (Dockerfile)
-You can build and run a IoTDB docker image by following the guide of
[Deployment by Docker](/#/Documents/latest/chap4/sec7)
+You can build and run a IoTDB docker image by following the guide of
[Deployment by Docker](/#/Documents/0.8.0/chap4/sec7)
diff --git a/docs/Documentation/UserGuide/4-Deployment and
Management/2-Configuration.md b/docs/Documentation/UserGuide/4-Deployment and
Management/2-Configuration.md
index ad9e9e7..031c4d1 100644
--- a/docs/Documentation/UserGuide/4-Deployment and
Management/2-Configuration.md
+++ b/docs/Documentation/UserGuide/4-Deployment and
Management/2-Configuration.md
@@ -206,7 +206,7 @@ The detail of each variables are as follows:
|Name| data\_dirs |
|:---:|:---|
-|Description| The directories of data files. Multiple directories are
separated by comma. See the
[multi\_dir\_strategy](/#/Documents/latest/chap4/sec2) configuration item for
data distribution strategy. The starting directory of the relative path is
related to the operating system. It is recommended to use an absolute path. If
the path does not exist, the system will automatically create it.|
+|Description| The directories of data files. Multiple directories are
separated by comma. See the
[multi\_dir\_strategy](/#/Documents/0.8.0/chap4/sec2) configuration item for
data distribution strategy. The starting directory of the relative path is
related to the operating system. It is recommended to use an absolute path. If
the path does not exist, the system will automatically create it.|
|Type|String[]|
|Default| data/data |
|Effective|After restart system|
diff --git a/docs/Documentation/UserGuide/4-Deployment and Management/3-System
Monitor.md b/docs/Documentation/UserGuide/4-Deployment and Management/3-System
Monitor.md
index b6077b7..f28cad7 100644
--- a/docs/Documentation/UserGuide/4-Deployment and Management/3-System
Monitor.md
+++ b/docs/Documentation/UserGuide/4-Deployment and Management/3-System
Monitor.md
@@ -150,15 +150,15 @@ There are several attributes under Monitor, including the
numbers of files opene
This module is the statistical monitoring method provided by IoTDB for users
to store data information. We will record the statistical data in the system
and store it in the database. The current 0.7.0 version of IoTDB provides
statistics for writing data.
-The user can choose to enable or disable the data statistics monitoring
function (set the `enable_stat_monitor` item in the configuration file, see
[Engine Layer](/#/Documents/latest/chap4/sec2) for details).
+The user can choose to enable or disable the data statistics monitoring
function (set the `enable_stat_monitor` item in the configuration file, see
[Engine Layer](/#/Documents/0.8.0/chap4/sec2) for details).
#### Writing Data Monitor
The current statistics of writing data by the system can be divided into two
major modules: **Global Writing Data Statistics** and **Storage Group Writing
Data Statistics**. **Global Writing Data Statistics** records the point number
written by the user and the number of requests. **Storage Group Writing Data
Statistics** records data of a certain storage group.
-The system defaults to collect data every 5 seconds, and writes the statistics
to the IoTDB and stores them in a system-specified locate. (If you need to
change the statistic frequency, you can set The `back_loop_period_in_second
entry` in the configuration file, see Section [Engine
Layer](/#/Documents/latest/chap4/sec2) for details). After the system is
refreshed or restarted, IoTDB does not recover the statistics, and the
statistics data will restart from zero.
+The system defaults to collect data every 5 seconds, and writes the statistics
to the IoTDB and stores them in a system-specified locate. (If you need to
change the statistic frequency, you can set The `back_loop_period_in_second
entry` in the configuration file, see Section [Engine
Layer](/#/Documents/0.8.0/chap4/sec2) for details). After the system is
refreshed or restarted, IoTDB does not recover the statistics, and the
statistics data will restart from zero.
-In order to avoid the excessive use of statistical information, we add a
mechanism to periodically clear invalid data for statistical information. The
system will delete invalid data at regular intervals. The user can set the
trigger frequency (`stat_monitor_retain_interval_in_second`, default is 600s,
see section [Engine Layer](/#/Documents/latest/chap4/sec2) for details) to set
the frequency of deleting data. By setting the valid data duration
(`stat_monitor_detect_freq_in_second entry [...]
+In order to avoid the excessive use of statistical information, we add a
mechanism to periodically clear invalid data for statistical information. The
system will delete invalid data at regular intervals. The user can set the
trigger frequency (`stat_monitor_retain_interval_in_second`, default is 600s,
see section [Engine Layer](/#/Documents/0.8.0/chap4/sec2) for details) to set
the frequency of deleting data. By setting the valid data duration
(`stat_monitor_detect_freq_in_second entry` [...]
It's convenient for you to use `select` clause to get the writing data
statistics the same as other timeseires.
diff --git a/docs/Documentation/UserGuide/4-Deployment and Management/5-System
log.md b/docs/Documentation/UserGuide/4-Deployment and Management/5-System
log.md
index 4e9fe42..6cb30fd 100644
--- a/docs/Documentation/UserGuide/4-Deployment and Management/5-System log.md
+++ b/docs/Documentation/UserGuide/4-Deployment and Management/5-System log.md
@@ -27,7 +27,7 @@ IoTDB allows users to configure IoTDB system logs (such as
log output level) by
The default log configuration file is named logback.xml. The user can modify
the configuration of the system running log by adding or changing the xml tree
node parameters. It should be noted that the configuration of the system log
using the log configuration file does not take effect immediately after the
modification, instead, it will take effect after restarting the system. The
usage of logback.xml is just as usual.
-At the same time, in order to facilitate the debugging of the system by the
developers and DBAs, we provide several JMX interface to dynamically modify the
log configuration, and configure the Log module of the system in real time
without restarting the system. For detailed usage, see [Dynamic System Log
Configuration](/#/Documents/latest/chap4/sec4) section.
+At the same time, in order to facilitate the debugging of the system by the
developers and DBAs, we provide several JMX interface to dynamically modify the
log configuration, and configure the Log module of the system in real time
without restarting the system. For detailed usage, see [Dynamic System Log
Configuration](/#/Documents/0.8.0/chap4/sec4) section.
### Dynamic System Log Configuration
diff --git a/docs/Documentation/UserGuide/4-Deployment and Management/6-Data
Management.md b/docs/Documentation/UserGuide/4-Deployment and Management/6-Data
Management.md
index 61354c2..3fa66ec 100644
--- a/docs/Documentation/UserGuide/4-Deployment and Management/6-Data
Management.md
+++ b/docs/Documentation/UserGuide/4-Deployment and Management/6-Data
Management.md
@@ -30,17 +30,17 @@ The data that IoTDB stores is divided into three
categories, namely data files,
### Data Files
-Data files store all the data that the user wrote to IoTDB, which contains
TsFile and other files. TsFile storage directory can be configured with the
`tsfile_dir` configuration item (see [file
layer](/#/Documents/latest/chap4/sec2) for details). Other files can be
configured through [data_dir](/#/Documents/latest/chap4/sec2) configuration
item (see [Engine Layer](/#/Documents/latest/chap4/sec2) for details).
+Data files store all the data that the user wrote to IoTDB, which contains
TsFile and other files. TsFile storage directory can be configured with the
`tsfile_dir` configuration item (see [file
layer](/#/Documents/0.8.0/chap4/sec2) for details). Other files can be
configured through [data_dir](/#/Documents/0.8.0/chap4/sec2) configuration item
(see [Engine Layer](/#/Documents/0.8.0/chap4/sec2) for details).
-In order to better support users' storage requirements such as disk space
expansion, IoTDB supports multiple file directorys storage methods for TsFile
storage configuration. Users can set multiple storage paths as data storage
locations( see [tsfile_dir](/#/Documents/latest/chap4/sec2) configuration
item), and you can specify or customize the directory selection policy (see
[mult_dir_strategy](/#/Documents/latest/chap4/sec2) configuration item for
details).
+In order to better support users' storage requirements such as disk space
expansion, IoTDB supports multiple file directorys storage methods for TsFile
storage configuration. Users can set multiple storage paths as data storage
locations( see [tsfile_dir](/#/Documents/0.8.0/chap4/sec2) configuration item),
and you can specify or customize the directory selection policy (see
[mult_dir_strategy](/#/Documents/0.8.0/chap4/sec2) configuration item for
details).
### System Files
-System files include restore files and schema files, which store metadata
information of data in IoTDB. It can be configured through the `sys_dir`
configuration item (see [System Layer](/#/Documents/latest/chap4/sec2) for
details).
+System files include restore files and schema files, which store metadata
information of data in IoTDB. It can be configured through the `sys_dir`
configuration item (see [System Layer](/#/Documents/0.8.0/chap4/sec2) for
details).
### Pre-write Log Files
-Pre-write log files store WAL files. It can be configured through the
`wal_dir` configuration item (see [System
Layer](/#/Documents/latest/chap4/sec2) for details).
+Pre-write log files store WAL files. It can be configured through the
`wal_dir` configuration item (see [System Layer](/#/Documents/0.8.0/chap4/sec2)
for details).
### Example of Setting Data storage Directory
diff --git a/docs/Documentation/UserGuide/8-System Tools/1-Sync.md
b/docs/Documentation/UserGuide/8-System Tools/1-Sync.md
index 01a4d88..8cfa849 100644
--- a/docs/Documentation/UserGuide/8-System Tools/1-Sync.md
+++ b/docs/Documentation/UserGuide/8-System Tools/1-Sync.md
@@ -19,7 +19,7 @@
-->
-# Chapter 7: System Tools
+# Chapter 8: System Tools
## Data Import
diff --git a/docs/Documentation/UserGuide/8-System Tools/2-Memory Estimation
Tool.md b/docs/Documentation/UserGuide/8-System Tools/2-Memory Estimation
Tool.md
index 9b9a1ce..3c40ef2 100644
--- a/docs/Documentation/UserGuide/8-System Tools/2-Memory Estimation Tool.md
+++ b/docs/Documentation/UserGuide/8-System Tools/2-Memory Estimation Tool.md
@@ -19,6 +19,8 @@
-->
+# Chapter 8: System Tools
+
# Memory Estimation Tool
# Introduction
![https://user-images.githubusercontent.com/13203019/51577327-7aa50780-1ef4-11e9-9d75-cadabb62444e.jpg"](https://user-images.githubusercontent.com/13203019/51577327-7aa50780-1ef4-11e9-9d75-cadabb62444e.jpg"){kind=link}
![https://user-images.githubusercontent.com/13203019/51577616-67df0280-1ef5-11e9-9dff-2eb8342074eb.jpg"](https://user-images.githubusercontent.com/13203019/51577616-67df0280-1ef5-11e9-9dff-2eb8342074eb.jpg"){kind=link}
![https://user-images.githubusercontent.com/13203019/51577727-d4f29800-1ef5-11e9-8ff3-3bb519da3993.jpg"](https://user-images.githubusercontent.com/13203019/51577727-d4f29800-1ef5-11e9-8ff3-3bb519da3993.jpg"){kind=link}
![https://user-images.githubusercontent.com/13203019/51577450-dcfe0800-1ef4-11e9-9399-4ba2b2b7fb73.jpg"](https://user-images.githubusercontent.com/13203019/51577450-dcfe0800-1ef4-11e9-9399-4ba2b2b7fb73.jpg"){kind=link}