Bug #3613
Change conflict handling in object write
| Status: | Resolved | Start date: | 04/18/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Sofia Papagiannaki | % Done: | 0% |
|
| Category: | Pithos | Spent time: | - | |
| Target version: | - |
Description
Pithos in case of missing blocks during smart object write
(using hashmap) used to raise an api fault with payload
the list with the missing blocks serialized in json format.
However, the common api_method decorator in case of api fault
returns a different response content format containing details about
the fault.
This causes problem to pithos clients which expect
a specific response content format in that case.
History
#1 Updated by Sofia Papagiannaki about 11 years ago
The solution was adopted is:
when pithos server detects such a case returns directly
an HttpResponse with the same status code (409) as before
and the expected content.
#2 Updated by Sofia Papagiannaki about 11 years ago
- Status changed from Assigned to Resolved