You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2018/09/03 10:02:00 UTC

[jira] [Resolved] (KYLIN-3488) Support MySQL as Kylin metadata storage

     [ https://issues.apache.org/jira/browse/KYLIN-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaofeng SHI resolved KYLIN-3488.
---------------------------------
    Resolution: Fixed

> 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
>             Fix For: v2.5.0
>
>
> 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)