John Speidel created AMBARI-7937:
------------------------------------
Summary: Blueprint topology validation doesn't check
hive-env/hive_database when determining if MYSQL component is managed
Key: AMBARI-7937
URL: https://issues.apache.org/jira/browse/AMBARI-7937
Project: Ambari
Issue Type: Bug
Components: blueprints
Reporter: John Speidel
Assignee: Robert Nettleton
Fix For: 1.7.0
When a blueprint is submitted, topology validation performs some checks to
determine if the topology specified in the blueprint is valid. If the HIVE
service is included in the topology, the validator needs to ensure that the
hive database is either managed by the cluster or that an external database is
specified in config. To determine this, the validator checks the configuration
value of the property "global/hive_database". Now that global has been
deprecated and we now use "*-env" configurations, the validator needs to also
check "hive-env/hive_database" if the user provided this configuration.
Without this change, topology validation will fail when using an external HIVE
database if "hive-env/hive_database" is specified instead of
"global/hive_database".
The workaround for this is to use the deprecated "global/hive_database"
property or to disable topology validation via "?validate_topology=false".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
