kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KYLIN-3488) Support MySQL as Kylin metadata storage
Date Mon, 03 Sep 2018 10:03:01 GMT

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

ASF GitHub Bot commented on KYLIN-3488:
---------------------------------------

shaofengshi commented on issue #216: KYLIN-3488 Support MySQL as Kylin metadata storage
URL: https://github.com/apache/kylin/pull/216#issuecomment-418066280
 
 
   Merged by patch with code review commit. Close this PR.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)

Mime
View raw message