Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rename Source Escaping #23831

Open
Bharat-Goyal opened this issue Dec 5, 2024 · 2 comments
Open

Rename Source Escaping #23831

Bharat-Goyal opened this issue Dec 5, 2024 · 2 comments
Assignees
@vibhansa-msft @tanyasethi-msft
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Data Lake

Comments

@Bharat-Goyal
Copy link

Bharat-Goyal commented Dec 5, 2024 •
edited
Loading

Bug Report

https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/storage/azdatalake/file/client.go#L243
The renameSource header needs to be URL encoded otherwise there is a 400 error.
If the rename source is something along the lines of dir1/lör 006.jpg, the error code returned
is along the lines of

--------------------------------------------------------------------------------
{
  "error": {
    "code": "InvalidSourceUri",
    "message": "The source URI is invalid.\nRequestId:13eb4511-801f-0061-0dcf-46d26c000000\nTime:2024-12-05T04:40:15.1863240Z"
  }
}

Package /sdk/storage/azdatalake
SDK version master
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 5, 2024
@jhendrixMSFT jhendrixMSFT added Data Lake Client This issue points to a problem in the data-plane of the library. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 5, 2024
@github-actions github-actions bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 5, 2024
@Bharat-Goyal
Copy link
Author

@tanyasethi-msft @vibhansa-msft any update on this? Is there any reason this behavior has been maintained on purpose or would this be something that can be fixed.

@tanyasethi-msft
Copy link
Member

Hi @Bharat-Goyal, thanks for reporting this! This seems like a bug in sdk and we will fix it before our next release in Jan 2025.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vibhansa-msft vibhansa-msft

@tanyasethi-msft tanyasethi-msft

Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Data Lake
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jhendrixMSFT @Bharat-Goyal @vibhansa-msft @tanyasethi-msft