issue_comments

Table actions

1 row where issue = 461088361 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • Assign attributes to DataArrays when creating dataset with PydapDataStore + subsetting · 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
506218086 https://github.com/pydata/xarray/issues/3047#issuecomment-506218086 https://api.github.com/repos/pydata/xarray/issues/3047 MDEyOklzc3VlQ29tbWVudDUwNjIxODA4Ng== shoyer 1217238 2019-06-27T06:56:18Z 2019-06-27T06:56:18Z MEMBER

This is likely an issue with pydap, or possibly with the DAP server. Xarray doesn't have any special logic for handling DAP URLs of any particular form. They just get passed directly on to PyDAP (or netCDF4-Python).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Assign attributes to DataArrays when creating dataset with PydapDataStore + subsetting 461088361

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