[AMBARI-20594] Validate hive service dependencies based on the configuration on blueprint deployments

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.1
• Component/s: ambari-server
• Assignee: Laszlo Puskas
• Reporter: Laszlo Puskas
• Created: 27/Mar/17 18:42
• Updated: 16/Feb/18 13:13
• Resolved: 03/Apr/17 12:48

Description

Problem:
On blueprint deployments when the HIVE service is configured with default values the cluster provisioning fails if the MYSQL_SERVER component is not explicitly listed in the blueprint.

Solution:
When the cluster template is posted (so that all the configuration is together) the cluster topology is validated:

1. if hive service is required
2. if the default hive database is to be used
3. if the MYSQL_SERVER is not listed in the blueprint

then the cluster creation is interrupted and appropriate error is returned .

Issue Links

• relates to: AMBARI-10776 blueprint topology validation doesn't properly handle the 'auto deploy' component dependency graph