issue_comments

Table actions

1 row where issue = 102703065 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • jhamman · 1 ✖

issue 1

  • Support for netcdf4/hdf5 compression · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
134256961 https://github.com/pydata/xarray/issues/548#issuecomment-134256961 https://api.github.com/repos/pydata/xarray/issues/548 MDEyOklzc3VlQ29tbWVudDEzNDI1Njk2MQ== jhamman 2443309 2015-08-24T15:47:15Z 2015-08-24T15:47:15Z MEMBER

I don't see any reason why we couldn't support this. The difficulty is that the implementation will be different (or not possible) for difficult backends.

netCDF4 adds compression at the Variable level so we would have to think about how to implement this to our Dataset.to_netcdf method. Would we end up setting the compression level / type in each DataArray or would we add an argument to the to_netcdf method?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Support for netcdf4/hdf5 compression 102703065

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]);