ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-21912) Make Ambari changes for external-conf
Date Mon, 11 Sep 2017 15:41:00 GMT


Hadoop QA commented on AMBARI-21912:

{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:red}-1 core tests{color}.  The test build failed in [ambari-server|]

Console output:

This message is automatically generated.

> Make Ambari changes for external-conf
> -------------------------------------
>                 Key: AMBARI-21912
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Prabhjyot Singh
>            Assignee: Prabhjyot Singh
>         Attachments: AMBARI-21912_trunk_v1.patch
> When the user upgrades from HDP-2.5.x to HDP-2.6.x, they have to do these manual steps
listed here,
to make JDBC(phoenix) works.

This message was sent by Atlassian JIRA

View raw message