Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 5 Jan 2017 09:46:58 +0000 (UTC)
From: "Nate Cole (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13032212.1483609586000.648422.1483609618654@Atlassian.JIRA>
In-Reply-To: <JIRA.13032212.1483609586000@Atlassian.JIRA>
References: <JIRA.13032212.1483609586000@Atlassian.JIRA> <JIRA.13032212.1483609586342@arcas>
Subject: [jira] [Created] (AMBARI-19381) Heartbeat version transitions must
 be change to Component instead of Cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 05 Jan 2017 09:47:00 -0000

Nate Cole created AMBARI-19381:
----------------------------------

             Summary: Heartbeat version transitions must be change to Component instead of 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)