You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Luke Han (JIRA)" <ji...@apache.org> on 2016/10/08 00:06:20 UTC
[jira] [Commented] (KYLIN-2065) kylin result cache improvement
[ https://issues.apache.org/jira/browse/KYLIN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556693#comment-15556693 ]
Luke Han commented on KYLIN-2065:
---------------------------------
[~feng_xiao_yu] this is really great features many people are looking for a while.
Please share more detail about your design, idea and patch too.
Would love to see a sample or testing result if possible:-)
Thanks.
> kylin result cache improvement
> ------------------------------
>
> Key: KYLIN-2065
> URL: https://issues.apache.org/jira/browse/KYLIN-2065
> Project: Kylin
> Issue Type: Improvement
> Reporter: fengYu
> Assignee: fengYu
>
> data stored in kylin(hbase) is rarely modified, except some one refresh a segment, I think a result cache is useful, kylin support in-memory ehcache, but it is limited and can not share between query nodes, we develop a cache solution which store in hbase and expire based on cube last-modify-time or segment last-modify-time.
> I will arrange the patch on 1.5.4 which will upload later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)