issue_comments

Table actions

1 row where issue = 839914235 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • dcherian · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
806009190 https://github.com/pydata/xarray/issues/5071#issuecomment-806009190 https://api.github.com/repos/pydata/xarray/issues/5071 MDEyOklzc3VlQ29tbWVudDgwNjAwOTE5MA== dcherian 2448579 2021-03-24T17:16:58Z 2021-03-24T17:16:58Z MEMBER

Yes there is no way of knowing that your function only needs "foo" and not "air". The actual function is totally opaque to map_blocks so it provides your whole dataset.

Can you send a PR improving the docs on this point?

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Applying a function on a subset of variables using `map_blocks` is much slower 839914235

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