SaketaChalamchala commented on PR #5533: URL: https://github.com/apache/ozone/pull/5533#issuecomment-1792652028
> Can we throw error at the beginning of the operation itself for FSO bucket instead failing in the middle of the operation and show the error? There is no was to know on S3 gateway if the delete requests for keys are a part of the force delete operation. From S3G perspective we receive individual requests for deleting keys and then a request to delete the bucket at the end. So, there might not be a way to identify the top of the operation. ``` $ aws s3 --endpoint http://0.0.0.0:9878 rb --force s3://bucket1 # GET Request 0 is list all keys in the bucket # DELETE Request 1 delete: s3://bucket1/dir1/dir2/dir3/ ### fails because /dir1/dir2/dir3/ is not empty # DELETE Request 2 delete: s3://bucket1/dir1/ ### fails because /dir1/ is not empty # DELETE Request 3 delete: s3://bucket1/dir1/dir2/dir3/key1 ### succeeds # DELETE Request 4 delete: s3://bucket1/dir1/dir2/ ### fails because /dir1/dir2/ is not empty # DELETE Request 5 is delete: s3://bucket1 remove_bucket failed: s3://bucket1 An error occurred (BucketNotEmpty) when calling the DeleteBucket operation: The bucket you tried to delete is not empty. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
