You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/09/03 08:26:00 UTC
[jira] [Commented] (KYLIN-3488) Support MySQL as Kylin metadata
storage
[ https://issues.apache.org/jira/browse/KYLIN-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601879#comment-16601879 ]
ASF subversion and git services commented on KYLIN-3488:
--------------------------------------------------------
Commit 210719296973214bff7dcaf9a076d535ae7f7ddc in kylin's branch refs/heads/2.5.x from GinaZhai
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=2107192 ]
KYLIN-3488 Support Mysql as Kylin metadata storage
> 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)