[ 
https://issues.apache.org/jira/browse/KYLIN-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601880#comment-16601880
 ] 

ASF subversion and git services commented on KYLIN-3488:
--------------------------------------------------------

Commit 854ac500e25a4c4e7da98b27abbeb3d43eef6889 in kylin's branch 
refs/heads/2.5.x from shaofengshi
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=854ac50 ]

KYLIN-3488 code review


> Support MySQL as Kylin metadata storage
> ---------------------------------------
>
>                 Key: KYLIN-3488
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3488
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Metadata
>            Reporter: Shaofeng SHI
>            Priority: Major
>
> Kylin uses HBase as the metastore; But in some cases user expects the 
> metadata not in HBase.
> Sonny Heer from mailing list mentioned:
> "I'm fairly certain anyone using Kylin with AWS EMR will benefit from this.   
> Having multiple hbase clusters across AZs is a huge benefit.  BTW only thing 
> blocking at the moment is write operations happening from kylin query nodes."



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to