issue_comments: 370884840

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/1970#issuecomment-370884840 https://api.github.com/repos/pydata/xarray/issues/1970 370884840 MDEyOklzc3VlQ29tbWVudDM3MDg4NDg0MA== 1217238 2018-03-06T18:43:10Z 2020-06-09T01:20:04Z MEMBER

Backend needs that have changed since I drafted an API refactor in https://github.com/pydata/xarray/pull/1087: - pickle support, required to support backends with dask distributed - caching for managing open files, required for efficiently loading data from multiple files at once (see file_manager.py) - locking, required for threadsafe operations. Note that xarray backends are only threadsafe after files are opened, not during open_dataset (https://github.com/pydata/xarray/issues/4100). - support for array indexing modes, required for supporting various forms of indexing in xarray - customized conventions for encoding/decoding data (e.g., required for zarr)

It would be nice to figure out how to abstract away these details from backend authors as much as possible. Most of the ingredients for these features exist in xarray.backends (e.g., see CachingFileManager), but the lack of a clean-separation between internal and public APIs makes it hard to write backends outside of xarray.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   302806158