issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 778069594 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • dcherian · 1 ✖

issue 1

  • WIP: testing.assert_* check dtype · 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
754142883 https://github.com/pydata/xarray/pull/4760#issuecomment-754142883 https://api.github.com/repos/pydata/xarray/issues/4760 MDEyOklzc3VlQ29tbWVudDc1NDE0Mjg4Mw== dcherian 2448579 2021-01-04T18:36:52Z 2021-01-04T18:36:52Z MEMBER

sometimes dask can get the dtype wrong before the compute (see below)

I suspect this is only for object arrays since you need not get back an object array? Maybe check in lazy_array_equiv only if all dtypes are not object

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   WIP: testing.assert_* check dtype 778069594

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