[
https://issues.apache.org/jira/browse/AMBARI-21072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017349#comment-16017349
]
Oleg Nechiporenko commented on AMBARI-21072:
--------------------------------------------
+1 for patch
> Removal of from/to Upgrade Versions in Web Client
> -------------------------------------------------
>
> Key: AMBARI-21072
> URL: https://issues.apache.org/jira/browse/AMBARI-21072
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 3.0.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21072.patch
>
>
> Beginning with AMBARI-21022, there is no longer a single from/to version for
> a given upgrade/downgrade. The following properties have been removed:
> {code}
> Upgrade/repository_version
> Upgrade/from_version
> Upgrade/to_version
> {code}
> Instead, they have been replaced with:
> {code}
> Upgrade/repository_version_id
> Upgrade/associated_version
> Upgrade/versions
> {code}
> - {{Upgrade/repository_version_id}} - the ID of the repository when creating
> a new upgrade. This replaces the ambiguous "repository_version" field which
> was previously used.
> - {{Upgrade/associated_version}} - a read-only property which gives you
> either the "upgrade to" version or "downgrade from" version. It's
> "associated" with the upgrade's direction. This will help you build strings
> like, "Upgrading to 2.5.0.0" and "Downgrading from 2.5.0.0". The prior way of
> display this "Downgrading to 2.5.0.0" is incorrect now as services can be
> downgraded to different versions.
> - {{Upgrade/versions}} - a read-only structure which essentially gives you
> the to/from of each service in the upgrade. Example:
> {code:title=Upgrade of STORM/ZK On Different Repos}
> "Upgrade": {
> "associated_version": "2.5.4.0-121",
> "cluster_name": "c1",
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 100,
> "request_context": "Upgrading to 2.5.4.0-121",
> "request_id": 18,
> "request_status": "COMPLETED",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING",
> "versions": {
> "STORM": {
> "from_repository_id": 1,
> "from_repository_version": "2.5.0.0-1237",
> "target_repository_id": 5,
> "target_repository_version": "2.5.4.0-121"
> },
> "ZOOKEEPER": {
> "from_repository_id": 2,
> "from_repository_version": "2.5.2.9-9999",
> "target_repository_id": 5,
> "target_repository_version": "2.5.4.0-121"
> }
> }
> },
> {code}
> {code:title=Downgrade of STORM/ZK Back To Different Repos}
> "Upgrade": {
> "associated_version": "2.5.4.0-121",
> "cluster_name": "c1",
> "direction": "DOWNGRADE",
> "downgrade_allowed": false,
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 100,
> "request_context": "Downgrading from 2.5.4.0-121",
> "request_id": 18,
> "request_status": "COMPLETED",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING",
> "versions": {
> "STORM": {
> "from_repository_id": 5,
> "from_repository_version": "2.5.4.0-121",
> "to_repository_id": 1,
> "to_repository_version": "2.5.0.0-1237"
> },
> "ZOOKEEPER": {
> "from_repository_id": 5,
> "from_repository_version": "2.5.4.0-121",
> "to_repository_id": 2,
> "to_repository_version": "2.5.2.9-9999"
> }
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)