issue_comments
2 rows where issue = 1646267547 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- open_mfdataset very slow · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1489341690 | https://github.com/pydata/xarray/issues/7697#issuecomment-1489341690 | https://api.github.com/repos/pydata/xarray/issues/7697 | IC_kwDOAMm_X85YxYz6 | dcherian 2448579 | 2023-03-29T21:20:59Z | 2023-03-29T21:20:59Z | MEMBER |
we still construct a dataset representation for each file which involves reading all coordinates etc. The consistency checking is bypassed at the "concatenation" stage. You could also speed using dask by setting up a cluster and using |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
open_mfdataset very slow 1646267547 | |
| 1489302292 | https://github.com/pydata/xarray/issues/7697#issuecomment-1489302292 | https://api.github.com/repos/pydata/xarray/issues/7697 | IC_kwDOAMm_X85YxPMU | dcherian 2448579 | 2023-03-29T20:53:37Z | 2023-03-29T20:53:37Z | MEMBER | Fundamentally, xarray has to touch every file because there is no guarantee they are consistent with each other. A number of us now use kerchunk to create virtual aggregate datasets that can be read a lot faster. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
open_mfdataset very slow 1646267547 |
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