Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

split up metadata #7

Open
d70-t opened this issue May 20, 2022 · 0 comments
Open

split up metadata #7

d70-t opened this issue May 20, 2022 · 0 comments

Comments

@d70-t
Copy link
Owner

d70-t commented May 20, 2022

Currently the entire metadata tree is part of a single output object. Due to the 2MB size limit, this will quickly cause trouble for larger datasets. A natural approach would be to split the metadata object up into multiple objects based on the hierarchy inherent to zarr (e.g. one DAG-CBOR block per variable and dataset instead of only one object per dataset).

We might still need to resort to HAMT if the dictionaries on a single hierarchical level become too large, but that might still be quite far away. We probably might also want to introduce further hierarchical levels within the chunk keys of a single zarr variable as proposed here demonstrated here. This would reduce the number of items per dictionary while aligning IPLD objects to (to-be-introduced) zarr-shards, which in turn may lead to better locality within block requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant