issue_comments
1 row where issue = 231715344 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- changes made to coords using groupby and apply do not persist · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 605654288 | https://github.com/pydata/xarray/issues/1428#issuecomment-605654288 | https://api.github.com/repos/pydata/xarray/issues/1428 | MDEyOklzc3VlQ29tbWVudDYwNTY1NDI4OA== | keewis 14808389 | 2020-03-29T15:28:52Z | 2020-03-29T15:28:52Z | MEMBER | This is a special case for a coordinate along the groupby dimension: since for each group the groupby dimension coordinate is a scalar, it is not treated as a dimension. This means If we'd want to do something about that, I guess we'd need to modify the concatenation code to know about the groupby dimension and its coords? As a workaround, we can modify the original coord (note the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
changes made to coords using groupby and apply do not persist 231715344 |
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