[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407988#comment-15407988
]
Hadoop QA commented on AMBARI-17981:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12822064/ambari-17987.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8289//console
This message is automatically generated.
> Integrate Druid With Ambari
> ---------------------------
>
> Key: AMBARI-17981
> URL: https://issues.apache.org/jira/browse/AMBARI-17981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Nishant Bangarwa
> Labels: features
> Attachments: ambari-17987.patch
>
>
> This task includes adding support for druid cluster provisioning via Ambari.
> Details about Druid cluster design and different node types are present here
> -
> http://druid.io/docs/latest/design/design.html
> In general, Druid can be defined as a service in HDP which has following
> components -
> 1) Coordinator
> 2) Overlord
> 3) Historical
> 4) Broker
> 5) Middlemanager
>
> Druid also has external dependencies on following
> 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster
> 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS.
> 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a
> mysql instance provisioned by ambari itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
