issue_comments
4 rows where author_association = "NONE" and issue = 58117200 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Support multi-dimensional grouped operations and group_over · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
781427391 | https://github.com/pydata/xarray/issues/324#issuecomment-781427391 | https://api.github.com/repos/pydata/xarray/issues/324 | MDEyOklzc3VlQ29tbWVudDc4MTQyNzM5MQ== | matthiasdemuzere 6926916 | 2021-02-18T15:33:06Z | 2021-02-18T15:33:06Z | NONE | still relevant, also for me ... I just wanted to group by half hours, for which I'd need access to |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support multi-dimensional grouped operations and group_over 58117200 | |
531937119 | https://github.com/pydata/xarray/issues/324#issuecomment-531937119 | https://api.github.com/repos/pydata/xarray/issues/324 | MDEyOklzc3VlQ29tbWVudDUzMTkzNzExOQ== | stale[bot] 26384082 | 2019-09-16T20:08:04Z | 2019-09-16T20:08:04Z | NONE | In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here or remove the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support multi-dimensional grouped operations and group_over 58117200 | |
336925565 | https://github.com/pydata/xarray/issues/324#issuecomment-336925565 | https://api.github.com/repos/pydata/xarray/issues/324 | MDEyOklzc3VlQ29tbWVudDMzNjkyNTU2NQ== | jjpr-mit 25231875 | 2017-10-16T15:35:06Z | 2017-10-16T15:35:06Z | NONE | Is use case 1 (Multiple groupby arguments along a single dimension) being held back for use case 2 (Multiple groupby arguments along different dimensions)? Use case 1 would be very useful by itself. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support multi-dimensional grouped operations and group_over 58117200 | |
265462343 | https://github.com/pydata/xarray/issues/324#issuecomment-265462343 | https://api.github.com/repos/pydata/xarray/issues/324 | MDEyOklzc3VlQ29tbWVudDI2NTQ2MjM0Mw== | hottwaj 5629061 | 2016-12-07T14:35:01Z | 2016-12-07T14:35:01Z | NONE | In case it is of interest to anyone, the snippet below is a temporary and quite dirty solution I've used to do a multi-dimensional groupby... It runs nested groupby-apply operations over each given dimension until no further grouping needs to be done, then applies the given function "apply_fn"
Obviously performance can potentially be quite poor. Passing the dimensions to group over in order of increasing length will reduce your cost a little. |
{ "total_count": 3, "+1": 3, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support multi-dimensional grouped operations and group_over 58117200 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 4