issue_comments

Table actions

1 row where issue = 688640232 and user = 1053153 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

  • chrisroat · 1 ✖

issue 1

  • Stack: avoid re-chunking (dask) and insert new coordinates arbitrarily · 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
685173725 https://github.com/pydata/xarray/issues/4389#issuecomment-685173725 https://api.github.com/repos/pydata/xarray/issues/4389 MDEyOklzc3VlQ29tbWVudDY4NTE3MzcyNQ== chrisroat 1053153 2020-09-01T22:46:02Z 2020-09-01T22:46:02Z CONTRIBUTOR

There has been some discussion on the dask chunking issue here: https://github.com/dask/dask/issues/3650 https://github.com/dask/dask/issues/5544

Regarding the position of the inserted variable, it is not related to the chunking. It seems possible to do this. Would this be an acceptable change? If so, the first problem is the signature, as multiple dimensions may be passed in. :/

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Stack: avoid re-chunking (dask) and insert new coordinates arbitrarily 688640232

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