fsspec / fsspec/filesystem_spec
Use mv_file instead of copy + rm to implement mv
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 490
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 38
Description
As discussed in https://github.com/fsspec/gcsfs/pull/800#discussion_r3041091240, we can consider using mv_file to implement mv method. We might see performance gains if some fsspec implementations include atomic mv_file like we see in case of GCSFS.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the filesystem specification's mv method and its current copy-plus-rm implementation, then read the linked gcsfs pull request discussion about using mv_file. Check how mv_file is defined and used across implementations. Done means mv uses the shared operation where appropriate, preserves existing behavior, and has coverage for the changed path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100