ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-21098) Integrate Titan into Ambari
Date Mon, 19 Jun 2017 16:06:00 GMT


Hadoop QA commented on AMBARI-21098:

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-agent ambari-server

Console output:

This message is automatically generated.

> Integrate Titan into Ambari
> ---------------------------
>                 Key: AMBARI-21098
>                 URL:
>             Project: Ambari
>          Issue Type: Story
>    Affects Versions: trunk, 2.5.1
>            Reporter: Hui Cao
>            Assignee: Hui Cao
>              Labels: titan
>             Fix For: trunk
>         Attachments: AMBARI-21098.patch, Ambari integration for Titan design doc.pdf
>   Original Estimate: 504h
>  Remaining Estimate: 504h
> Titan is designed to support the processing of graphs so large that they require storage
and computational capacities beyond what a single machine can provide. Scaling graph data
processing for real time traversals and analytical queries is Titan’s foundational benefit.
> This story is aimed to integrate Titan into Ambari so that it can be installed and managed
by Ambari from web UI.

This message was sent by Atlassian JIRA

View raw message