ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Cutler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10945) Create a mainrepoid field in repoinfo.xml to indicate which repo base url will be updated
Date Wed, 06 May 2015 00:13:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-10945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Cutler updated AMBARI-10945:
----------------------------------
    Attachment: AMBARI-10945.patch

> Create a mainrepoid field in repoinfo.xml to indicate which repo base url will be updated
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10945
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10945
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Bryan Cutler
>            Assignee: Bryan Cutler
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-10945.patch
>
>
> During the Ambari upgrade process, StackUpgradeUtil.updateLocalRepo() attempts to update
the base URL of a repository with the assumption that the repoid will be in the form "stackName-stackVersion."
 If the repoid does not follow this, there is an error and the upgrade process can not continue.
> I propose that we add an optional field in repoinfo.xml that can define a "main" repository
to be updated so that there is no assumption of the repoid.  If this field is not provided,
then it will fall back to updating a repoid with "stackName-stackVersion."



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

Mime
View raw message