kylin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amareshwari Sriramdasu <>
Subject Understanding commonalties between kylin and lens
Date Fri, 26 Dec 2014 11:32:53 GMT
Hello Kylin developers,

I'm a developer at Apache Lens (,
doc avaialble at,
which tries solve similar problem as kylin wrt OLAP cubes. So, i'm sending
out this mail to understand commonalties and see if we can reuse and
collaborate on some.

Lens is an analytics platform which tries to give the ability to create
OLAP cube on top HCatalog tables, supports multiple storages to be the
underlying storage for fact and dimension data like HDFS, HBase,
traditional DWH, with pluggable execution engines to read the underlying
data. Lens provides other services like query lifecycle manager (with
history, statistics) which will allow to know which are the frequently
queried columns so that aggregated facts can be created on them.

You can see OLAP cube in lens here -

After going through the kylin docs(,  i
understand (correct me if i'm wrong) that
Kylin builds a cube by storing aggregated facts materialized in Hbase, it
constructs aggregated facts from tables in HDFS. It also provides ability
for administrator to define cube and cubeoids.

I see the commonalties are mainly wrt OLAP cube definitions. The
differentiators are Kylin gives an execution engine for running a query on
cube, whereas Lens doesn't have any execution engine in itself.

Let us know if the above details sound fine. If so, can look at what we can
do next to understand more.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message