[#22] Update system attributes #22
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-http-gw#22
Loading…
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-http-gw:feature/update_system_attributes"
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?
WIP: feature/update_system_attributesto WIP: [#22] Update system attributesa047da7207
to7c769638a0
7c769638a0
to8d81913674
WIP: [#22] Update system attributesto [#22] Update system attributes@ -445,2 +442,2 @@
3. `X-Attribute-Neofs-Expiration-Timestamp: 1637574797`
4. `X-Attribute-Neofs-Expiration-RFC3339: 2021-11-22T09:55:49Z`
There are some reserved headers type of `X-Attribute-SYSTEM-*` (headers are arranged in descending order of priority):
1. `X-Attribute-Frostfs-Expiration-Epoch: 100`
Should be
system
and notfrostfs?
8d81913674
toc0284c2505
@ -14,3 +14,3 @@
)
var frostfsAttributeHeaderPrefixes = [...][]byte{[]byte("Neofs-"), []byte("NEOFS-"), []byte("neofs-")}
var frostfsAttributeHeaderPrefixes = [...][]byte{[]byte("System-"), []byte("SYSTEM-"), []byte("system-")}
Do we want to keep compatibility with deprecated prefixes for couple of releases?
/cc @TrueCloudLab/storage-services-committers
After TrueCloudLab/frostfs-s3-gw#67 and TrueCloudLab/frostfs-sdk-go#40 I think we have to support compatibility there for a couple releases.
/cc @dkirillov
c0284c2505
to296f3d3c66
296f3d3c66
to5ad6738de9
5ad6738de9
toc10a34ea87
c10a34ea87
to8dc3e88276
8dc3e88276
to9fd705ef41
9fd705ef41
to399eab9671
@ -447,2 +446,3 @@
4. `X-Attribute-System-Expiration-RFC3339: 2021-11-22T09:55:49Z`
which transforms to `X-Attribute-Neofs-Expiration-Epoch`. So you can provide expiration any convenient way.
which transforms to `X-Attribute-Frostfs-Expiration-Epoch`. So you can provide expiration any convenient way.
transforms to
X-Attribute-System-Expiration-Epoch
@ -409,2 +410,3 @@
domain.SetName(testContainerName)
container.WriteDomain(&cnr, domain)
// currently in aio node know nothing about new sys attributes
Maybe todo and link with #2?
@ -120,28 +113,20 @@ func (u *Uploader) Upload(c *fasthttp.RequestCtx) {
response.Error(c, err.Error(), fasthttp.StatusBadRequest)
return
}
if needParseExpiration(filtered) {
This check is basically moved into
PrepareExpirationHeader
, right?Yes
399eab9671
to81f7168a16