ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajit Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15150) Support response body for DELETE API
Date Tue, 12 Apr 2016 23:47:25 GMT

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

Ajit Kumar updated AMBARI-15150:
--------------------------------
    Status: Patch Available  (was: Open)

> Support response body for DELETE API 
> -------------------------------------
>
>                 Key: AMBARI-15150
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15150
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Ajit Kumar
>            Assignee: Ajit Kumar
>             Fix For: 2.4.0
>
>         Attachments: rb43926.patch
>
>
> Currently DELETE API only returns status code and no body. This doesn't fit well in bulk
delete scenario as user needs to know which keys were deleted and which one failed and why.
For this, ResourceProvider needs to return metadata as part of RequestStatus object which
can be translated to metadata for Result object at API layer.
> At API layer, for all failed keys, reason code (like 404) is required which will make
scripting easy instead of just including error message as string.
> DELETE response json object should be 
> {code}
> deleteResult : [
>     deleted : {
>         key : <resource-key>
>     },
>    deleted : {
>         key : <resource-key>
>     },
>     ...
>     error: {
>         key : <resource-key>
>         code: 404
>         message: "Resource not found"
>    },
>    error: {
>         key : <resource-key>
>         code: 404
>         message: "Resource not found"
>    }
>    ...
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message