Update docs to reflect open_mfdataset default chunk behaviour#10567
Update docs to reflect open_mfdataset default chunk behaviour#10567keewis merged 3 commits intopydata:mainfrom
Conversation
|
Thank you for opening this pull request! It may take us a few days to respond here, so thank you for being patient. |
for more information, see https://pre-commit.ci
|
@dcherian would you mind taking a quick look at this for me? |
|
I would expect the Edit: all CI passes! |
|
Thanks! Anything else I should do here, or am I just waiting for someone to check the docstring update is correct and merge? |
|
Thanks for the ping, @jemmajeffree, this completely fell off my radar I'll go ahead and merge since this is such a small change |
* main: Update docs to reflect open_mfdataset default chunk behaviour (pydata#10567)
Looking at #5704 and #9038 (and various other issues that reference these), it seems like there's no easy solution and the current
open_mfdatasetchunk default is going to stay for a while. i.e.chunks=Noneas a kwarg toopen_mfdatasetis 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.