issue_comments

Table actions

1 row where author_association = "NONE", issue = 467771094 and user = 29253833 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

  • zbruick · 1 ✖

issue 1

  • Allow GRIB data as an example dataset · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
511157664 https://github.com/pydata/xarray/issues/3118#issuecomment-511157664 https://api.github.com/repos/pydata/xarray/issues/3118 MDEyOklzc3VlQ29tbWVudDUxMTE1NzY2NA== zbruick 29253833 2019-07-13T22:16:47Z 2019-07-13T22:16:47Z NONE

And I would think support for .zarr and .hdf files may also be useful at some point down the road. While there are many ugly ways to do this, the cleanest way that @StephanSiemen and myself have thought of is to make load_dataset as general as possible, which would break the current examples by requiring the full file name, including the extension in load_dataset. Thoughts on this? @rabernat 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow GRIB data as an example dataset 467771094

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