issue_comments

Table actions

4 rows where issue = 345354038 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

author_association 2

issue 1

  • znetcdf: h5netcdf analog for zarr? · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
650656215 https://github.com/pydata/xarray/issues/2323#issuecomment-650656215 https://api.github.com/repos/pydata/xarray/issues/2323 MDEyOklzc3VlQ29tbWVudDY1MDY1NjIxNQ== stale[bot] 26384082 2020-06-28T00:32:22Z 2020-06-28T00:32:22Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   znetcdf: h5netcdf analog for zarr?  345354038
408639375 https://github.com/pydata/xarray/issues/2323#issuecomment-408639375 https://api.github.com/repos/pydata/xarray/issues/2323 MDEyOklzc3VlQ29tbWVudDQwODYzOTM3NQ== shoyer 1217238 2018-07-28T22:40:51Z 2018-07-28T22:40:51Z MEMBER

if we a znetcdf library like h5netcdf we could get mf_dataset "for free" though, right?

We would still need an adapter layer in xarray, although it could be a little smaller.

Basically, we would need to make open_zarr() a special case of open_dataset(). In principle, I think this is totally doable, though there are a few options for open_dataset that we haven't ported over to open_zarr yet (e.g., caching).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   znetcdf: h5netcdf analog for zarr?  345354038
408606913 https://github.com/pydata/xarray/issues/2323#issuecomment-408606913 https://api.github.com/repos/pydata/xarray/issues/2323 MDEyOklzc3VlQ29tbWVudDQwODYwNjkxMw== rsignell-usgs 1872600 2018-07-28T13:07:39Z 2018-07-28T13:07:39Z NONE

@shoyer, if we a znetcdf library like h5netcdf we could get mf_dataset "for free" though, right?
Zarr definitely has more and different compression options than NetCDF -- does that make this concept problematic?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   znetcdf: h5netcdf analog for zarr?  345354038
408546582 https://github.com/pydata/xarray/issues/2323#issuecomment-408546582 https://api.github.com/repos/pydata/xarray/issues/2323 MDEyOklzc3VlQ29tbWVudDQwODU0NjU4Mg== shoyer 1217238 2018-07-27T21:45:57Z 2018-07-27T21:45:57Z MEMBER

z5 is the name of another library that reads/writes zarr files, so let's not copy that: https://github.com/constantinpape/z5 😀

We could indeed work on getting zarr support in open_mfdataset, but that's really independent of factoring out zarr/netCDF support into a separate project. I don't recall off hand why zarr has the separate function for opening it -- it may have something to do with using different decoders than netCDF files. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   znetcdf: h5netcdf analog for zarr?  345354038

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);