ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-6907) Config History: should display new current version after reverting to an old version
Date Tue, 19 Aug 2014 18:35:19 GMT

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

Yusaku Sako commented on AMBARI-6907:
-------------------------------------

+1 for the 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)

Mime
View raw message