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
@caiostringari, sorry I missed your report! I agree, it would be good to give examples for other common datastores.
As you can see from the code, zappend passes target_storage_options directly to the underlying data store. Therefore the valid keyword arguments are prescribed by the specific fsspec filesystem implementation. Look here for Azure: https://github.com/fsspec/adlfs?tab=readme-ov-file#details
Activity
forman commentedon May 28, 2024
@caiostringari, sorry I missed your report! I agree, it would be good to give examples for other common datastores.
As you can see from the code,
zappendpassestarget_storage_optionsdirectly to the underlying data store. Therefore the valid keyword arguments are prescribed by the specificfsspecfilesystem implementation. Look here for Azure:https://github.com/fsspec/adlfs?tab=readme-ov-file#details
okz commentedon Jun 11, 2024
Hi, to add @forman's note, I don't think a
https://would correctly get decoded as an azure path.the following configuration patterns worked for me