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:46:32 UTC
[iotdb] branch master updated: Optimize the document format (#4658)
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 b7028de Optimize the document format (#4658)
b7028de is described below
commit b7028deb0353b8fc9a00041762b85ad35595d37e
Author: 肖志红 <73...@users.noreply.github.com>
AuthorDate: Wed Dec 29 16:45:03 2021 +0800
Optimize the document format (#4658)
---
docs/UserGuide/Data-Concept/Encoding.md | 4 +++-
docs/zh/UserGuide/Data-Concept/Encoding.md | 3 ++-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/docs/UserGuide/Data-Concept/Encoding.md b/docs/UserGuide/Data-Concept/Encoding.md
index ae94bb4..3a04b12 100644
--- a/docs/UserGuide/Data-Concept/Encoding.md
+++ b/docs/UserGuide/Data-Concept/Encoding.md
@@ -50,7 +50,9 @@ Usage restrictions: When using GORILLA to encode INT32 data, you need to ensure
* 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.
-* Correspondence between data type and encoding
+
+
+### Correspondence between data type and encoding
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.
diff --git a/docs/zh/UserGuide/Data-Concept/Encoding.md b/docs/zh/UserGuide/Data-Concept/Encoding.md
index 87e7f2e..5fea17e 100644
--- a/docs/zh/UserGuide/Data-Concept/Encoding.md
+++ b/docs/zh/UserGuide/Data-Concept/Encoding.md
@@ -51,7 +51,8 @@ GORILLA 编码是一种无损编码，它比较适合编码前后值比较接近
字典编码是一种无损编码。它适合编码基数小的数据（即数据去重后唯一值数量小）。不推荐用于基数大的数据。
-* 数据类型与编码的对应关系
+
+### 数据类型与编码的对应关系
前文介绍的五种编码适用于不同的数据类型，若对应关系错误，则无法正确创建时间序列。数据类型与支持其编码的编码方式对应关系总结如表格 2-3。