[
https://issues.apache.org/jira/browse/AMBARI-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196444#comment-14196444
]
Hudson commented on AMBARI-8136:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #117 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/117/])
AMBARI-8136 - Views: creating instance of same name overwrites existing
(tbeerbower) (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dac8a9d7533f6d433935268594765b67b216adde)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProvider.java
> Views: creating instance of same name overwrites existing
> ---------------------------------------------------------
>
> Key: AMBARI-8136
> URL: https://issues.apache.org/jira/browse/AMBARI-8136
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 1.7.0
>
> Attachments: AMBARI-8136.patch
>
>
> Attempt to create an existing view instance fails as expected but updates
> in-memory representation of the existing instance.
> STR:
> 1. create view instance JOBS1
> 2. save, success
> 3. attempt to create another view instance and call it JOBS1
> 4. You are shown an error since the instance name needs to be unique. And API
> is showing a conflict. All that seems correct. Except, it overwrites all the
> view properties: display name, description, config params, etc. So I lost all
> my original settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
