[jira] [Commented] (AMBARI-15094) Patch Upgrade UpgradeCatalog Changes

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-15094:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #4382 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4382/])
AMBARI-15094 - Patch Upgrade UpgradeCatalog Changes (jonathanhurley) (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4f78af7ae47564fdc6a2c013cf1757f19005e6a5])
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/DbmsHelper.java
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/GenericDbmsHelper.java


> Patch Upgrade UpgradeCatalog Changes
> ------------------------------------
>
>                 Key: AMBARI-15094
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15094
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-upgrade
>    Affects Versions: 2.4.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.4.0
>
>
> This JIRA will be used to keep track of the changes required for the UpgradeCatalog that will be used for PU.
> +Changed tables+
> {{repo_version}}
> * Add {{type}} column, default 'STANDARD'
> * Add {{version_url}} varchar(1024)
> * Add {{version_xml}} mediumtext/text
> * Add {{version_xsd}} varchar(512)
> * Add {{parent_id}} bigint, nullable
> {{servicecomponentdesiredstate}}
> * Add PK {{id}} column
> * Remove existing PK, create {{UNIQUE}} constraint out of same columns
> * Create {{INDEX}} on old PK columns
> {{hostcomponentdesiredstate}}
> * Reorder {{hstcmpnntdesiredstatecmpnntnme}} {{FOREIGN KEY}}
> ** {{(component_name, service_name, cluster_id)}}
> {{hostcomponentstate}}
> * Reorder {{hstcomponentstatecomponentname}} {{FOREIGN KEY}}
> ** {{(component_name, service_name, cluster_id)}}
> {{servicecomponent_history}}
> * Creation of new table
> * Addition of new sequence to track PK ID



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