Apache Kylin : Analytical Data Warehouse for Big Data
Welcome to Kylin Wiki.
In this pages, I would like to list all new feature and break changes. Some features are in the status of IN PROGRESS, means Kylin team is going to implement this feature, and we will obey its priority. So if you have your suggestion/opinion on current priority, please let us know.
Basic feature
IN PROGRESS SOURCE IN PROGRESS SOURCE P1 FUTURE IN PROGRESS SOURCE P2 FUTURE IN PROGRESS SOURCE P2 FUTURE DELETED BUILD ENGINE READY BUILD ENGINE P0 4.0.0-ALPHA N/A BUILD ENGINE DELETED STORAGE ENGINE READY STORAGE ENGINE P0 4.0.0-ALPHA READY QUERY ENGINE P0 4.0.0-ALPHA READY MEASURE P0 4.0.0-ALPHA READY MEASURE P0 4.0.0-ALPHA IN PROGRESS MEASURE P0 4.0.0-BETA READY MEASURE 4.0.0-ALPHA READY QUERY ENGINE BEFORE 4.0 DEPRECATED METASTORE P2 BEFORE 4.0 READY METASTORE P0 BEFORE 4.0 IN PROGRESS TOOL P1 4.0.0-BETA READY TOOL P0 4.0.0-ALPHA READY SOURCE P1 4.0.0-ALPHA IN PROGRESS QUERY ENGINE P0 4.0.0-BETA DELETED N/A DELETED N/A READY BUILD ENGINE P0 4.0.0-ALPHA IN PROGRESS ADVENCED P0 4.0.0-BETA IN PROGRESS ADVENCED P0 4.0.0-BETA READY ADVENCED P0 4.0.0-ALPHA READY ADVENCED P0 4.0.0-ALPHA DELETED ADVENCED DELETED ADVENCED IN PROGRESS ENV P0 4.0.0-BETA IN PROGRESS ENV P0 4.0.0-ALPHA IN PROGRESS ENV P0 4.0.0-BETA IN PROGRESS ENV P2 FUTURE IN PROGRESS ENV P2 FUTUREFeature Description Comment Status Component Priority Expected Kafka Source(NRT) Ingest streaming data in batch way In design phase, did not have a conclusion of how to implement. P1FUTUREKafka Source(Real-time OLAP) Ingest streaming data in stream/micro-batch way In design phase, did not have a conclusion of how to implement. JDBC Source(Original version) Ingest data via JDBC contract In design phase, did not have a conclusion of how to implement. JDBC Source(Datasource SDK) Ingest data via JDBC contract In design phase, did not have a conclusion of how to implement. MapReduce Build Engine Build pre-calculated cuboid data by Hadoop Mapreduce This feature maybe useless Spark Build Engine Build pre-calculated cuboid data by Apache Spark New implementation provided Flink Build Engine Build pre-calculated cuboid data by Apache Flink Support in Kylin 3.1 HBase Storage Use HBase to store pre-calculated cuboid data. Discussion in mailing list Parquet Storage Use Parquet to store pre-calculated cuboid data. Discussion in mailing list Distributed Query Engine Use calcite&sparder(a.k.a. Spark with custom extension) toparse/analyse/excute a SQL query. New implementation provided Advanced Measure - Bitmap Advanced Measure - HLL Advanced Measure - TopN Advanced Measure - Percentile P0 Query Cache Cache query result in query's memory or external cache service. P0HBase Metastore Use HBase as metastore. Should be removed in the future. RDBMS Metastore Use RDBMS as metastore. Should as the first choice of metastore. Cardinality Computation Calculate cardinality of fact table and dimension table. Planning Storage Cleanup New implementation CSV Source New implementation SQL Standard Global Dictionary(Hive) New global dictionary will replace this feature. Global Dictionary(AppendTireDictionary) New global dictionary will replace this feature. Global Dictionary(Spark bucket dictionary) New implementation Cube Planner In design phase, did not have a conclusion of how to implement. System Cube and Dashboard Not well tested, planning Read write Seperatation New implementation provided Pushdown Engine New pushdown engine will only support SparkSQL. Shrunken Dictionary This feature maybe useless UHC dictionary This feature maybe useless Deploy on AWS EMR Planning Containerization(Quick-start) Planning Hadoop3 support Going to support Hadoop3 + Hive2 in 2020-Q4. Not sure when to suppoort Hive 3. Planning Hive3 support N/A Spark3 support N/A
Overview
Content Tools
ThemeBuilder
Apps