Allow track_order to be passed to h5netcdf
Open
Nobody has claimed this yet.
enhancement
topic-backends
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
when using h5netcdf as a backend. Writing the same exact content to two different files results in unique md5 checksum for the two identical xarray files.
See https://github.com/h5netcdf/h5netcdf/issues/211
Describe the solution you'd like
When saving an nc file. allow track_order=False to be passed as an arg
Describe alternatives you've considered
using netcdf4 engine
Additional context
No response
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
No file or test is named in the issue. Start by tracing how xarray passes save arguments to the h5netcdf backend, then reproduce writing identical content with and without track_order=False. Done means track_order=False can be supplied when saving through h5netcdf and identical files produce matching checksums.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100