[jira] [Commented] (AMBARI-20594) Validate hive service dependencies based on the configuration on blueprint deployments

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-20594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945240#comment-15945240 ] 

Hadoop QA commented on AMBARI-20594:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12860862/AMBARI-20594.trunk.v4.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11212//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11212//console

This message is automatically generated.

> Validate hive service dependencies based on the configuration on blueprint deployments
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20594
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20594
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20594.trunk.v4.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> 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:
> # if hive service is required
> # if the default hive database is to be used
> # if the MYSQL_SERVER is not listed in the blueprint
> then the cluster creation is interrupted and appropriate error is returned .



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)