You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/05/30 22:46:20 UTC
[jira] [Updated] (AMBARI-2233) Ensure version values are used
appropriately throughout Ambari
[ https://issues.apache.org/jira/browse/AMBARI-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Mohanty updated AMBARI-2233:
----------------------------------
Attachment: AMBARI-2233.patch
> Ensure version values are used appropriately throughout Ambari
> --------------------------------------------------------------
>
> Key: AMBARI-2233
> URL: https://issues.apache.org/jira/browse/AMBARI-2233
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.2.4
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 1.2.4
>
> Attachments: AMBARI-2233.patch
>
>
> The current version of Ambari build is being used in several scenarios:
> * Ensure Ambari Server installs the correct version of Ambari Agent
> * Ensure that Ambari Server only accepts registration from correct version of Ambari Agent
> * Ensure that DB version is compatible with Ambari Server
> ** The DB version itself will be used to control DB upgrades
> Towards this end the following open issues remain:
> * Get the build version be automatically embedded in the version file
> * Use the above for deploying agent as well as allowing agents to register
> * Regarding DB version there are two possible paths:
> ** Separate out DB version and have it be modified manually as needed
> ** Have the build version be used as DB version - this may make writing upgrade scripts little complicated as build version may change due to some proj mgmt decision
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira