idea: referencefilesystem as a way to prepend to zarr
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 366
- Forks
- 96
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This is not really a kerchunk process, but if you wanted to extend a zarr dataset by prepending chunks to it, you would currently write the new files and be forced to rename all the other chunks, as well as update the metadata - which would change how it looked to other users.
However, with our system, the new could files could be written with different names (or even "-1" negative names) and then construct a new view containing the new prepended chunks without changing the original dataset at all.
cc @jakirkham
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
The issue mentions referencefilesystem, zarr datasets, chunks, and metadata, but names no files, tests, or entry points. Start by locating the relevant referencefilesystem and zarr-handling code, then determine how a prepended view could preserve the original dataset; done would require a concrete, agreed design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100