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

Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2017/12/04 16:23:00 UTC

[jira] [Updated] (AMBARI-22353) Remove properties.json And Switch To Adding Properties to ResourceProviders Dynamically

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

Dmitry Lysnichenko updated AMBARI-22353:
----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   24c64b44d9..e77a31ab0a  trunk -> trunk


> Remove properties.json And Switch To Adding Properties to ResourceProviders Dynamically
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22353
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22353
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-22353.patch
>
>
> Legacy/ancient ResourceProviders use the {{properties.json}} file to govern which properties can be used with the provider. This seems like excessive decoupling without any benefit and usually leads to runtime errors when new or removed properties are forgotten.
> This file should be removed and the providers should be registering the known properties on their own.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)