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

Posted to dev@ambari.apache.org by "Xi Wang (JIRA)" <ji...@apache.org> on 2014/08/19 02:39:18 UTC

[jira] [Updated] (AMBARI-6907) Config History: should display new current version after reverting to an old version

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

Xi Wang updated AMBARI-6907:
----------------------------

    Attachment: AMBARI-6907.patch

> Config History: should display new current version after reverting to an old version
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-6907
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6907
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.7.0
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6907.patch
>
>
> FE issue after: 
> https://issues.apache.org/jira/browse/AMBARI-6848. Service config version should always clone and rev up (not simply point to an older version)
> say, there is v1, v2, v3(current).
> clicking on 'Make current' when displaying v1 ,
> now UI display v1 as current version,
> However the correct behavior should be : display v4 as current 



--
This message was sent by Atlassian JIRA
(v6.2#6252)