Repository: kylin
Updated Branches:
  refs/heads/document d7507f217 -> fa1bd3732


remove extra blank


Project: http://git-wip-us.apache.org/repos/asf/kylin/repo
Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/fa1bd373
Tree: http://git-wip-us.apache.org/repos/asf/kylin/tree/fa1bd373
Diff: http://git-wip-us.apache.org/repos/asf/kylin/diff/fa1bd373

Branch: refs/heads/document
Commit: fa1bd3732822906ec34805c90d8179349d0be12c
Parents: d7507f2
Author: shaofengshi <shaofeng...@apache.org>
Authored: Mon May 22 22:18:16 2017 +0800
Committer: shaofengshi <shaofeng...@apache.org>
Committed: Mon May 22 22:18:16 2017 +0800

----------------------------------------------------------------------
 website/community/poweredby.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kylin/blob/fa1bd373/website/community/poweredby.md
----------------------------------------------------------------------
diff --git a/website/community/poweredby.md b/website/community/poweredby.md
index 520e4d0..5175cde 100644
--- a/website/community/poweredby.md
+++ b/website/community/poweredby.md
@@ -46,7 +46,7 @@ __Companies & Organizations__
 * [Qunar](https://www.qunar.com)  (_NASDAQ:QUNR_)
     * Apache Kylin is used at Qunar for Data Analysis Engine on 
Hadoop, which offers powerful OLAP capability for flight business with 
good performance.
 * [Strikingly](https://strikingly.com/) 
-    *  Strikingly adopted Kylin + AWS EMR solution. By adopting Kylin, the 
query performance was improved from 5 ~ 10 seconds to less than 1 second, and 
it can serve much more concurrent requests now. When workload and data 
increases, we just need add EMR nodes on demand then get capacity expanded. 
This architecture ensures we don't need worry about the data growth in next 
couple years.
+    * Strikingly adopted Kylin + AWS EMR solution. By adopting Kylin, the 
query performance was improved from 5 ~ 10 seconds to less than 1 second, and 
it can serve much more concurrent requests now. When workload and data 
increases, we just need add EMR nodes on demand then get capacity expanded. 
This architecture ensures we don't need worry about the data growth in next 
couple years.
 * [Yahoo! Japan](https://about.yahoo.co.jp/info/en/) 
-    *  Yahoo! JAPAN uses Apache Kylin to generate tailored report for Yahoo! 
Shopping. Apache Kylin contributes to minimize the latency for viewing the 
report. Consequently, the platform team has been released from ad hoc tasks to 
improve performance and it has become possible to focus on adding functions for 
users.
+    * Yahoo! JAPAN uses Apache Kylin to generate tailored report for Yahoo! 
Shopping. Apache Kylin contributes to minimize the latency for viewing the 
report. Consequently, the platform team has been released from ad hoc tasks to 
improve performance and it has become possible to focus on adding functions for 
users.
 

Reply via email to