-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
400 Error when using FileClient.Delete() with ApiVersion[2023-08-03] and OAuth in Storage Datalake SDK #37869
Comments
Thank you for your feedback. This has been routed to the support team for assistance. |
The paginated and recursive query parameters do not apply to file delete - https://learn.microsoft.com/en-us/rest/api/storageservices/datalakestoragegen2/path/delete |
Hi, Sean. You can easily reproduce this 400 error by using following code:
And you can get the following error:
|
And another thing is that the
The The code line: This can cause the value of paginated to be set incorrectly when Delete(). |
Adding Service team to look into this |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sumantmehtams. |
This was fixed with #37934 |
The 2nd issue was fixed with #38083 |
Library name and version
Azure.Storage.Files.Datalake.12.16.0.alpha.20230726.1
Describe the bug
In the latest source code of Storage Datalake SDK, when using
FileClient.Delete()
with ApiVersion2023-08-03
andOAuth
, the query parameter of the request should bepaginated=true&recursive=false
. This combination produces a 400 error no matter if the resourceType is file or directory.Expected behavior
Return success instead of 400 error.
Actual behavior
Return HttpStatusCode
400
with message: A query parameter that's mandatory for this request is not specified.Reproduction Steps
2023-08-03
andOAuth
There is also a x-ms-reuqest-id about this issue to search server log: c2e472e5-101f-0047-3430-c026fb000000
Environment
Visual Studio 2022
The text was updated successfully, but these errors were encountered: