issue_comments
5 rows where author_association = "MEMBER", issue = 168272291 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- WIP: progress toward making groupby work with multiple arguments · 5 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 371672217 | https://github.com/pydata/xarray/pull/924#issuecomment-371672217 | https://api.github.com/repos/pydata/xarray/issues/924 | MDEyOklzc3VlQ29tbWVudDM3MTY3MjIxNw== | shoyer 1217238 | 2018-03-09T00:27:32Z | 2018-03-09T00:27:32Z | MEMBER | @pwolfram Personally, I am waiting to implement this until after https://github.com/pydata/xarray/issues/1603. I'm pretty sure that the alternative model for indexes proposed there will make this far easier to implement. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
WIP: progress toward making groupby work with multiple arguments 168272291 | |
| 286517390 | https://github.com/pydata/xarray/pull/924#issuecomment-286517390 | https://api.github.com/repos/pydata/xarray/issues/924 | MDEyOklzc3VlQ29tbWVudDI4NjUxNzM5MA== | shoyer 1217238 | 2017-03-14T18:31:12Z | 2017-03-14T18:31:12Z | MEMBER | I don't have any progress to report since my last comment. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
WIP: progress toward making groupby work with multiple arguments 168272291 | |
| 280441902 | https://github.com/pydata/xarray/pull/924#issuecomment-280441902 | https://api.github.com/repos/pydata/xarray/issues/924 | MDEyOklzc3VlQ29tbWVudDI4MDQ0MTkwMg== | shoyer 1217238 | 2017-02-16T20:00:44Z | 2017-02-16T20:00:44Z | MEMBER | @RafalSkolasinski Sure, here is the current list:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
WIP: progress toward making groupby work with multiple arguments 168272291 | |
| 279100389 | https://github.com/pydata/xarray/pull/924#issuecomment-279100389 | https://api.github.com/repos/pydata/xarray/issues/924 | MDEyOklzc3VlQ29tbWVudDI3OTEwMDM4OQ== | shoyer 1217238 | 2017-02-11T00:08:18Z | 2017-02-11T00:08:18Z | MEMBER | @RafalSkolasinski This pull request was mostly working, but still needs some significant work to clean it up and update it to the current version of the codebase. I don't think anyone is working on it currently (I'm not) but I'm sure someone will get to it eventually. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
WIP: progress toward making groupby work with multiple arguments 168272291 | |
| 236402472 | https://github.com/pydata/xarray/pull/924#issuecomment-236402472 | https://api.github.com/repos/pydata/xarray/issues/924 | MDEyOklzc3VlQ29tbWVudDIzNjQwMjQ3Mg== | shoyer 1217238 | 2016-07-31T01:49:15Z | 2016-07-31T01:49:15Z | MEMBER | @rabernat I updated the top post with examples. So yes, for your example, the coordinates of the output would have every unique combination of Once we figure out squeezing out grouped/stacked dimensions (not quite working yet), this will let us write things like |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
WIP: progress toward making groupby work with multiple arguments 168272291 |
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 1