Skip to content

Releases: google/xarray-beam

v0.10.1

30 Sep 22:49

Choose a tag to compare

Update xarray version in docs build

PiperOrigin-RevId: 813456305

v0.10.0

30 Sep 19:38

Choose a tag to compare

Add docs for xbeam.Dataset

PiperOrigin-RevId: 813378676

v0.9.3

23 Sep 19:30

Choose a tag to compare

Update xarray_beam version to 0.9.3.

PiperOrigin-RevId: 810535844

v0.9.2

12 Sep 19:45

Choose a tag to compare

Expose encoding parameter in ChunksToZarr.

PiperOrigin-RevId: 806388507

v0.9.1

10 Sep 07:10

Choose a tag to compare

Adds option to specify zarr format version to ChunksToZarr

This allows users to specify the desired Zarr format version (2 or 3) when writing datasets using `xarray_beam`. The default behavior remains unchanged, allowing the underlying zarr library to determine the format.

PiperOrigin-RevId: 805225875

v0.9.0

08 Sep 19:45

Choose a tag to compare

Vendor rechunker.algorithm inside xarray-beam

Rechunker is deprecated and no longer maintained:
https://github.com/pangeo-data/rechunker/issues/160

In particular, it pins zarr=2, but we need to support zarr v3 in xarray-beam.

PiperOrigin-RevId: 804545298

v0.8.1

08 Sep 19:04

Choose a tag to compare

Switch Xarray-Beam packaging to pyproject.toml

This is the modern alternative to setup.py.

PiperOrigin-RevId: 804528285

0.8.0: Add xarray_beam.replace_template_dims

23 Apr 17:37

Choose a tag to compare

PiperOrigin-RevId: 750350345

0.7.0: Add a warning when using xarray_beam.ChunksToZarr with no template

18 Feb 21:45

Choose a tag to compare

If this works well at some point in the future (e.g., using zarr v3), we can always remove the warning. But for now, this is better than letting users run directly into the race condition in https://github.com/google/xarray-beam/issues/85

I've also removed all suggestions from the docs of omitting a `template`.

PiperOrigin-RevId: 728341864

release version 0.6.3

01 Dec 18:58

Choose a tag to compare

PiperOrigin-RevId: 587056902