issue_comments

Table actions

1 row where issue = 1318369110 and user = 34276374 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

  • tbloch1 · 1 ✖

issue 1

  • xarray.DataArray.str.cat() doesn't work on chunked data · 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
1196410247 https://github.com/pydata/xarray/issues/6828#issuecomment-1196410247 https://api.github.com/repos/pydata/xarray/issues/6828 IC_kwDOAMm_X85HT8WH tbloch1 34276374 2022-07-27T08:19:28Z 2022-07-27T08:19:28Z NONE

Thanks for the workaround @mathause!

Is there a benefit to your approach, rather than calling compute() on each DataArray? It seems like calling compute() twice is faster for the MVCE example (but maybe it won't scale that way).

But either way, it would be nice if the function threw a warning/error for handling dask arrays!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray.DataArray.str.cat() doesn't work on chunked data 1318369110

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