-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
S3 api CopyObject unexpected behavior if the source file does not exist #2306
Comments
Added a fix. But The return http status code is set to 400 (Bad Request). Please help to verify it. |
@chrislusf Thanks for fast response.
I think the absence of the file does not cause the error. Checking for missing file does not work. |
Hello @chrislusf I have 4 filer and the metadata is stored in Mysql Galera cluster. After updating to 2.66, I noticed that there are more tables in the database than before. The table names correspond to the files that were created when using the copyObject API. There is nothing inside the table. I think the fix is f62df7f will close this problem We need to release the next release as soon as possible. Dbeaver |
We have updated the version to 2.67 and have tested a CopyObject command Answer:
It seems to work correctly |
Thanks for the update! |
Hello
Describe the bug
S3 has a CopyObject command that lets you create a duplicate file.
Minio returns a 404 error if there is no source file, the target file is not created.
But, seaweedfs creates an empty target file
System Setup
version 30GB 2.65 cd838b1 linux amd64
Expected behavior
Returns a 404 error if there is no source file
Additional context
We are using AWS SDK for Java.
Sample code
The text was updated successfully, but these errors were encountered: