issue_comments

Table actions

1 row where issue = 320838184 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

  • Avoiding duplicate time coordinates when opening multiple files · 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
387549048 https://github.com/pydata/xarray/issues/2108#issuecomment-387549048 https://api.github.com/repos/pydata/xarray/issues/2108 MDEyOklzc3VlQ29tbWVudDM4NzU0OTA0OA== shoyer 1217238 2018-05-08T21:31:58Z 2018-05-08T21:31:58Z MEMBER

The pandas duplicated() method might be more convenient than using np.unique(), e.g., you could equivalently write: arr.sel(time=~arr.indexes['time'].duplicated())

I think we would be open to adding duplicated() to xarray, too, if you or someone else is interested in making a pull request.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Avoiding duplicate time coordinates when opening multiple files 320838184

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