html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/5175#issuecomment-830746640,https://api.github.com/repos/pydata/xarray/issues/5175,830746640,MDEyOklzc3VlQ29tbWVudDgzMDc0NjY0MA==,1217238,2021-05-02T05:34:35Z,2021-05-02T05:34:35Z,MEMBER,"@skorper Could you kindly explain your use-case here? Why it is useful for you to retrieve underlying stores? :)

This has never been part of Xarray's supported public API, and unless that changes the present work-around could break again in the future without warning.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,860180906
https://github.com/pydata/xarray/issues/5175#issuecomment-822377249,https://api.github.com/repos/pydata/xarray/issues/5175,822377249,MDEyOklzc3VlQ29tbWVudDgyMjM3NzI0OQ==,226037,2021-04-19T10:56:01Z,2021-04-19T10:56:01Z,MEMBER,"@kmuehlbauer precisely. For example the `AbstractDataStore` is not part of the API anymore and it is kept only for backward compatibility.

What I see missing is a way defined at API level for the backends to ""attach"" arbitrary information and possibly code to the backend `Dataset`s. cc @shoyer @jhamman ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,860180906
https://github.com/pydata/xarray/issues/5175#issuecomment-822142644,https://api.github.com/repos/pydata/xarray/issues/5175,822142644,MDEyOklzc3VlQ29tbWVudDgyMjE0MjY0NA==,11022336,2021-04-19T03:34:38Z,2021-04-19T03:34:38Z,NONE,Thanks @kmuehlbauer! That works great for now. ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,860180906
https://github.com/pydata/xarray/issues/5175#issuecomment-821854599,https://api.github.com/repos/pydata/xarray/issues/5175,821854599,MDEyOklzc3VlQ29tbWVudDgyMTg1NDU5OQ==,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}",,860180906
https://github.com/pydata/xarray/issues/5175#issuecomment-821784136,https://api.github.com/repos/pydata/xarray/issues/5175,821784136,MDEyOklzc3VlQ29tbWVudDgyMTc4NDEzNg==,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}",,860180906