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/06/30 08:25:36 UTC
[iotdb] branch remove_regular created (now 62b6716)
This is an automated email from the ASF dual-hosted git repository.
qiaojialin pushed a change to branch remove_regular
in repository https://gitbox.apache.org/repos/asf/iotdb.git.
at 62b6716 remove REGULAR encoding docs
This branch includes the following new commits:
new 62b6716 remove REGULAR encoding docs
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[iotdb] 01/01: remove REGULAR encoding docs
Posted by qi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
qiaojialin pushed a commit to branch remove_regular
in repository https://gitbox.apache.org/repos/asf/iotdb.git
commit 62b6716c54be8df54cec2404b6029f265f26e266
Author: qiaojialin <64...@qq.com>
AuthorDate: Wed Jun 30 16:24:56 2021 +0800
remove REGULAR encoding docs
---
docs/UserGuide/Data-Concept/Encoding.md | 6 ------
docs/zh/UserGuide/Data-Concept/Encoding.md | 6 ------
2 files changed, 12 deletions(-)
diff --git a/docs/UserGuide/Data-Concept/Encoding.md b/docs/UserGuide/Data-Concept/Encoding.md
index 5b44184..a87fbdc 100644
--- a/docs/UserGuide/Data-Concept/Encoding.md
+++ b/docs/UserGuide/Data-Concept/Encoding.md
@@ -47,12 +47,6 @@ 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.
-
* DICTIONARY
DICTIONARY encoding is lossless. It is suitable for TEXT data with low cardinality (i.e. low number of distinct values). It is not recommended to use it for high-cardinality data.
diff --git a/docs/zh/UserGuide/Data-Concept/Encoding.md b/docs/zh/UserGuide/Data-Concept/Encoding.md
index 787c833..8750f95 100644
--- a/docs/zh/UserGuide/Data-Concept/Encoding.md
+++ b/docs/zh/UserGuide/Data-Concept/Encoding.md
@@ -47,12 +47,6 @@ GORILLA编码是一种无损编码，它比较适合编码前后值比较接近
使用限制：使用Gorilla编码INT32数据时，需要保证序列中不存在值为`Integer.MIN_VALUE`的数据点；使用Gorilla编码INT64数据时，需要保证序列中不存在值为`Long.MIN_VALUE`的数据点。
-* 定频数据编码 (REGULAR)
-
-定频数据编码，仅适用于整型（INT32）和长整型（INT64）的时间列定频数据，且允许数据中有一些点缺失，使用此方法编码定频数据优于二阶差分编码（TS_2DIFF）。
-
-定频数据编码无法用于非定频数据，建议使用二阶差分编码（TS_2DIFF）进行处理。
-
* 字典编码 （DICTIONARY）
字典编码是一种无损编码。它适合编码基数小的数据（即数据去重后唯一值数量小）。不推荐用于基数大的数据。