issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 317114207 and user = 2443309 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

  • jhamman · 1 ✖

issue 1

  • No file error message using open_mfdataset · 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
383975935 https://github.com/pydata/xarray/issues/2077#issuecomment-383975935 https://api.github.com/repos/pydata/xarray/issues/2077 MDEyOklzc3VlQ29tbWVudDM4Mzk3NTkzNQ== jhamman 2443309 2018-04-24T15:30:24Z 2018-04-24T15:30:24Z MEMBER

Thanks for the report. Looking at open_mfdataset:

https://github.com/pydata/xarray/blob/99b457ce5859bd949cfea4671db5150c7297843a/xarray/backends/api.py#L558-L564

you'll see we are using glob to expand the path names. This is not likely to work for URLs. I'm not 100% sure if it is even possible to do a path expansion on OpenDAP datasets.

If you can do the expansion yourself, that would be the easiest workaround. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   No file error message using open_mfdataset 317114207

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