pull_requests: 597608584
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 597608584 | MDExOlB1bGxSZXF1ZXN0NTk3NjA4NTg0 | 5065 | closed | 0 | Zarr chunking fixes | 1197350 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #2300, closes #5056 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` This PR contains two small, related updates to how Zarr chunks are handled. 1. We now delete the `encoding` attribute at the Variable level whenever `chunk` is called. The persistence of `chunk` encoding has been the source of lots of confusion (see #2300, #4046, #4380, https://github.com/dcs4cop/xcube/issues/347) 2. Added a new option called `safe_chunks` in `to_zarr` which allows for bypassing the requirement of the many-to-one relationship between Zarr chunks and Dask chunks (see #5056). Both these touch the internal logic for how chunks are handled, so I thought it was easiest to tackle them with a single PR. | 2021-03-22T01:35:22Z | 2021-04-26T16:37:43Z | 2021-04-26T16:37:43Z | 2021-04-26T16:37:42Z | dd7f742fd79126d8665740c5a461c265fdfdc0da | 0 | 023920b8d11d1a77bedfa880fcaf68f95167729c | 69950a46f9402a7c5ae6d86d766d7933738dc62b | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/5065 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests