issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 195050684 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

  • Generated Dask graph is huge - performance issue? · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
274605239 https://github.com/pydata/xarray/issues/1161#issuecomment-274605239 https://api.github.com/repos/pydata/xarray/issues/1161 MDEyOklzc3VlQ29tbWVudDI3NDYwNTIzOQ== shoyer 1217238 2017-01-23T20:21:14Z 2017-01-23T20:21:14Z MEMBER

Fixed by #1162 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generated Dask graph is huge - performance issue? 195050684
266588337 https://github.com/pydata/xarray/issues/1161#issuecomment-266588337 https://api.github.com/repos/pydata/xarray/issues/1161 MDEyOklzc3VlQ29tbWVudDI2NjU4ODMzNw== shoyer 1217238 2016-12-12T23:34:41Z 2016-12-12T23:34:41Z MEMBER

I'm thinking I might but together a draft PR for comments

Yes, please do -- that's much easier to read and comment on than what you have here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generated Dask graph is huge - performance issue? 195050684
266526859 https://github.com/pydata/xarray/issues/1161#issuecomment-266526859 https://api.github.com/repos/pydata/xarray/issues/1161 MDEyOklzc3VlQ29tbWVudDI2NjUyNjg1OQ== shoyer 1217238 2016-12-12T19:27:28Z 2016-12-12T19:27:28Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generated Dask graph is huge - performance issue? 195050684
266517317 https://github.com/pydata/xarray/issues/1161#issuecomment-266517317 https://api.github.com/repos/pydata/xarray/issues/1161 MDEyOklzc3VlQ29tbWVudDI2NjUxNzMxNw== shoyer 1217238 2016-12-12T18:52:35Z 2016-12-12T18:52:35Z MEMBER

Indeed, sel_points currently uses a very inefficient implementation -- it indexes each point and then concatenates them together.

Could be worth experimenting with dask.array.Array.vindex to make a more scalable version: https://github.com/dask/dask/pull/439

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generated Dask graph is huge - performance issue? 195050684

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