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

Tom Beerbower updated AMBARI-8136:
----------------------------------
    Description: 
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.


  was:
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.



> 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)

Reply via email to