You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2014/02/18 20:16:19 UTC
[jira] [Assigned] (AMBARI-4716) Run Ambari Server Upgrade via code
rather than DDL/DML.
[ https://issues.apache.org/jira/browse/AMBARI-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle reassigned AMBARI-4716:
---------------------------------------
Assignee: Myroslav Papirkovskyy (was: Siddharth Wagle)
Attached initial patch which applies on top of trunk.
> Run Ambari Server Upgrade via code rather than DDL/DML.
> -------------------------------------------------------
>
> Key: AMBARI-4716
> URL: https://issues.apache.org/jira/browse/AMBARI-4716
> Project: Ambari
> Issue Type: Task
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Siddharth Wagle
> Assignee: Myroslav Papirkovskyy
> Fix For: 1.5.0
>
> Attachments: AMBARI-4716.patch
>
>
> Evaluate running Ambari Server Upgrade via code rather than DDL/DML.
> The upgrade procedure has become a mammoth exercise and very error prone. We need to make sure we can do it via java code (which can be unit tested).
> If possible:
> ambari-server upgrade should do any database changes via java code which can use eclipse link to make any changes.
> This change allows devs to be flexible about what we can add in upgrade and also unit test those.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)