issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 181017850 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
251534952 https://github.com/pydata/xarray/issues/1037#issuecomment-251534952 https://api.github.com/repos/pydata/xarray/issues/1037 MDEyOklzc3VlQ29tbWVudDI1MTUzNDk1Mg== shoyer 1217238 2016-10-04T22:42:42Z 2016-10-04T22:42:42Z MEMBER

This was certainly not an intentional change, but on the other hand, the original behavior was not tested or intentionally specified, either.

It would be good to figure out where in open_mfdataset/auto_concat the attributes are lost.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   attrs empty for open_mfdataset vs population for open_dataset 181017850

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