[
https://issues.apache.org/jira/browse/AMBARI-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877124#comment-15877124
]
Hudson commented on AMBARI-20055:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6802 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6802/])
AMBARI-20055 - Add Upgrade Logic For Removal of clusterconfigmapping (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9386eed4073cb8b75800f516ddfe01c3f6528bb4])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/GenericDbmsHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java
> 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)
