pizzarr

Releases

5

Needs compilation

No

Needs R

>= 4.2

Config/testthat/edition

3

Config/testthat/parallel

false

Language

en-US

RoxygenNote

7.3.3

• High-dimensional statistics

Since March 2026

• jsonlite
• memoise
• qs2
• R6
• stats
• stringr
• utils

Installing it adds

17 packages, 19.7 MB of source

Of those, need compilation

13

• bench
• bit64
• blosc
• bslib
• covr
• crul
• knitr
• pkgdown
• rmarkdown
• testthat
• vcr
• withr

Lines by kind (33,599)

Lines by language

Languages are counted from file extensions.

Files

253

R functions

127

Object systems

S3: 4 methods, R6: 38 classes

Median

3

Mean

4.8

Highest

24

Median lines per function

10

R functions

127

Calls

164

Unconnected

31

Groups

3

Lines counted

3,132

Lines the tests ran

2,702

Tests passed

Yes

Measured with

covr 3.6.5 on R 4.6.1

Has tests

Yes

Test frameworks

testthat

Test cases

672

Lines of tests

14,954

Test lines per line of code

1.71

• Getting Started
• AnnData Stores
• Basics
• OME-NGFF Images
• R Session Info
• Reading Zarr V3
• Remote and Cloud Stores
• Zarr Operations Cookbook
• Zarr V3 Cross-Implementation Interop
• zarrs Backend

README

Yes, 1,115 words

Release notes file

Yes

Help pages

98

Lines of documentation

7,980

Commits

211

Open pull requests

1

Tagged releases

6

Latest tagged release

v0.2.1, 23 Sep 2026

In development

Default branch at 0.2.2, ahead of CRAN 0.2.1 (checked 2026-10-25)

Issues closed in

161 days (median)

Pull requests closed in

0 days (median)

Pull requests merged

94%

Created

1 Mar 2021

Licence file reads as

–

Method, repository practices

Across zarr-developers

Cloud storage

• New zarrs_get_key() reads a single key from any store the zarrs backend can open, returning raw bytes or NULL when the key is absent. Cloud stores delegate all I/O to object_store and expose no key-level read, so consolidated metadata (.zmetadata) was unreachable from R for an s3:// or gs:// URL. Reading that one key is enough to enumerate a store's arrays and recover their dimension names and attributes, which is what group-level inquiry over s3:// needs.

Cloud storage fixes

• S3 requests were always sent unsigned, so configured AWS credentials were ignored and private buckets returned 403. Signing is now decided from the environment: requests are unsigned when no credential source is present, so public buckets still work without configuration, and signed as soon as AWS_ACCESS_KEY_ID, AWS_SESSION_TOKEN, AWS_PROFILE, or another credential variable is set. AWS_SKIP_SIGNATURE forces either behaviour.
• zarr_open() on an s3:// or gs:// string fell through to DirectoryStore, which tried to create a directory named after the URL. These URLs now resolve to S3Store and GcsStore, and cloud stores default to read mode.
• S3Store and GcsStore inherited no-op get_item(), contains_item(), and listdir() methods that silently returned NULL. They now raise an error naming the supported read paths.
• HttpStore$listdir() took no arguments, so the path argument every other store accepts raised an error that callers swallowed --- ZarrGroup's print method reported No. members : 0 for every HTTP-backed group. It now accepts path and lists within it.

Documentation

• New vignettes/remote-stores.Rmd covering remote and cloud access: the mapping from fsspec/xarray storage_options to pizzarr's environment variables, the HTTPS and s3:// routes, alternate endpoints such as MinIO, Ceph, and Open Storage Network pods, and the current limits.
• Alternate S3 endpoints are configured with AWS_ENDPOINT; AWS_ALLOW_HTTP and AWS_VIRTUAL_HOSTED_STYLE_REQUEST cover plain-HTTP and path-style addressing. This worked before but was undocumented.
• Anonymous access to public GCS buckets over gs:// is documented, and now tested. It needs GOOGLE_SKIP_SIGNATURE=true, since GCS does not infer anonymous access from absent credentials the way S3 does.
• S3Store, GcsStore, and HttpStore gained detailed documentation of credentials, endpoints, and which distribution tier each requires.
• zarr_open()'s store argument now documents every accepted form: a path, an http(s):// URL, an s3:// or gs:// URL, or a Store object.
• zarr_open_group()'s storage_options argument is documented as ignored rather than as an fsspec passthrough.
• Vignettes reorganized around data conventions rather than transport, now that connection details have their own article. remote-ome-ngff.Rmd merged into ome-ngff.Rmd, which covers the OME-NGFF multiscales convention against both a local and a remote store; remote-anndata.Rmd renamed anndata.Rmd.
• The OME-NGFF and AnnData vignettes now evaluate their code at build time instead of showing static listings, so the examples are checked. Both require the blosc package and network access, and degrade to unevaluated when either is missing.
• README gained a "Remote and cloud data" section.