[jira] [Updated] (AMBARI-23590) Return mpack info even when attempting to register duplicate mpack
[ https://issues.apache.org/jira/browse/AMBARI-23590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-23590: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Return mpack info even when attempting to register duplicate mpack > -- > > Key: AMBARI-23590 > URL: https://issues.apache.org/jira/browse/AMBARI-23590 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When registering an mpack, if the mpack has already been registered, the > server returns a 409. However, we also need the server to return the same > data that it returns when the mpack is initially registered (most > importantly, the registered mpack ID). This is required so that we can have > the UI behave the same way – the operation needs to appear idempotent, even > if the response code is a 409. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23590) Return mpack info even when attempting to register duplicate mpack
[ https://issues.apache.org/jira/browse/AMBARI-23590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-23590: --- Status: Patch Available (was: In Progress) > Return mpack info even when attempting to register duplicate mpack > -- > > Key: AMBARI-23590 > URL: https://issues.apache.org/jira/browse/AMBARI-23590 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > When registering an mpack, if the mpack has already been registered, the > server returns a 409. However, we also need the server to return the same > data that it returns when the mpack is initially registered (most > importantly, the registered mpack ID). This is required so that we can have > the UI behave the same way – the operation needs to appear idempotent, even > if the response code is a 409. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23590) Return mpack info even when attempting to register duplicate mpack
[ https://issues.apache.org/jira/browse/AMBARI-23590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23590: Labels: pull-request-available (was: ) > Return mpack info even when attempting to register duplicate mpack > -- > > Key: AMBARI-23590 > URL: https://issues.apache.org/jira/browse/AMBARI-23590 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > When registering an mpack, if the mpack has already been registered, the > server returns a 409. However, we also need the server to return the same > data that it returns when the mpack is initially registered (most > importantly, the registered mpack ID). This is required so that we can have > the UI behave the same way – the operation needs to appear idempotent, even > if the response code is a 409. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
