You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2014/02/24 12:45:19 UTC
[jira] [Resolved] (AMBARI-4799) RMF. Lazy failing on wrong
configuration access is broken
[ https://issues.apache.org/jira/browse/AMBARI-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk resolved AMBARI-4799.
-------------------------------------
Resolution: Fixed
committed to trunk
> RMF. Lazy failing on wrong configuration access is broken
> ---------------------------------------------------------
>
> Key: AMBARI-4799
> URL: https://issues.apache.org/jira/browse/AMBARI-4799
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 1.5.0
>
>
> When we access the configuration which is not actually send from server, we should get exception early on access, rather then just hang until something breaks.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)