ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Jackson (JIRA)" <j...@apache.org>
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.
Date Thu, 11 Jun 2015 15:46:00 GMT
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)

Mime
View raw message