id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
221387277,MDU6SXNzdWUyMjEzODcyNzc=,1372,decode_cf() loads chunked arrays,4992424,closed,0,,,7,2017-04-12T20:52:48Z,2018-04-12T23:38:02Z,2018-04-12T23:38:02Z,NONE,,,,"Currently using xarray version 0.9.2 and dask version 0.14.0.

Suppose you load a NetCDF file with the **chunks** parameter:

``` python
ds = xr.open_dataset(""my_data.nc"", decode_cf=False, chunks={'lon': 10, 'lat': 10})
```

The data is loaded as dask arrays, as expected. But if we then manually call `xarray.decode_cf()`, it'll eagerly load the data. Is this the expected behavior, or should `decode_cf()` preserve the laziness of the data?","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1372/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue
121740837,MDU6SXNzdWUxMjE3NDA4Mzc=,678,Save to netCDF with record dimension?,4992424,closed,0,,,6,2015-12-11T16:20:35Z,2018-01-08T20:11:27Z,2018-01-08T20:11:27Z,NONE,,,,"Is it currently possible in xray to identify a coordinate as a record dimension when saving to netCDF? Saving a Dataset to disk - even when it's a Dataset that was directly read in from a netCDF file with a record dimension - seems to destroy any indication that there was a record dimension. For instance, reading in CESM output tapes and then immediately saving them to disk demotes ""time"" from being a record dimension. 
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/678/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue