[
https://issues.apache.org/jira/browse/BIGTOP-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305835#comment-14305835
]
Richard Pelavin commented on BIGTOP-999:
----------------------------------------
Think it would l be straightforward to use the hiera setting
#hadoop_cluster_node::cluster_components:
# - crunch
# - flume
# - giraph
# - hbase
# ...
to be place where postgresql or mysql can be optionally included
On PuppetForge there are very hardened postgresql and mysql modules
https://forge.puppetlabs.com/puppetlabs/postgresql
https://forge.puppetlabs.com/puppetlabs/mysql
May be more sophisticated then needed but these could be easily hidden behind
bigtop puppet wrappers
Also newbie question is I dont know philosophy taken in bigtop about including
things like Puppet Forge modules
> 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)
