[
https://issues.apache.org/jira/browse/AMBARI-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592115#comment-14592115
]
Sumit Mohanty commented on AMBARI-12002:
----------------------------------------
[~jackson], for now a work-around will be to install the cluster and then use
Add Service or Add Component to add the custom service.
> Support ordered component installs.
> ------------------------------------
>
> Key: AMBARI-12002
> URL: https://issues.apache.org/jira/browse/AMBARI-12002
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Environment: HDP2.2, RHEL6
> Reporter: Christopher Jackson
>
> When defining a custom service it may involve a component which needs to
> modify another component. As such the order in which components install
> becomes important. This could be achieved by looking at the list of
> dependencies for a given component. It should enforce that all components
> listed as dependencies with a scope of host are installed prior to the given
> component.
> Per Sumit Mohanty, 'Its easy to implement an install order as well -
> basically call the same helper method as done for START.'
> In my use case I have CUSTOM_SERVICE/CUSTOM_CLIENT that has a scope:host
> dependency on HDFS/HDFS_CLIENT and HBASE/HBASE_CLIENT, I would expect
> HDFS_CLIENT and HBASE_CLIENT to install before CUSTOM_CLIENT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
