-
Notifications
You must be signed in to change notification settings - Fork 494
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
feat:(core): add content encoding
to Opwrite
#5390
Conversation
content encoding
to Opwrite
81850af
to
92d93a0
Compare
Yes, please do this! |
core/tests/behavior/async_write.rs
Outdated
.content_encoding(target_content_encoding) | ||
.await?; | ||
|
||
// TODO: check the content encoding in the stat op response? |
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.
We can merge the PR which adds content-encoding in meta first.
92d93a0
to
a39a7f2
Compare
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.
Thank you, nice change!
Thank you for the updates! 🥰 |
Which issue does this PR close?
Closes #5378
I think we need to add
content_encoding
to the metadata to properly test it? https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html#API_HeadObject_ResponseSyntaxAre there any user-facing changes?
Add
op.write_with(path, content).content_encoding("encoding")