zarrs / zarrs/zarrs-python

memory storage

Open
#144 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
80
Forks
8
Avg merge
21h 44m
Merged PRs (30d)
5

Description

In the context of using a zarrs-backed codec pipeline on in-memory storage:

Don't think so since this package doesn't support that kind of store crossing into rust

Originally posted by @ilan-gold in https://github.com/zarrs/zarrs-python/pull/143#discussion_r2754011244

what would we need to change in zarr-python to enable this?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked discussion in pull request #143 and trace how zarr-python handles in-memory storage with the zarrs-backed codec pipeline. Determine what changes would let the store cross into Rust, and define completion as a working in-memory storage workflow with appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.