issues: 295146502
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
295146502 | MDU6SXNzdWUyOTUxNDY1MDI= | 1894 | Zarr keys include variable name | 306380 | closed | 0 | 1 | 2018-02-07T13:56:32Z | 2018-02-17T04:40:15Z | 2018-02-17T04:40:15Z | MEMBER | When using open_zarr on a dataset with many variables the keynames include the variable name, like
In the distributed scheduler these keynames get shortened to prefixes like We may want to avoid including the variable name into the keyname here in order to avoid breaking these out into several groups. Instead you might consider putting the variable name within the key as another member of the tuple like the following:
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1894/reactions", "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |