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

Hudson commented on AMBARI-20542:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7150 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7150/])
AMBARI-20542 Fixed configuration type validation in case of blueprint (lpuskas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fb153e3e9ea9cafafb2c793d6ca2fa56da0a8533])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/validators/ClusterConfigTypeValidatorTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/validators/ClusterConfigTypeValidator.java


> Fixed configuration type validation in case of blueprint deployments.
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-20542
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20542
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>            Priority: Blocker
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20542.b-2.5.v2.patch, AMBARI-20542.trunk.v2.patch
>
>
> Extended configuration type validation to the configurations posted in 
> blueprints. (Previously only the configurations posted in the cluster 
> template were considered) 
> Also a bug prohibits blueprint deployments that doesn't contain all the 
> config types for services listed in the blueprint.



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

Reply via email to