You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2015/01/06 00:30:35 UTC
[jira] [Updated] (AMBARI-8995) Service to advertise HDP version of
component during START in response's structuredOut
[ https://issues.apache.org/jira/browse/AMBARI-8995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Fernandez updated AMBARI-8995:
----------------------------------------
Attachment: AMBARI-8995.patch
> Service to advertise HDP version of component during START in response's structuredOut
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-8995
> URL: https://issues.apache.org/jira/browse/AMBARI-8995
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.0
>
> Attachments: AMBARI-8995.patch
>
>
> This is a prereq for (Rolling Upgrade - Finalize needs to complete upgrade states in DB, which can do other work in parallel), and is related to (Rolling Upgrade Bootstrap - Allow Ambari upgrade from 1.7.0 - 2.0.0 to populate new tables, which prepares the pre-reqs for a downgrade).
> Basically, when a service starts, the response's structuredOut needs to contain something like,
> {"version": "2.2.1.0-2175"}
> This Jira captures the python work to be done for all of the services.
> The backend will then store this in the hostcomponentstate table when the HeartBeatHandler detects it, and use it to bubble up information into the host_version and cluster_version tables
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)