You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both Neuroglancer Precomputed and Zarr (v3) can have sharded data formats. When served from a file server, range requests should be used to fetch only individual chunks out of the shards.
This needs to
understand the sharding metadata of the datasets to figure out byte offsets and lengths of the chunks to request
adapt the NIO file systems to support such partial reads
adapt the data reading code to use those partial reads (both in local and remote case)
Possibly related: https://stackoverflow.com/questions/35745403/java-how-to-read-part-of-file-from-specified-position-of-bytes
My assumption is that in the NIO implementation this will use SeekableByteChannel, which is implemented by the different NIO File System implementations. The HttpsFileSystem currently reads the whole file before returning a SeekableByteChannel, needs to be adapted to use http range requests. I don’t know how the S3 and GCS File System adapters behave.
The text was updated successfully, but these errors were encountered:
I think a good first step would be to adapt the https file system to also see how well the NIO api works with the range requests. Feel free to exchange the http library used there if needed (I think the one I plugged in there has been discontinued in the meantime)
Both Neuroglancer Precomputed and Zarr (v3) can have sharded data formats. When served from a file server, range requests should be used to fetch only individual chunks out of the shards.
This needs to
Possibly related:
https://stackoverflow.com/questions/35745403/java-how-to-read-part-of-file-from-specified-position-of-bytes
My assumption is that in the NIO implementation this will use SeekableByteChannel, which is implemented by the different NIO File System implementations. The HttpsFileSystem currently reads the whole file before returning a SeekableByteChannel, needs to be adapted to use http range requests. I don’t know how the S3 and GCS File System adapters behave.
The text was updated successfully, but these errors were encountered: