You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iotdb.apache.org by ha...@apache.org on 2021/12/29 08:02:58 UTC
[iotdb] branch rel/0.12 updated: [To rel/0.12][IOTDB-1874]Remove useless regulars and optimize formatting (#4653)
This is an automated email from the ASF dual-hosted git repository.
haonan pushed a commit to branch rel/0.12
in repository https://gitbox.apache.org/repos/asf/iotdb.git
The following commit(s) were added to refs/heads/rel/0.12 by this push:
new 191f61d [To rel/0.12][IOTDB-1874]Remove useless regulars and optimize formatting (#4653)
191f61d is described below
commit 191f61d4281327163b3c729934015dfa1aa3aa1e
Author: 肖志红 <73...@users.noreply.github.com>
AuthorDate: Wed Dec 29 16:02:29 2021 +0800
[To rel/0.12][IOTDB-1874]Remove useless regulars and optimize formatting (#4653)
Co-authored-by: Haonan <hh...@outlook.com>
---
docs/UserGuide/Data-Concept/Encoding.md | 7 +------
docs/zh/UserGuide/Data-Concept/Encoding.md | 7 +------
2 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/docs/UserGuide/Data-Concept/Encoding.md b/docs/UserGuide/Data-Concept/Encoding.md
index 7a12011..7fb9f64 100644
--- a/docs/UserGuide/Data-Concept/Encoding.md
+++ b/docs/UserGuide/Data-Concept/Encoding.md
@@ -47,13 +47,8 @@ Currently, there are two versions of GORILLA encoding implementation, it is reco
Usage restrictions: When using GORILLA to encode INT32 data, you need to ensure that there is no data point with the value `Integer.MIN_VALUE` in the sequence. When using GORILLA to encode INT64 data, you need to ensure that there is no data point with the value `Long.MIN_VALUE` in the sequence.
-* REGULAR
-Regular data encoding is more suitable for time encoding regular sequence increasing data (e.g. the timeseries with the same time elapsed between each data point), in which case it's better than TS_2DIFF.
-
-Regular data encoding method is not suitable for the data with fluctuations (irregular data), and TS_2DIFF is recommended to deal with it.
-
-* Correspondence between data type and encoding
+### Correspondence between data type and encoding
The four 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.
diff --git a/docs/zh/UserGuide/Data-Concept/Encoding.md b/docs/zh/UserGuide/Data-Concept/Encoding.md
index 6265256..1034b24 100644
--- a/docs/zh/UserGuide/Data-Concept/Encoding.md
+++ b/docs/zh/UserGuide/Data-Concept/Encoding.md
@@ -47,13 +47,8 @@ GORILLA编码是一种无损编码，它比较适合编码前后值比较接近
使用限制：使用Gorilla编码INT32数据时，需要保证序列中不存在值为`Integer.MIN_VALUE`的数据点；使用Gorilla编码INT64数据时，需要保证序列中不存在值为`Long.MIN_VALUE`的数据点。
-* 定频数据编码 (REGULAR)
-定频数据编码，仅适用于整型（INT32）和长整型（INT64）的时间列定频数据，且允许数据中有一些点缺失，使用此方法编码定频数据优于二阶差分编码（TS_2DIFF）。
-
-定频数据编码无法用于非定频数据，建议使用二阶差分编码（TS_2DIFF）进行处理。
-
-* 数据类型与编码的对应关系
+### 数据类型与编码的对应关系
前文介绍的四种编码适用于不同的数据类型，若对应关系错误，则无法正确创建时间序列。数据类型与支持其编码的编码方式对应关系总结如表格2-3。