Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 11 Jun 2015 15:46:00 +0000 (UTC)
From: "Christopher Jackson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12837178.1434037529000.46896.1434037560512@Atlassian.JIRA>
In-Reply-To: <JIRA.12837178.1434037529000@Atlassian.JIRA>
References: <JIRA.12837178.1434037529000@Atlassian.JIRA>
 <JIRA.12837178.1434037529240@arcas>
Subject: [jira] [Created] (AMBARI-11860) Add the capability for a component
 to specify in its own metainfo that it is a mandatory dependency to another
 component.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Christopher Jackson created AMBARI-11860:
--------------------------------------------

             Summary: Add the capability for a component to specify in its own metainfo that it is a mandatory dependency to another component.
                 Key: AMBARI-11860
                 URL: https://issues.apache.org/jira/browse/AMBARI-11860
             Project: Ambari
          Issue Type: New Feature
            Reporter: Christopher Jackson


When creating custom services it would be nice to be able to specify that the custom service component that you're creating is a dependency of some already existing services component. 

For example take the following use case:

I am writing a custom service with a client component that contains java libraries that contain custom HBase coprocessors. My custom component and its custom libraries must exist on all Nodes running an HBase component. I should be able to specify this in the metainfo.xml file of my custom service without needing to alter the HBase services metainfo.xml file.


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