`write_empty_chunks` not in `DataArray.to_zarr`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
What is your issue?
Our to_zarr methods on DataArray & Dataset are slightly inconsistent — Dataset.to_zarr has write_empty_chunks and chunkmanager_store_kwargs. They're also in a different order.
Up a level — not sure of the best way of enforcing consistency here; a couple of ideas.
- We could have tests that operate on both a
DataArrayandDataset, parameterized by fixtures (might also help reduce the duplication in some of our tests), though we then need to make the tests generic. We could have some general tests which just test that methods work, and then delegate to the current per-object tests for finer guarantees. - We could have a tool which collects the differences between
DataArray&Datasetmethods and snapshots them — then we'll see if they diverge, while allowing for some divergences.
Contributor guide
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
Compare the DataArray.to_zarr and Dataset.to_zarr method definitions, focusing on write_empty_chunks, chunkmanager_store_kwargs, and argument order. Read the existing tests for both methods and determine whether the requested parity is the full scope or whether a generic consistency check is intended. Done means the two APIs are consistently defined and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100