You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "YoungWoo Kim (JIRA)" <ji...@apache.org> on 2015/02/04 10:04:34 UTC

[jira] [Commented] (BIGTOP-999) Consolidate metastores in Bigtop distribution

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

YoungWoo Kim commented on BIGTOP-999:
-------------------------------------

[~mgrover] Agreed and I'm interested in this! Actually the embedded metastores have certain limitations. However I'm curious the upstream projects have intersection in its supported databases. It might be MySQL or PostgreSQL is good candidate for this. If you have any ideas, please let me know. Thanks!

> Consolidate metastores in Bigtop distribution
> ---------------------------------------------
>
>                 Key: BIGTOP-999
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-999
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.6.0
>            Reporter: Mark Grover
>            Assignee: Mark Grover
>             Fix For: backlog
>
>
> Presently a bunch of components come with their own embedded metastores - Hive, Hue, Oozie, Sqoop. For some cases, an embedded metastore may work just fine for others, it's almost always need to change it to you a more practical non-embedded metastore.
> Given that Bigtop is a distribution of its own, it makes sense for it to consolidate all these metastores into one physical database.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)