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
Currently cubed doesn't allow to specify the credentials of a storage file system to Spec class. Although the class allows to pass some storage_options, these are actually never used.
This is a limitation since when working with S3-compatible storage system such as minIO the user should be able to specify credentials.
The solution could come from:
Specifying credentials and addtional configuration parameters to Spec:
Wrapping the store path with specs storage_options when creating the temp_store and the target_store. e.g. in rechunk
iftarget_storeisNone:
target_store=new_temp_path(name=name, spec=spec) # return not only path, but also store argumentsname_int=f"{name}-int"temp_store=new_temp_path(name=name_int, spec=spec) # return not only path, but also store arguments
Before calling zarr.open_array, checking if self.store is just a string or a string packed with additional arguments. If that is the case create a S3 compatible storage class as:
Currently cubed doesn't allow to specify the credentials of a storage file system to
Spec
class. Although the class allows to pass somestorage_options
, these are actually never used.This is a limitation since when working with S3-compatible storage system such as minIO the user should be able to specify credentials.
The solution could come from:
self.store
is just a string or a string packed with additional arguments. If that is the case create a S3 compatible storage class as:As accessing a MinIO server from zarr, for instance, is done by:
The text was updated successfully, but these errors were encountered: