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

Hadoop QA commented on AMBARI-14776:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12785366/AMBARI-14776_trunk.patch
  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 tests.
                        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 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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5132//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5132//console

This message is automatically generated.

> Accumulo service check improvements
> -----------------------------------
>
>                 Key: AMBARI-14776
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14776
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 2.3.0
>
>         Attachments: AMBARI-14776_trunk.patch
>
>
> Was looking at a failed Accumulo service check and noticed that there are a 
> few things that could be improved to make the check more reliably accurate.
> 1. The Accumulo table is generically named "testtable". We should name this 
> something specific to "Ambari" and "service check".
> 2. Ensure that the table doesn't exist before trying to create it.



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

Reply via email to