issue_comments

Table actions

1 row where issue = 218315793 and user = 306380 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

  • mrocklin · 1 ✖

issue 1

  • Dask Persist · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
290539816 https://github.com/pydata/xarray/issues/1344#issuecomment-290539816 https://api.github.com/repos/pydata/xarray/issues/1344 MDEyOklzc3VlQ29tbWVudDI5MDUzOTgxNg== mrocklin 306380 2017-03-30T20:46:27Z 2017-03-30T20:46:27Z MEMBER

We do eventually want to support some sort of duck typing. This way people can do things like the following while still benefiting from shared intermediates:

x, y, z = dask.persist(my_df, my_arrray, my_xarray)

But this may not happen as quickly as a .persist method. Also we've added .persist to the Base dask collections class, so it's part of the standard dask API at this point.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dask Persist 218315793

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