[
https://issues.apache.org/jira/browse/AMBARI-16030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253109#comment-15253109
]
Alejandro Fernandez commented on AMBARI-16030:
----------------------------------------------
I suggest renaming stop_time to end_time.
What will happen if the user attempts to upgrade from version x to y but it
fails (perhaps it did a partial upgrade of some sort).
Then they discard that particular upgrade, and pick some other version such as
z. In this case, we would want to know that upgrade x->y failed.
If the user does end up deleting ambari-server.log, it would be useful to
collect some error statements in this table, as well as the status.
> Ambari version history: Add ambari_version_history table for record keeping
> history of ambari versions
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16030
> URL: https://issues.apache.org/jira/browse/AMBARI-16030
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.4.0
>
>
> When investigating customer issues, information about history about Ambari
> versions is missing. We rely on this information to be provided in the EAR.
> Many times information in the EAR is inaccurate. Also information about when
> the Ambari upgrades actually happened in the past is completely missing.
> Instead of relying on this information to be provided, Ambari should record
> Ambari upgrade history in Ambari DB.
> {noformat}
> ambari_version_history
> Version Date Notes
> 2.2.2.0-1 02/09/2015 01:00:00 Clean Install
> 2.2.3.0-2 03/10/2015 01:00:00 Upgraded 2.2.2.0-1 ->
> 2.2.3.0-2
> 2.4.0.0-3 06/09/2015 01:00:00 Upgraded 2.2.3.0-2 ->
> 2.4.0.0-3
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
