As a participant, I cannot be more  excited for Kylin 3.0’s release.

I think Kylin 3.0 brings this project into a new era, it’s a real-time OLAP 
engine now. Meanwhile it keeps its great performance for the queries on 
extremely large historical data set. 



Best regards,

 

Ni Chunen / George



On 12/20/2019 21:49,Luke Han<[email protected]> wrote:
Congrats!

Almost 5 years after the first release (v0.7.1-incubating (First Apache
Release) - 2015-06-10 <http://kylin.apache.org/docs16/release_notes.html>).

Great milestone with the great community!


Best Regards!
---------------------

Luke Han


On Fri, Dec 20, 2019 at 8:45 PM ShaoFeng Shi <[email protected]> wrote:

The Apache Kylin team is pleased to announce the immediate availability of
the 3.0.0 release.

This is the GA release of Kylin’s next generation after 2.x, with the new
real-time OLAP feature, Kylin can query streaming data with sub-second
latency. All of the
changes in this release can be found in:
https://kylin.apache.org/docs/release_notes.html


You can download the source release and binary packages from Apache
Kylin's download page:https://kylin.apache.org/download/


Apache Kylin is an open-source Distributed Analytics Engine designed to
provide SQL interface and multi-dimensional analysis (OLAP) on Apache
Hadoop, supporting extremely
large datasets.


Apache Kylin lets you query massive dataset at sub-second latency in 3
steps:
1. Identify a star schema or snowflake schema data set on Hadoop.
2. Build Cube on Hadoop.
3. Query data with ANSI-SQL and get results in sub-second, via ODBC, JDBC
or RESTful API.


Thanks to everyone who has contributed to this release.


We welcome your help and feedback. For more information on how to report
problems, and to get involved, visit the project website at
https://kylin.apache.org/

Best regards,

Shaofeng Shi 史少锋
Apache Kylin PMC
Email: [email protected]

Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: [email protected]
Join Kylin dev mail group: [email protected]



Reply via email to