ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20055) Add Upgrade Logic For Removal of clusterconfigmapping
Date Tue, 21 Feb 2017 02:14:44 GMT

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

Hadoop QA commented on AMBARI-20055:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12853615/AMBARI-20055.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 1 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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Add Upgrade Logic For Removal of clusterconfigmapping
> -----------------------------------------------------
>
>                 Key: AMBARI-20055
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20055
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: trunk
>
>         Attachments: AMBARI-20055.patch
>
>
> The Ambari upgrade scripts should now perform the following operations:
> - Adding the following columns / constraints to the {{clusterconfig}} table:
> -- {{selected SMALLINT NOT NULL DEFAULT 0}} - whether or not the configuration is currently
selected
> -- {{selected_timestamp BIGINT NOT NULL DEFAULT 0}} - the last time that the configuration
was marked as {{selected}}
> - Finding all {{selected}} mappings in {{clusterconfigmapping}} and marked their associated
entry in {{clusterconfig}} as {{selected}}
> - Removal of the {{clusterconfigmapping}} table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message