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

Implement index_location setting for Zarr3 Datasets #7553

Merged
merged 11 commits into from
Jan 22, 2024
Merged

Conversation

frcroth
Copy link
Member

@frcroth frcroth commented Jan 15, 2024

URL of deployed dev instance (used for testing):

  • https://___.webknossos.xyz

Steps to test:

  • Test datasets with permutations of the configuration options
    • With crc32c codec / without
    • index_location start / end

TODOs:

  • ...

Issues:


(Please delete unneeded items, merge only when none are left open)

  • Updated changelog
  • Needs datastore update after deployment

@frcroth frcroth requested a review from fm3 January 15, 2024 15:46
@frcroth frcroth requested a review from normanrz January 15, 2024 15:52
@@ -122,8 +119,22 @@ class Zarr3Array(vaultPath: VaultPath,
parsed = parseShardIndex(shardIndexRaw)
} yield parsed

private lazy val shardIndexChecksumLength =
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this works for most datasets, but not for all. Although, it doesn't make a lot of sense, it is spec-compliant to have multiple crc32c checksums. In the future, there might be other codecs that change the size of the shard index.

A more correct way would be to compute the size of the index based on the entire index_codecs pipeline. zarrita uses for that the compute_encoded_size methods.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least, there should be some assertions that only supported index configurations are usable.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@frcroth frcroth requested a review from fm3 January 22, 2024 10:38
@frcroth frcroth requested a review from fm3 January 22, 2024 10:54
@fm3
Copy link
Member

fm3 commented Jan 22, 2024

Approving this now based on normans previous feedback. @normanrz if you have other wishes, let’s add them as a follow-up issue :) that way this PR isn’t blocked

@frcroth frcroth merged commit 453cefe into master Jan 22, 2024
2 checks passed
@frcroth frcroth deleted the index-location branch January 22, 2024 12:53
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

Successfully merging this pull request may close these issues.

Implement zarr3 sharding index_location
3 participants