You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kylin.apache.org by sh...@apache.org on 2019/03/22 10:23:38 UTC
[kylin] branch document updated: Update
2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md
This is an automated email from the ASF dual-hosted git repository.
shaofengshi pushed a commit to branch document
in repository https://gitbox.apache.org/repos/asf/kylin.git
The following commit(s) were added to refs/heads/document by this push:
new befa20e Update 2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md
befa20e is described below
commit befa20e311b85527c21becfd0e9d0aa44dbfa4e3
Author: Nikhil <ni...@Nikhil-Jains-MacBook-Pro.local>
AuthorDate: Fri Mar 22 18:05:47 2019 +0800
Update 2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md
Corrected the field name used in the example.
---
.../2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/_posts/blog/2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md b/website/_posts/blog/2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md
index 11c7df5..1877ae4 100644
--- a/website/_posts/blog/2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md
+++ b/website/_posts/blog/2018-12-12-why-did-meituan-develop-kylin-on-druid-part1-of-2.md
@@ -81,7 +81,7 @@ Meituan deployed into production an offline OLAP platform with Apache Kylin as i
Kylin stores its data in HBase by converting the Dimensions and Measures into HBase Keys and Values, respectively. As HBase doesn’t support secondary index and only has one RowKey index, Kylin’s Dimension values will be combined into a fixed sequence to store as RowKey. In this way, filtering on a Dimension in the front of the sequence will perform better than those at the back. Here’s an example:
-In the testing environment, there are two almost identical Cubes (Cube1 and Cube2). They both have the same data source and the same Dimensions/Measures. The only difference is the order of the Dimensions in the RowKey: Cube1 puts P_LINEORDER.LO_CUSTKEY at the first while Cube2 the last.
+In the testing environment, there are two almost identical Cubes (Cube1 and Cube2). They both have the same data source and the same Dimensions/Measures. The only difference is the order of the Dimensions in the RowKey: Cube1 puts P_LINEORDER.LO_ORDERKEY at the first while Cube2 the last.
Graphic 5 Cube1 RowKey Sequence