issue_comments

Table actions

1 row where author_association = "NONE", issue = 607229563 and user = 59711987 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

  • chfite · 1 ✖

issue 1

  • Can Resample dim be spatial and not just datetime? · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
620018834 https://github.com/pydata/xarray/issues/4008#issuecomment-620018834 https://api.github.com/repos/pydata/xarray/issues/4008 MDEyOklzc3VlQ29tbWVudDYyMDAxODgzNA== chfite 59711987 2020-04-27T14:21:20Z 2020-04-27T14:21:20Z NONE

Thanks @dcherian for the input. coarsen looks like it would help me in what I'm doing some, but yeah having to specify "index space" is not as ideal in some cases. In theory it would be nice if in resample I could provide it the new coords I want it resampled to or something, similar to how you can feed new coords into interp. Then I guess it would be able to use those coordinates and groupby_bins under the hood to get the coarsened result? How feasible is it for someone with more xarray knowledge than myself to make this change?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can Resample dim be spatial and not just datetime? 607229563

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