You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iotdb.apache.org by qi...@apache.org on 2021/09/07 12:21:56 UTC
[iotdb] branch master updated: Modify user manual about
datatime-input (#3901)
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/iotdb.git
The following commit(s) were added to refs/heads/master by this push:
new aaa96b9 Modify user manual about datatime-input (#3901)
aaa96b9 is described below
commit aaa96b974becf7cc57ef5ac36c3fa9e199423010
Author: 肖志红 <73...@users.noreply.github.com>
AuthorDate: Tue Sep 7 20:21:30 2021 +0800
Modify user manual about datatime-input (#3901)
---
docs/UserGuide/Data-Concept/Data-Type.md | 14 +-------------
docs/UserGuide/Data-Concept/Encoding.md | 2 +-
docs/zh/UserGuide/Data-Concept/Data-Type.md | 14 +-------------
docs/zh/UserGuide/Data-Concept/Encoding.md | 4 ++--
4 files changed, 5 insertions(+), 29 deletions(-)
diff --git a/docs/UserGuide/Data-Concept/Data-Type.md b/docs/UserGuide/Data-Concept/Data-Type.md
index 2490769..6406f2c 100644
--- a/docs/UserGuide/Data-Concept/Data-Type.md
+++ b/docs/UserGuide/Data-Concept/Data-Type.md
@@ -62,27 +62,15 @@ Absolute timestamps in IoTDB are divided into two types: LONG and DATETIME (incl
| yyyy-MM-dd HH:mm:ss |
| yyyy/MM/dd HH:mm:ss |
| yyyy.MM.dd HH:mm:ss |
-| yyyy-MM-dd'T'HH:mm:ss |
-| yyyy/MM/dd'T'HH:mm:ss |
-| yyyy.MM.dd'T'HH:mm:ss |
| yyyy-MM-dd HH:mm:ssZZ |
| yyyy/MM/dd HH:mm:ssZZ |
| yyyy.MM.dd HH:mm:ssZZ |
-| yyyy-MM-dd'T'HH:mm:ssZZ |
-| yyyy/MM/dd'T'HH:mm:ssZZ |
-| yyyy.MM.dd'T'HH:mm:ssZZ |
| yyyy/MM/dd HH:mm:ss.SSS |
| yyyy-MM-dd HH:mm:ss.SSS |
| yyyy.MM.dd HH:mm:ss.SSS |
-| yyyy/MM/dd'T'HH:mm:ss.SSS |
-| yyyy-MM-dd'T'HH:mm:ss.SSS |
-| yyyy.MM.dd'T'HH:mm:ss.SSS |
| yyyy-MM-dd HH:mm:ss.SSSZZ |
| yyyy/MM/dd HH:mm:ss.SSSZZ |
| yyyy.MM.dd HH:mm:ss.SSSZZ |
-| yyyy-MM-dd'T'HH:mm:ss.SSSZZ |
-| yyyy/MM/dd'T'HH:mm:ss.SSSZZ |
-| yyyy.MM.dd'T'HH:mm:ss.SSSZZ |
| ISO8601 standard time format |
</center>
@@ -166,4 +154,4 @@ Relative time refers to the time relative to the server time ```now()``` and ```
now() - 1w //1 week earlier than the current server time
```
- > Note：There must be spaces on the left and right of '+' and '-'.
\ No newline at end of file
+ > Note：There must be spaces on the left and right of '+' and '-'.
diff --git a/docs/UserGuide/Data-Concept/Encoding.md b/docs/UserGuide/Data-Concept/Encoding.md
index a87fbdc..61dd4ec 100644
--- a/docs/UserGuide/Data-Concept/Encoding.md
+++ b/docs/UserGuide/Data-Concept/Encoding.md
@@ -33,7 +33,7 @@ Second-order differential encoding is more suitable for encoding monotonically i
* RLE
-Run-length encoding is 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 is suitable for storing sequence with continuous 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, while it is necessary to specify reserved decimal digits (MAX\_POINT\_NUMBER) when creating time series. It is more suitable to store sequence data where floating-point values appear continuously, monotonously increasing or decreasing, and it is not suitable for storing sequence data with high precision requirements after the decimal point or with large fluctuations.
diff --git a/docs/zh/UserGuide/Data-Concept/Data-Type.md b/docs/zh/UserGuide/Data-Concept/Data-Type.md
index edf277d..3fde98d 100644
--- a/docs/zh/UserGuide/Data-Concept/Data-Type.md
+++ b/docs/zh/UserGuide/Data-Concept/Data-Type.md
@@ -61,27 +61,15 @@ IOTDB 中绝对时间戳分为二种，一种为 LONG 类型，一种为 DATETIM
| yyyy-MM-dd HH:mm:ss |
| yyyy/MM/dd HH:mm:ss |
| yyyy.MM.dd HH:mm:ss |
-| yyyy-MM-dd'T'HH:mm:ss |
-| yyyy/MM/dd'T'HH:mm:ss |
-| yyyy.MM.dd'T'HH:mm:ss |
| yyyy-MM-dd HH:mm:ssZZ |
| yyyy/MM/dd HH:mm:ssZZ |
| yyyy.MM.dd HH:mm:ssZZ |
-| yyyy-MM-dd'T'HH:mm:ssZZ |
-| yyyy/MM/dd'T'HH:mm:ssZZ |
-| yyyy.MM.dd'T'HH:mm:ssZZ |
| yyyy/MM/dd HH:mm:ss.SSS |
| yyyy-MM-dd HH:mm:ss.SSS |
| yyyy.MM.dd HH:mm:ss.SSS |
-| yyyy/MM/dd'T'HH:mm:ss.SSS |
-| yyyy-MM-dd'T'HH:mm:ss.SSS |
-| yyyy.MM.dd'T'HH:mm:ss.SSS |
| yyyy-MM-dd HH:mm:ss.SSSZZ |
| yyyy/MM/dd HH:mm:ss.SSSZZ |
| yyyy.MM.dd HH:mm:ss.SSSZZ |
-| yyyy-MM-dd'T'HH:mm:ss.SSSZZ |
-| yyyy/MM/dd'T'HH:mm:ss.SSSZZ |
-| yyyy.MM.dd'T'HH:mm:ss.SSSZZ |
| ISO8601 standard time format |
</center>
@@ -162,4 +150,4 @@ IoTDB 在显示时间戳时可以支持 LONG 类型以及 DATETIME-DISPLAY 类
now() - 1w //比服务器时间早 1 周的时间
```
- > 注意：'+'和'-'的左右两边必须有空格
\ No newline at end of file
+ > 注意：'+'和'-'的左右两边必须有空格
diff --git a/docs/zh/UserGuide/Data-Concept/Encoding.md b/docs/zh/UserGuide/Data-Concept/Encoding.md
index d3f22a5..e010821 100644
--- a/docs/zh/UserGuide/Data-Concept/Encoding.md
+++ b/docs/zh/UserGuide/Data-Concept/Encoding.md
@@ -33,7 +33,7 @@ PLAIN 编码，默认的编码方式，即不编码，支持多种数据类型
* 游程编码（RLE）
-游程编码，比较适合存储某些整数值连续出现的序列，不适合编码大部分情况下前后值不一样的序列数据。
+游程编码，比较适合存储某些数值连续出现的序列，不适合编码大部分情况下前后值不一样的序列数据。
游程编码也可用于对浮点数进行编码，但在创建时间序列的时候需指定保留小数位数（MAX_POINT_NUMBER，具体指定方式参见本文 [SQL 参考文档](../Appendix/SQL-Reference.md)）。比较适合存储某些浮点数值连续出现的序列数据，不适合存储对小数点后精度要求较高以及前后波动较大的序列数据。
@@ -66,4 +66,4 @@ GORILLA 编码是一种无损编码，它比较适合编码前后值比较接近
|DOUBLE |PLAIN, RLE, TS_2DIFF, GORILLA|
|TEXT |PLAIN, DICTIONARY|
-</div>
\ No newline at end of file
+</div>