[jira] [Updated] (AMBARI-10639) Configuration Versions Should Be Calculated By the Database

["Jonathan Hurley (JIRA)" <ji...@apache.org>]

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

Jonathan Hurley updated AMBARI-10639:
-------------------------------------
    Attachment: AMBARI-10639.patch

> Configuration Versions Should Be Calculated By the Database
> -----------------------------------------------------------
>
>                 Key: AMBARI-10639
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10639
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10639.patch
>
>
> {{ConfigVersionHelper}} is used by Ambari to determine the "next" version when creating configuration versions and service configuration versions. This presents two problems:
> - In a distributed system, have an in-memory atomic does not work. When Ambari becomes HA aware, this will be problematic.
> - It does not support downgrading and removing the current maximum. There would need to be code added in various places to always remember to decrement this value. The decoupled nature is prone it error.
> Instead, this class should be removed in favor of calculate this from the database using a max() function on the column. This will allow removal of configurations during downgrade to properly revert to the prior configuration version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)