-
Notifications
You must be signed in to change notification settings - Fork 761
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
deps: Bump to OpenDAL v0.4 #4678
Conversation
Signed-off-by: Xuanwo <[email protected]>
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/databend/databend/J8b129EDBSxKdjgHoSBR3kXpHeai [Deployment for 6656f45 canceled] |
Thanks for the contribution! Please review the labels and make any necessary changes. |
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
In this PR, I also fix some clippy warnings around benches. The most interesting one:
It seems our CI doesn't cover benches code. Ask @everpcpc for verification. Locally, I use |
yes, we only run it seems came from e264ce4#diff-99b87178e201388c0ebfd7d8584c9f6930100d335919c10b7399b39a88cb0c03R27 we'd better change to |
Checking one question with this PR:
The bucket path:
Why the response status is But I have try a COPY command it returns 404(This is the expected):
|
Client:
Server error log:
Error code line: |
Fixed in 6656f45 And to this error, can you try using the same credential to send a HEAD request to the same object (take version/tenant prefix into consideration) For example: aws s3api head-object --bucket=bucket --key=prefix/to/fuse/1/5/_ss/8878969040bd4d7aa5d28297cff1f321
|
Thank you for your useful information, have a try and response is 403:
And i have check an exists key:
|
Signed-off-by: Xuanwo <[email protected]>
Do you have set output type for aws? Please checkout your With the same command: :( aws s3api head-object --bucket=databend-shared --key=fuse/1/1/_ss/92318ff55f694b51b59f119a7c39eda8_v1.json
{
"AcceptRanges": "bytes",
"LastModified": "Wed, 30 Mar 2022 07:36:55 GMT",
"ContentLength": 19254,
"ETag": "\"d1308468d48c4d8e5572e4f66f3665b8\"",
"VersionId": "KtVbGRhs8apEOin2ZNsa5T44bciFfupD",
"ContentType": "binary/octet-stream",
"Metadata": {}
}
:) aws s3api head-object --bucket=databend-shared --key=fuse/1/1/_ss/92318ff55f694b51b59f119a7c39eda8_v1.jsonx
An error occurred (403) when calling the HeadObject operation: Forbidden |
For a quick workaround, specify aws s3api head-object --bucket=databend-shared --key=fuse/1/1/_ss/92318ff55f694b51b59f119a7c39eda8_v1.json --output=json |
Works:
The not exists path head-object returns 403:
|
It seems an expected behavior of AWS S3: https://stackoverflow.com/questions/19037664/how-do-i-have-an-s3-bucket-return-404-instead-of-403-for-a-key-that-does-not-e
|
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.
looks great to me
Signed-off-by: Xuanwo [email protected]
I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
This PR will bump OpenDAL to v0.4, read v0.4.0 release note to know more.
For databend, this PR will address the following problems:
Changelog
Test Plan
Unit Tests
Stateless Tests