inconsistent-error-format

Bug #1373955 reported by Dmitriy Ukhlov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Fix Released
Medium
Dmitriy Ukhlov

Bug Description

Error details returned from REST API as part of http response body have
more than one format.
FORMAT 1:
----------
{
explanation: "The resource could not be found."
code: 404
-error:
{ message: "Table 'resources111' does not exist" traceback: null type: "TableNotExistsException" }
title: "Not Found"
}
In some cases we also get error response in following format
FORMAT 2
----------
{"__type":"com.amazonaws.dynamodb.v20111205#ResourceInUseException","message":"T he resource which you are attempting to change is in use."}
It would be good to have all errors returned in same consistent format.

Dmitriy Ukhlov (dukhlov)
Changed in magnetodb:
assignee: nobody → Dmitriy Ukhlov (dukhlov)
Changed in magnetodb:
status: New → In Progress
Dmitriy Ukhlov (dukhlov)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnetodb (master)

Reviewed: https://review.openstack.org/123458
Committed: https://git.openstack.org/cgit/stackforge/magnetodb/commit/?id=c04e846720923f4661c945119be70036f5bf3847
Submitter: Jenkins
Branch: master

commit c04e846720923f4661c945119be70036f5bf3847
Author: Dmitriy Ukhlov <email address hidden>
Date: Tue Sep 23 17:40:40 2014 +0300

    Fix error handling

    In some cases our code throws Amazon DynamoDB specific
    exceptions even we work with REST API.

    Closes-bug: #1373955

    Change-Id: I253e9d4287fb8ab5e5604df7ba00b99b37920409

Changed in magnetodb:
status: In Progress → Fix Committed
Changed in magnetodb:
importance: Undecided → Medium
milestone: none → kilo-2
Changed in magnetodb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.