ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15150) Support response body for DELETE API
Date Fri, 15 Apr 2016 06:29:25 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242521#comment-15242521
] 

Hadoop QA commented on AMBARI-15150:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12798832/rb43926.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 7 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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.state.cluster.ClustersDeadlockTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6460//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6460//console

This message is automatically generated.

> Support response body for DELETE API 
> -------------------------------------
>
>                 Key: AMBARI-15150
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15150
>             Project: Ambari
>          Issue Type: Task
>          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