ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8995) Service to advertise HDP version of component during START in response's structuredOut
Date Wed, 07 Jan 2015 02:31:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267195#comment-14267195
] 

Hadoop QA commented on AMBARI-8995:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12690477/AMBARI-8995.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1209//console

This message is automatically generated.

> 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)

Mime
View raw message