[
https://issues.apache.org/jira/browse/AMBARI-20433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-20433:
--------------------------------
Description:
Currently, service interdependency are statically defined in the stack
regardless its needed or not. For instance, Spark has a static dependency on
Hive and will force Hive to be installed whenever Spark is install, but Hive is
only needed if Spark Thrift Server component is installed.
It would be nice if the stack has the ability to declare the dependency
conditionally and at component level and the dependency will only be in effect
when the component is chosen.
was:
Currently, service interdependency are statically defined in the stack
regardless its needed or not. For instance, Spark has a static dependency on
Hive and will force Hive to be installed whenevern Spark is install, but Hive
is only needed if Spark Thrift Server component is installed.
It would be nice if the stack has to ability to declare the dependency
conditionally and at component level and the dependency will only be in effect
when the component is chosen.
> Need the ability to have dynamic dependency between component/services
> ----------------------------------------------------------------------
>
> Key: AMBARI-20433
> URL: https://issues.apache.org/jira/browse/AMBARI-20433
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Environment: all
> Reporter: Tuong Truong
> Assignee: Tim Thorpe
>
> Currently, service interdependency are statically defined in the stack
> regardless its needed or not. For instance, Spark has a static dependency on
> Hive and will force Hive to be installed whenever Spark is install, but Hive
> is only needed if Spark Thrift Server component is installed.
> It would be nice if the stack has the ability to declare the dependency
> conditionally and at component level and the dependency will only be in
> effect when the component is chosen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
