fsspec / fsspec/filesystem_spec
caching location to be non-local
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 490
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 38
Description
Proposal to have the target location for file caching to be something other than the local filesystem, e.g., a scratch bucket for initial copy of a dataset from one cloud platform to another.
In parallel, the same_names=True parameter should be changed to allow a certain number of parent filenames to be stored as part of the cached file name.
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 Python caching implementation and the same_names=True parameter, then trace how cache paths and parent filenames are currently handled. Clarify the supported non-local cache target and parent-depth behavior; the work is done when both caching scenarios have defined behavior and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100