issue_comments

Table actions

1 row where issue = 161068483 and user = 1217238 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • shoyer · 1 ✖

issue 1

  • Perf: use Scipy engine by default for netcdf3? · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
227042249 https://github.com/pydata/xarray/issues/887#issuecomment-227042249 https://api.github.com/repos/pydata/xarray/issues/887 MDEyOklzc3VlQ29tbWVudDIyNzA0MjI0OQ== shoyer 1217238 2016-06-20T03:14:09Z 2016-06-20T03:14:09Z MEMBER

Yes, I have found this to be true in my experience, as well. The scipy backend also works more smoothly when using multiple threads with dask, because it releases the GIL.

I would be happy to accept a patch that adds this as the default behavior. We would need to detect netCDF3 vs netCDF4 files automatically when doing file reading by looking at the first few bytes from the file. See these docs for file format specs, which include the necessary details: https://www.hdfgroup.org/HDF5/doc/H5.format.html#Superblock http://www.unidata.ucar.edu/software/netcdf/docs/file_format_specifications.html

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Perf: use Scipy engine by default for netcdf3? 161068483

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