issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 106068129 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

issue 1

  • Resampling followed by to_array().values · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
139646912 https://github.com/pydata/xarray/issues/572#issuecomment-139646912 https://api.github.com/repos/pydata/xarray/issues/572 MDEyOklzc3VlQ29tbWVudDEzOTY0NjkxMg== shoyer 1217238 2015-09-11T19:54:31Z 2015-09-11T19:54:31Z MEMBER

When you use open_mfdataset, the data is loaded with dask and all computation is lazy. That means that the resampling doesn't happen until you actually look at the data or call .values on the line below.

If the data is small enough that it fits into memory, one thing you could do is to call .load() before doing the resample. Then the computation will be done on all NumPy arrays, which can be faster in some circumstances.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Resampling followed by to_array().values 106068129

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