issue_comments

Table actions

1 row where issue = 1564661430 and user = 23487320 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

  • weiji14 · 1 ✖

issue 1

  • deprecate open_zarr · 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
1435869985 https://github.com/pydata/xarray/pull/7496#issuecomment-1435869985 https://api.github.com/repos/pydata/xarray/issues/7496 IC_kwDOAMm_X85VlaMh weiji14 23487320 2023-02-19T04:55:26Z 2023-02-19T04:55:26Z CONTRIBUTOR

The inconsistency in the chunks argument is non-ideal, but that could be handled by a separate deprecation process.

There was some discussion on whether xr.open_dataset should default to chunks=None, or switch to open_zarr's chunks="auto" at https://github.com/pydata/xarray/pull/4187#issuecomment-690885702 (the last attempt at deprecating open_zarr :slightly_smiling_face:). Just bringing it up for debate.

Also, quite a few people were in favour of keeping open_zarr back in 2020 (see e.g. https://github.com/pydata/xarray/pull/4187#issuecomment-652482831), but maybe times have changed, and a consistent API is more desirable than convenience?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_zarr 1564661430

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