issue_comments

Table actions

2 rows where issue = 236595831 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • xarray.Dataset from existing netCDF4.Dataset · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
309170633 https://github.com/pydata/xarray/issues/1459#issuecomment-309170633 https://api.github.com/repos/pydata/xarray/issues/1459 MDEyOklzc3VlQ29tbWVudDMwOTE3MDYzMw== shoyer 1217238 2017-06-17T00:08:20Z 2017-06-17T00:08:20Z MEMBER

We could add an alternative constructor to NetCDF4DataStore. This would work fine in most cases, with one exception: attempting to pickle the data store would fail. But as long as you mention that downside (relevant for using dask distributed) I'd be fine with this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray.Dataset from existing netCDF4.Dataset 236595831
309135182 https://github.com/pydata/xarray/issues/1459#issuecomment-309135182 https://api.github.com/repos/pydata/xarray/issues/1459 MDEyOklzc3VlQ29tbWVudDMwOTEzNTE4Mg== fmaussion 10050469 2017-06-16T21:11:24Z 2017-06-16T21:11:24Z MEMBER

I needed this too and proposed a change which wasn't accepted a while ago: https://github.com/pydata/xarray/pull/1060 (the PR topic changed in the meantime, so it's hard to follow).

I am still using the same quite ugly solution. I have a shallow subclass of NetCDF4DataStore which I then feed to open_dataset... 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray.Dataset from existing netCDF4.Dataset 236595831

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