home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 837243943

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
837243943 MDExOlB1bGxSZXF1ZXN0NTk3NjA4NTg0 5065 Zarr chunking fixes 1197350 closed 0     32 2021-03-22T01:35:22Z 2021-04-26T16:37:43Z 2021-04-26T16:37:43Z MEMBER   0 pydata/xarray/pulls/5065
  • [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.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5065/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    13221727 pull

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 32 rows from issue in issue_comments
Powered by Datasette · Queries took 0.738ms · About: xarray-datasette