issue_comments

Table actions

where issue = 212646769 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
285492492 https://github.com/pydata/xarray/issues/1302#issuecomment-285492492 https://api.github.com/repos/pydata/xarray/issues/1302 MDEyOklzc3VlQ29tbWVudDI4NTQ5MjQ5Mg== shoyer 1217238 2017-03-09T21:41:50Z 2017-03-09T21:41:50Z MEMBER

Does it work to load one of these single datasets completely into memory, e.g., by calling .load()?

There might be a general issue with loading the "lat" variable that only appears with open_mfdataset because it does the check explicitly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opening multiple OpenDAP paths with open_mfdataset fails 212646769

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