You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2017/01/05 10:01:12 UTC

[jira] [Updated] (AMBARI-19381) Heartbeat version transitions must be update Component alongside Cluster

     [ https://issues.apache.org/jira/browse/AMBARI-19381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole updated AMBARI-19381:
-------------------------------
    Summary: Heartbeat version transitions must be update Component alongside Cluster  (was: Heartbeat version transitions must be change to Component instead of Cluster)

> Heartbeat version transitions must be update Component alongside Cluster
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-19381
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19381
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 3.0.0
>
>
> Cluster can no longer be considered CURRENT on any singular version.  Several repositories can be current.  In that regard, heartbeats should be updating the component record with the appropriate repository status, and make sure there is a version record for the repository.
> * On heartbeat, create servicecomponent_version records
> * On cluster install (via install_packages), create servicecomponent_version records, if required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)