issue_comments: 790088409
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/2300#issuecomment-790088409 | https://api.github.com/repos/pydata/xarray/issues/2300 | 790088409 | MDEyOklzc3VlQ29tbWVudDc5MDA4ODQwOQ== | 1197350 | 2021-03-03T21:55:44Z | 2021-03-03T21:55:44Z | MEMBER |
I would not favor that. A user may choose to define their desired zarr chunks by putting this information in encoding. In this case, it's good to raise the error. (This is the case I had in mind when I wrote this code.) The problem here is that encoding is often being carried over from the original dataset and persisted across operations that change chunk size. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
342531772 |