issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 860180906 and user = 5821660 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

  • kmuehlbauer · 2 ✖

issue 1

  • Feature to retrieve the underlying store · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
821854599 https://github.com/pydata/xarray/issues/5175#issuecomment-821854599 https://api.github.com/repos/pydata/xarray/issues/5175 MDEyOklzc3VlQ29tbWVudDgyMTg1NDU5OQ== kmuehlbauer 5821660 2021-04-17T17:04:48Z 2021-04-17T17:04:48Z MEMBER

@skorper So, the workaround would be something along the lines:

```python

dataset = xr.open_dataset('/path/to/file.nc') nc_dataset = dataset._close.self.ds type(nc_dataset) <class 'netCDF4._netCDF4.Dataset'> ```

But note, this only works if the dataset was opened/created from a single source file. And I'm not sure, if this is wanted behaviour.

@alexamici can possibly answer your question, if such API would be possible. To my understanding the backend refactor also did a great deal to disentangle Datasets from the underlying data sources. Please correct me @alexamici, if I'm wrong. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature to retrieve the underlying store 860180906
821784136 https://github.com/pydata/xarray/issues/5175#issuecomment-821784136 https://api.github.com/repos/pydata/xarray/issues/5175 MDEyOklzc3VlQ29tbWVudDgyMTc4NDEzNg== kmuehlbauer 5821660 2021-04-17T07:49:41Z 2021-04-17T07:49:41Z MEMBER

AFAICT you could try to use ds._close to get the closing function(s) of the underlying file managers. Not sure if you then can lookup their parent-store(s) .

But you could open the store yourself, keep the reference and load it into a Dataset. Not sure if this would work for your use case, though. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature to retrieve the underlying store 860180906

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