issue_comments: 745393893
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/3476#issuecomment-745393893 | https://api.github.com/repos/pydata/xarray/issues/3476 | 745393893 | MDEyOklzc3VlQ29tbWVudDc0NTM5Mzg5Mw== | 13301940 | 2020-12-15T16:11:39Z | 2020-12-15T16:11:39Z | MEMBER |
Indeed. And it appears that these lines are the culprits:
Zarr appears to be ignoring the filter information from xarray. Zarr proceeds to extracting its own filter. As a result, we end up with two filters:
As @borispf and @jsadler2 suggested, clearing the filters from encoding before initiating the zarr store creation works:
@jhamman since you are more familiar with the internals of zarr + xarray, should we default to ignoring filter information from xarray and let zarr take care of the extraction of filter information? |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
516306758 |