Deprecate open_zarr in favor of open_dataset(..., engine='zarr') #7495

Activity

1. jhamman

   added

   needs triageIssue that has not been reviewed by xarray team memberIssue that has not been reviewed by xarray team member

   on Jan 31, 2023
2. dcherian

   added

   topic-backends

   needs triageIssue that has not been reviewed by xarray team memberIssue that has not been reviewed by xarray team member

   and removed

   needs triageIssue that has not been reviewed by xarray team memberIssue that has not been reviewed by xarray team member

   on Jan 31, 2023
3. TomNicholas

   added

   topic-zarrRelated to zarr storage libraryRelated to zarr storage library

   and removed

   needs triageIssue that has not been reviewed by xarray team memberIssue that has not been reviewed by xarray team member

   on Jan 31, 2023
4. keewis commented on Dec 12, 2023

   

   keewis

   on Dec 12, 2023

   Last edited by keewis

   Collaborator

   More actions

   To get back to this, I believe we should at least harmonize the meaning of the chunks parameter for both functions: open_zarr currently translates "auto" to {} if a chunk manager is available, or None otherwise, then forwards everything to open_dataset. open_dataset deals with None separately, but passes "auto" and dict values on to dask (with several translation layers in between), which means that open_dataset(..., chunks="auto") is not the same as open_zarr(..., chunks="auto").

   I believe we should aim to move the special-casing of "auto" to open_dataset while choosing a string that does not conflict with the chunks parameter for dask's rechunk.

   👍React with 👍3Reacted by Tom Nicholas, Joe Hamman and Maximilian Roos
5. jhamman commented on Dec 12, 2023

   

   jhamman

   on Dec 12, 2023

   MemberAuthor

   More actions

   👍 I have also come around to keeping open_zarr.

   Your plan around the chunks parameter seems quite reasonable.

   👍React with 👍1Reacted by Maximilian Roos
6. jhamman

   closed this as completedon Mar 20, 2025