issue_comments

Table actions

2 rows where issue = 647804004 and user = 2448579 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

  • dcherian · 2 ✖

issue 1

  • Xarray open_mfdataset with engine Zarr · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
696783734 https://github.com/pydata/xarray/pull/4187#issuecomment-696783734 https://api.github.com/repos/pydata/xarray/issues/4187 MDEyOklzc3VlQ29tbWVudDY5Njc4MzczNA== dcherian 2448579 2020-09-22T15:08:36Z 2020-09-22T15:08:36Z MEMBER

Thanks @weiji14 and @Mikejmnez . This is a great contribution.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray open_mfdataset with engine Zarr 647804004
652482831 https://github.com/pydata/xarray/pull/4187#issuecomment-652482831 https://api.github.com/repos/pydata/xarray/issues/4187 MDEyOklzc3VlQ29tbWVudDY1MjQ4MjgzMQ== dcherian 2448579 2020-07-01T15:20:39Z 2020-07-01T15:20:39Z MEMBER

I wonder if it's really worth deprecating open_zarr(). open_dataset(..., engine='zarr') is a bit more verbose, especially with backend_kwargs to pass optional arguments. It seems pretty harmless to keep open_zarr() around, especially if it's just an alias for open_datraset(engine='zarr').

I agree. I think we should keep open_zarr around.

As reminder (because it took me a while to remember!), one goal with this refactor is to have open_mfdataset work with all backends (including zarr and rasterio) by specifying the engine kwarg.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray open_mfdataset with engine Zarr 647804004

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