Skip to content

Support multiple zarr backends + abstraction #15

Open
@balbasty

Description

@balbasty

I feel like it would be good to have an option to switch between zarr/zarrita/tensorstore for the zarr i/o, as they all have pros and cons and this would enable benchmarking each of them.

The most useful think would probably to abstract away the few features that we actually use (opening/writing a group, opening/writing/slicing an array), and wrap each of the libraries in classes that inherit from this AbstractZarrIO class.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions