You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2013/12/10 19:10:07 UTC

[jira] [Commented] (AMBARI-4036) RMF: change the way we work with not existant configs

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

Dmitry Lysnichenko commented on AMBARI-4036:
--------------------------------------------

+1

> RMF: change the way we work with not existant configs
> -----------------------------------------------------
>
>                 Key: AMBARI-4036
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4036
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4036.patch
>
>
> Bugs that occur when server stops sending some command or config parameter (for example, due to xml configs changes) are extremely hard to detect if we use something like hdp_default.
> In RMF, this issue is partially fixed (we fail fast  on first usage of iundefined parameter), but it is not the case when using J2.
> Also now default is not really suitable since configurations json can be really different.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)