[iotdb] branch master updated: [ISSUE-2656] Update GZIP compression type in user doc (#2657)

[ha...@apache.org]

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 b6586ff  [ISSUE-2656] Update GZIP compression type in user doc (#2657)
b6586ff is described below

commit b6586ff7534429ac23aa85020a8dd6522b872575
Author: Qi Yu <yu...@gmail.com>
AuthorDate: Tue Feb 9 10:52:39 2021 +0800

    [ISSUE-2656] Update GZIP compression type in user doc (#2657)
---
 docs/UserGuide/Concept/Compression.md    | 4 +++-
 docs/zh/UserGuide/Concept/Compression.md | 3 ++-
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/UserGuide/Concept/Compression.md b/docs/UserGuide/Concept/Compression.md
index 30a8d7f..6eb0f80 100644
--- a/docs/UserGuide/Concept/Compression.md
+++ b/docs/UserGuide/Concept/Compression.md
@@ -23,7 +23,7 @@
 
 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 available only 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, and supports three compression methods: 
+IoTDB allows you to specify the compression method of the column when creating a time series, and supports the following compression methods: 
 
 * UNCOMPRESSED
 
@@ -31,4 +31,6 @@ IoTDB allows you to specify the compression method of the column when creating a
 
 * LZ4
 
+* GZIP
+
 The specified syntax for compression is detailed in [Create Timeseries Statement](../Operation%20Manual/SQL%20Reference.md).
diff --git a/docs/zh/UserGuide/Concept/Compression.md b/docs/zh/UserGuide/Concept/Compression.md
index 91103b6..27bc24e 100644
--- a/docs/zh/UserGuide/Concept/Compression.md
+++ b/docs/zh/UserGuide/Concept/Compression.md
@@ -23,10 +23,11 @@
 
 当时间序列写入并按照指定的类型编码为二进制数据后，IoTDB会使用压缩技术对该数据进行压缩，进一步提升空间存储效率。虽然编码和压缩都旨在提升存储效率，但编码技术通常只适合特定的数据类型（如二阶差分编码只适合与INT32或者INT64编码，存储浮点数需要先将他们乘以10m以转换为整数），然后将它们转换为二进制流。压缩方式（SNAPPY）针对二进制流进行压缩，因此压缩方式的使用不再受数据类型的限制。
 
-IoTDB允许在创建一个时间序列的时候指定该列的压缩方式。现阶段IoTDB现在支持的压缩方式有三种：
+IoTDB允许在创建一个时间序列的时候指定该列的压缩方式。现阶段IoTDB支持以下几种压缩方式：
 
 * UNCOMPRESSED（不压缩）
 * SNAPPY压缩
 * LZ4压缩
+* GZIP压缩
 
 压缩方式的指定语法详见本文[5.4节](../Operation%20Manual/SQL%20Reference.md)。