Lyndon1994 opened a new issue, #397:
URL: https://github.com/apache/arrow-rs-object-store/issues/397
## Bug Report
### What happened
When using `object_store` with `LocalFileSystem` on a blobfuse-mounted Azure
storage, file rename operations fail with "No such file or directory (os error
2)" when the source file path contains a hash fragment (`#`).
### Environment
- `object_store` version: 0.12.1
- Operating System: Linux (blobfusev2)
- Storage backend: Azure Blob Storage via blobfuse mount
- Related library: deltalake 1.0.1 (Python bindings)
### To Reproduce
1. Mount Azure Blob Storage using blobfuse
2. Attempt to rename a file with a path containing `#` character
3. The rename operation fails with `LocalFileSystem` error
### Expected behavior
File rename should succeed, or provide a more descriptive error message
indicating the issue with hash fragments in paths.
### Actual behavior
Generic LocalFileSystem error ↳ Unable to rename file ↳ No such file or
directory (os error 2)
### Additional context
This appears to be related to how blobfuse handles file paths with hash
fragments. The blobfuse logs show:
Failed request, request_id: status: 404 response:
{"error":{"code":"SourcePathNotFound","message":"The source path for a rename
operation does not exist."}}
The source path in the blobfuse log shows a `#1` suffix that seems to be
causing the issue:
src = /path/to/file.parquet#1
### Possible solutions
1. Add validation to reject file paths with hash fragments when using
`LocalFileSystem` with a clear error message
2. Escape or handle hash fragments properly in file paths
3. Provide better error messaging to indicate the specific issue with path
characters
### Related
- This issue is related to Delta Lake operations on Azure storage via
blobfuse mounts
- May be related to: https://github.com/apache/arrow-rs/pull/5094
This issue focuses on the core problem: the object_store LocalFileSystem
doesn't handle file paths with hash fragments properly when working with
blobfuse mounts, and provides insufficient error messaging to diagnose the
issue.
--
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]
