-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support putifabsent #8428
support putifabsent #8428
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, added 2 important comments.
pkg/gateway/errors/errors.go
Outdated
ErrObjectExists: { | ||
Code: "ErrObjectExists", | ||
Description: "Object path already exists in DB", | ||
HTTPStatusCode: http.StatusNotModified, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The correct error is PreconditionFailed with status code 412 (StatusPreconditionFailed).
As for the description, the exact AWS message is:
At least one of the pre-conditions you specified did not hold
let's stick to what AWS returns.
pkg/gateway/operations/putobject.go
Outdated
@@ -298,6 +298,11 @@ func handlePut(w http.ResponseWriter, req *http.Request, o *PathOperation) { | |||
o.Incr("put_object", o.Principal, o.Repository.Name, o.Reference) | |||
storageClass := StorageClassFromHeader(req.Header) | |||
opts := block.PutOpts{StorageClass: storageClass} | |||
err := o.checkIfAbsent(req) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This intention is right but not the approach.
In the current version the function checkIfAbsent
implements checkIfAbsent
by doing Get to the object and then Put. This is not gonna work because the Get->Put operation is not atomic.
The idea of the feature is that AWS implements this and provide atomicity out of the box.
Instead, our S3 Gateway should only forward the request to AWS and let them handle the precondition check.
Example implementation:
- add additional field to
opts := block.PutOpts{StorageClass: storageClass, IfNoneMatch}
(one line above) that check if the header exist and sets it. - let the ops propagate down to the blockstore adapter and then use it when calling PutObject as an option. We have a challenge here see below 👇 .
Challenge with PutObject call:
Our AWS SDK is outdated, so it does not contain the built-in option in the new version IfNoneMatch.
We have 2 options:
a. Upgrade the AWS SDK (preferable) after verifying there no breaking changes (separate PR)
b. Use the request middleware options that the current AWS SDK version provides to propagate the header.
- in AWS SDK introduces in service/s3/v1.60.0
NOTE: Same should apply for Multipart Uploads
pkg/gateway/operations/putobject.go
Outdated
@@ -325,3 +338,20 @@ func handlePut(w http.ResponseWriter, req *http.Request, o *PathOperation) { | |||
o.SetHeader(w, "ETag", httputil.ETag(blob.Checksum)) | |||
w.WriteHeader(http.StatusOK) | |||
} | |||
|
|||
func (o *PathOperation) checkIfAbsent(req *http.Request) (bool, error) { | |||
Header := req.Header.Get(IfNoneMatchHeader) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Use lowercase for variable names
- Be explicit in variable name
Header := req.Header.Get(IfNoneMatchHeader) | |
headerValue := req.Header.Get(IfNoneMatchHeader) |
pkg/gateway/operations/putobject.go
Outdated
@@ -298,6 +298,15 @@ func handlePut(w http.ResponseWriter, req *http.Request, o *PathOperation) { | |||
o.Incr("put_object", o.Principal, o.Repository.Name, o.Reference) | |||
storageClass := StorageClassFromHeader(req.Header) | |||
opts := block.PutOpts{StorageClass: storageClass} | |||
allowOverWrite, err := o.checkIfAbsent(req) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For future generations, please add comment explaining this, something or exactly like this otherwise it's confusing, since this does not actually the verify core part, it's more optimization (since not atomicity here)
pkg/gateway/operations/putobject.go
Outdated
@@ -298,6 +298,15 @@ func handlePut(w http.ResponseWriter, req *http.Request, o *PathOperation) { | |||
o.Incr("put_object", o.Principal, o.Repository.Name, o.Reference) | |||
storageClass := StorageClassFromHeader(req.Header) | |||
opts := block.PutOpts{StorageClass: storageClass} | |||
allowOverWrite, err := o.checkIfAbsent(req) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
allowOverWrite, err := o.checkIfAbsent(req) | |
allowOverwrite, err := o.checkIfAbsent(req) |
esti/s3_gateway_test.go
Outdated
{Path: "main/object1", Content: "data", IfNoneMatch: "", ExpectError: false}, | ||
{Path: "main/object1", Content: "data", IfNoneMatch: "", ExpectError: false}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both lines seems redundant, any other intention here? or just delete one?
esti/s3_gateway_test.go
Outdated
Key: aws.String(tc.Path), | ||
Body: strings.NewReader(tc.Content), | ||
} | ||
logger.Info("Sending PutObject request for Path: %s with If-None-Match: %s\n", tc.Path, tc.IfNoneMatch) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need in log message here, especially not at Info
level, but really no need at all.
if PutObject
fails you'll see in the require
assertion, if it doesn't - we don't care about the log then.
We try to avoid it as much as possible because in the context of the CI, all tests run together and there are TONS of logs.
esti/multipart_test.go
Outdated
@@ -166,7 +166,7 @@ func reverse(s string) string { | |||
return string(runes) | |||
} | |||
|
|||
func uploadMultipartParts(t *testing.T, ctx context.Context, logger logging.Logger, resp *s3.CreateMultipartUploadOutput, parts [][]byte, firstIndex int) []types.CompletedPart { | |||
func uploadMultipartParts(t *testing.T, ctx context.Context, svc *s3.Client, logger logging.Logger, resp *s3.CreateMultipartUploadOutput, parts [][]byte, firstIndex int) []types.CompletedPart { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason here to override the global svc
and pass here a custom client svc *s3.Client
?
(Even if required please don't use the same name as the global svc
since it's confusing)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The override is so i can use that func, since my test doesn't use that global client
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Added small comments nothing big - looks very good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!! 🥳 🥳 🥳
Closes #8380
Change Description
Added support for if-none-match header.
The header can be used for putObject or complete-multipart-upload operations.
changes were tested manually. In case of a collision an error with http status 304 will return, as in aws cli.