[ https://issues.apache.org/jira/browse/AMBARI-20122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Thorpe updated AMBARI-20122: -------------------------------- Description: After resolution of AMBARI-19685, stack advisor validates if stack defined dependency is not satisfied but recommendation API does not account for this. Stack defined dependencies are service/component based and has a scope CLUSTER|HOST. During recommendation the services to install have already been selected. We can't really utilize the cluster scope because either the dependent service was selected or it was not. If it was not selected it will be caught during validation. We can only recommend based on HOST scope. This JIRA is also limited to only handling those which don't have conditional dependencies. was: After resolution of AMBARI-19685, stack advisor validates if stack defined dependency is not satisfied but recommendation API does not account for this. stack defined dependencies are servicecomponent based and has a scope CLUSTER|HOST > Stack advisor needs to recommend dependency for slaves and masters > ------------------------------------------------------------------ > > Key: AMBARI-20122 > URL: https://issues.apache.org/jira/browse/AMBARI-20122 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 3.0.0 > Reporter: Jaimin Jetly > Assignee: Tim Thorpe > Fix For: 3.0.0 > > Attachments: AMBARI-20122.patch > > > After resolution of AMBARI-19685, stack advisor validates if stack defined > dependency is not satisfied but recommendation API does not account for this. > Stack defined dependencies are service/component based and has a scope > CLUSTER|HOST. > During recommendation the services to install have already been selected. We > can't really utilize the cluster scope because either the dependent service > was selected or it was not. If it was not selected it will be caught during > validation. We can only recommend based on HOST scope. > This JIRA is also limited to only handling those which don't have conditional > dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)