[
https://issues.apache.org/jira/browse/AMBARI-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21022:
-------------------------------------
Attachment: AMBARI-21022.patch
> Upgrades Should Be Associated With Repositories Instead of String Versions
> --------------------------------------------------------------------------
>
> Key: AMBARI-21022
> URL: https://issues.apache.org/jira/browse/AMBARI-21022
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-21022.patch
>
>
> The upgrade entity is modeled currently to store only references to versions
> For example, to_version is "2.5.0.0-1234" and from_version is "2.3.0.0-1".
> This presents a problem with support for multiple repositories since two
> stacks could potentially have the same version, thus preventing a repository
> from being retrieved simply by its no-longer-unique version.
> Instead, the upgrade should be associated with a {{RepositoryVersionEntity}}
> and enforced in the database.
> Using repository associations will also help to track the to/from history for
> components included in the upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
