+1

Rongchuan.Jin
 

在 2019/1/25 上午11:37,“PENG Zhengshuai”<[email protected]> 写入:

    +1
    
    > On Jan 23, 2019, at 11:15 PM, Chao Long <[email protected]> wrote:
    > 
    > +1
    > 
    > 
    > For parquet storage, I recently completed the development of removing 
dict from the query side, and the query performance has been inproved a lot. 
But there is still a lot of work to do, like removing query single-point issue, 
upgrading parquet to 1.11 for page index and etc. So I think release it in 
Kylin 3.0 is a great choice.
    > ------------------
    > Best Regards,
    > Chao Long
    > 
    > 
    > ------------------ 原始邮件 ------------------
    > 发件人: "ShaoFeng Shi"<[email protected]>;
    > 发送时间: 2019年1月23日(星期三) 下午3:56
    > 收件人: "dev"<[email protected]>;
    > 
    > 主题: [Discuss] Moving toward Apache Kylin 3.0
    > 
    > 
    > 
    > Hi Kylin developers,
    > 
    > In last week, Kylin released v2.6.0, with the enhanced & distributed query
    > cache and JDBC data source SDK. After this release, the next batch
    > candidate features include real-time streaming, parquet storage, and druid
    > storage. These features were developed in the past 1-2 years by different
    > Kylin players and were open sourced in the past 6 months. They have 
already
    > been staged in separate branches and are under evaluation by the 
community.
    > We have received much feedback from the community.
    > 
    > These candidate features are big supplements to as-is Kylin functions; For
    > example, the real-time streaming feature will bring Kylin from batch &
    > historical analytics into real-time analytics. The parquet storage will
    > make the deployment more flexible and more cloud-friendly. Of course,
    > stabilizing and improving these features need additional time and effort.
    > 
    > So, when we merging and releasing them, we'd better give it a new version
    > number so that user can clearly know the difference with current 2.x
    > versions. I discussed this with several developers offline, we think it is
    > time to move toward Kylin 3.0. So, if one of the above features is merged,
    > the version will be 3.0. The current 2.6 will be maintained until 3.x is
    > ready for production use.
    > 
    > Your comments, ideas, and suggestions are welcomed!
    > 
    > Best regards,
    > 
    > Shaofeng Shi 史少锋
    > Apache Kylin PMC
    > Work email: [email protected]
    > Kyligence Inc: https://kyligence.io/
    > 
    > 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