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

Zarr backend follow-up: tech #6119

Closed
5 of 7 tasks
fm3 opened this issue Mar 22, 2022 · 2 comments
Closed
5 of 7 tasks

Zarr backend follow-up: tech #6119

fm3 opened this issue Mar 22, 2022 · 2 comments

Comments

@fm3
Copy link
Member

fm3 commented Mar 22, 2022

Follow-up for reading zarr-datasets in wk backend:

  • cache clear for datavaults (when password for an account changes or the data vault breaks for some reason)
  • double-check that fill value is used if chunk does not exist
  • support string-encoded fill values
  • perf: async cache, for file systems, handles – use akka-caching (caution: Futures all around, needs actorSystem)
  • do not depend on jzarr, instead on its dependencies itself (only those we use) Do not depend on jzarr, use jblosc, ucarCdm directly #6152
  • where to store file systems / file system provider ref
  • perf optimization: skip allocating buffer if single-bucket request
@fm3
Copy link
Member Author

fm3 commented Apr 26, 2022

I’d say with #6152 and #6165 the two most important parts of this issue are taken care of. Let’s schedule it again when we feel that the other checkboxes are relevant enough :)

@fm3 fm3 removed their assignment Apr 26, 2022
@normanrz normanrz added the zarr label May 17, 2022
@fm3 fm3 mentioned this issue Aug 5, 2022
33 tasks
@fm3
Copy link
Member Author

fm3 commented Apr 18, 2023

I split the remaining parts of this issue into #6989 and #6990

@fm3 fm3 closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants