issue_comments
2 rows where issue = 315381649 and user = 2444231 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- open_mfdataset can't handle many files · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
382430172 | https://github.com/pydata/xarray/issues/2066#issuecomment-382430172 | https://api.github.com/repos/pydata/xarray/issues/2066 | MDEyOklzc3VlQ29tbWVudDM4MjQzMDE3Mg== | pgierz 2444231 | 2018-04-18T15:35:15Z | 2018-04-18T15:35:15Z | NONE | I’d be happy taking a shot at contributing an error catch for that. I assume that wouldn’t be too difficult, right? On 18. Apr 2018, 15:21 +0200, Ryan Abernathey notifications@github.com, wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
open_mfdataset can't handle many files 315381649 | |
382330380 | https://github.com/pydata/xarray/issues/2066#issuecomment-382330380 | https://api.github.com/repos/pydata/xarray/issues/2066 | MDEyOklzc3VlQ29tbWVudDM4MjMzMDM4MA== | pgierz 2444231 | 2018-04-18T09:47:49Z | 2018-04-18T09:47:49Z | NONE | That seemed to do the trick. Would it be worthwhile to consider putting the default value of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
open_mfdataset can't handle many files 315381649 |
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