Hadoop QA commented on AMBARI-17981:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
Console output: 

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
>    Affects Versions: 2.5.0
>            Reporter: Nishant Bangarwa
>              Labels: features
>         Attachments: ambari-17981.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

Reply via email to