issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 331752926 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

issue 1

  • fix zarr chunking bug · 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
396822353 https://github.com/pydata/xarray/pull/2228#issuecomment-396822353 https://api.github.com/repos/pydata/xarray/issues/2228 MDEyOklzc3VlQ29tbWVudDM5NjgyMjM1Mw== jhamman 2443309 2018-06-13T05:56:27Z 2018-06-13T05:56:27Z MEMBER

Eventually we want to think about supporting what I called the "hard case" at the end of _determine_zarr_chunks. But that is probably not urgent.

Yes, we'll get to it. @martindurant, in dask's to_zarr method, did you implement writing to zarr arrays with misaligned chunks (i.e. dask's chunks are not a 1:1 mapping to zarr chunks)?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   fix zarr chunking bug 331752926

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