[AMBARI-21683] Service and Patch Upgrade Catalog Changes for 3.0

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Won't Do
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Component/s: ambari-upgrade
• Epic Link: Ambari: Patch Upgrades
• Assignee: Jonathan Hurley
• Reporter: Dmitry Lysnichenko
• Created: 08/Aug/17 17:45
• Updated: 15/Feb/18 20:48
• Resolved: 15/Feb/18 20:48

Description

Implement the following upgrade catalog changes related to service/patch upgrades:

servicecomponentdesiredstate

• Remove: desired_stack_id BIGINT NOT NULL
• Remove: desired_version VARCHAR(255) NOT NULL DEFAULT 'UNKNOWN'
• Remove: FK on desired_stack_id (FK_scds_desired_stack_id)
• Add: desired_repo_version_id BIGINT NOT NULL
• Add: FK to repo_version_id (FK_scds_desired_repo_id)

hostcomponentdesiredstate

• Remove: desired_stack_id BIGINT NOT NULL
• Remove: FK on desired_stack_id (FK_hcds_desired_stack_id)

hostcomponentstate

• Remove: current_stack_id BIGINT NOT NULL
• Remove: FK on desired_stack_id (FK_hcs_current_stack_id)

servicedesiredstate

• Remove: desired_stack_id BIGINT NOT NULL
• Add: desired_repo_version_id BIGINT NOT NULL
• Add: FK to repo_version_id (FK_repo_version_id)

host_version

• Change the UNIQUE constraint to allow for multiple CURRENT repositories per host. Restriction should also include the repo_version_id for uniqueness now.

cluster_version

• This table was removed.

servicecomponent_version

• Create this table and populate with data

upgrade

• Add orchestration VARCHAR(255) NOT NULL DEFAULT 'STANDARD'

Issue Links

• is a clone of: AMBARI-21169 Service and Patch Upgrade Catalog Changes for 2.6.0