[
https://issues.apache.org/jira/browse/AMBARI-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221589#comment-14221589
]
Hudson commented on AMBARI-8361:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #302 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/302/])
AMBARI-8361. Configs: UI breaks during particular flow.(xiwang) (xiwang:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=870a5a5795f7ae757b47679281dcfcf64e6cfbaf)
* ambari-web/app/controllers/main/service/info/configs.js
> Configs: UI breaks during particular flow
> -----------------------------------------
>
> Key: AMBARI-8361
> URL: https://issues.apache.org/jira/browse/AMBARI-8361
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8361.patch, AMBARI-8361.patch,
> broken-versions.tiff
>
>
> Configs UI breaks with the following flow:
> 1) go to tez
> 2) edit tez.am.resource.memory.mb and make 1
> 3) click save
> 4) that prompts the warning that this is not a recommended value
> 5) click cancel
> 6) browse to pig
> 7) you are prompted you have unsaved changes, click discard
> 9) Pig configs ui ends up broken
> have to browse away and come back for it to straighten out. See attached for
> example of broken-ness.
> Reason: when trying to save changes for Tez, we set a
> "preSelectedConfigVersion", but the save was canceled later, on "discard" we
> need to clear that value
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)