[
https://issues.apache.org/jira/browse/AMBARI-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195710#comment-14195710
]
Hadoop QA commented on AMBARI-8136:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12679134/AMBARI-8136.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/488//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/488//console
This message is automatically generated.
> 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)
