Introduce auxilliary request result
detail #8
Labels
No labels
P0
P1
P2
P3
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#33 Add response for partial object placement
TrueCloudLab/frostfs-api
Reference: TrueCloudLab/frostfs-api#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For GET operation we return a single status value. Currently most of the time
ObjectNotFound
is returned. While it is inevitable (we cannot be sure in anything in a distributed system), it may confuse CLI users and, especially, gateways where a response can be a single number (e.g. HTTP status).I have 3 goals in mind:
Non-goals:
The proposal is to introduce well-known detail "auxilliary request result". It's payload contains 4 fields:
For GET we can return
ObjectNotFound
together with all details then. In CLI each of them can be printed, but higher level applications can also use (3) to make a request to another node or convert it to a more suitable response.All fields except (2) are must have IMO, but we can start with implementing at least 1 and 4.