issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 1188965542 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • keewis · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1085589487 https://github.com/pydata/xarray/issues/6433#issuecomment-1085589487 https://api.github.com/repos/pydata/xarray/issues/6433 IC_kwDOAMm_X85AtMfv keewis 14808389 2022-04-01T08:21:36Z 2022-04-01T09:19:14Z MEMBER

parallel=True will open (read the metadata) and preprocess the datasets in parallel using dask, which will happen in sequence with parallel=False. The difference is roughly: python if parallel: datasets, = dask.compute([dask.delayed(xr.open_dataset)(path, *args, **kwargs) for path in paths]) else: datasets = [xr.open_dataset(path, *args, **kwargs) for path in paths] So unlike load_dataset / the proposed load_mfdataset this will read metadata but not the actual data, and the result should be the same regardless of the parallel parameter (if it doesn't that would be a bug).

I agree that we could improve the parameter description, though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Rename/reword `parallel=True` option to `open_mfdataset` 1188965542

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);