Update docs to reflect open_mfdataset default chunk behaviour #10567
+4
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking at #5704 and #9038 (and various other issues that reference these), it seems like there's no easy solution and the current
open_mfdataset
chunk default is going to stay for a while. i.e.chunks=None
as a kwarg toopen_mfdataset
is overwritten withchunks={}
before callingopen_dataset
, so the default chunks are disk chunks not single-file chunks.xarray/xarray/backends/api.py
Line 1677 in 5ce69b2
In which case, we should probably update the docs to reflect this current behaviour.