issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 606165039 and user = 1197350 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

  • rabernat · 1 ✖

issue 1

  • Add hook to get progress of long-running operations · 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
619009819 https://github.com/pydata/xarray/issues/4000#issuecomment-619009819 https://api.github.com/repos/pydata/xarray/issues/4000 MDEyOklzc3VlQ29tbWVudDYxOTAwOTgxOQ== rabernat 1197350 2020-04-24T13:28:20Z 2020-04-24T13:28:52Z MEMBER

Whenever working with big data in xarray, the recommendation is to use dask, as @TomNicholas says.

It would be great if we could go directly from a dask.dataframe to an xarray dataset with dask arrays. Unfortunately this is not supported (yet): https://github.com/dask/dask/issues/6058

I believe our dev time would best be spent working on that integration, rather than building progress bars directly into xarray.

also see https://github.com/pydata/xarray/issues/3929

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add hook to get progress of long-running operations 606165039

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