ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laszlo Puskas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20594) Validate hive service dependencies based on the configuration on blueprint deployments
Date Tue, 28 Mar 2017 12:31:41 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-20594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Laszlo Puskas updated AMBARI-20594:
-----------------------------------
    Attachment: AMBARI-20594.trunk.v4.patch

> 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)

Mime
View raw message