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/pull/4461#issuecomment-741928992,https://api.github.com/repos/pydata/xarray/issues/4461,741928992,MDEyOklzc3VlQ29tbWVudDc0MTkyODk5Mg==,1217238,2020-12-09T17:37:01Z,2020-12-09T17:37:01Z,MEMBER,"We are excited about adding this feature! We love fsspec and think this would be very useful for xarray's users. In the long term, we would love to support fsspec for all the file formats that can handle file objects, e.g., including `engine='h5netcdf'` and `engine='scipy'`.

The concern right now is that this adds special case logic for zarr in open_dataset(), which @alexamici and @aurghs are presently (simultaneously!) trying to remove as part of paying down technical debt in the ongoing backends refactor.

I see two potential paths forwards:

1. Merge this as is. It has good test coverage and porting should (hopefully!) be relatively straightforward to port.
2. Insert this into the new backend API code instead, and require using the v2 backend API instead for this feature.

@alexamici could you please take a look and weigh in here? In particular, it would be helpful if you could point to where this would belong in the new refactor. This is also a good motivation for deleting the ""v1"" API code as soon as possible in favor of the ""v2"" code -- nothing is worse than needing to implement a new feature twice!","{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 1, ""rocket"": 0, ""eyes"": 0}",,709187212