Azure / Azure/MachineLearningNotebooks

`azureml-fsspec` file upload uninformative error

Open
#1,902 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
4.4k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

Hey, I am working on some simple EDA in AzureML, and I have successfully set up data asset to facilitate access to blob storage. Following [this documentation](https://learn.microsoft.com/en-us/azure/machine-learning/how-to-access-data-interactive?view=azureml-api-2&tabs=adls#access-data-from-a-datastore-uri-like-a-filesystem), I can easily read data using a number of methods, including creating an `AzureMachineLearningFileSystem` and using it to `.open()` some remote file. However, when I try uploading a file back to blob storage using an instance of `AzureMachineLearningFileSystem` and its `.upload()` method, it just fails with an error message mentioning the remote path I pass to it.

So, given a file system `fs`, local file `local.file.txt`, which I want to upload as `remote.file.txt`, I run the following (based on the sample [here](https://learn.microsoft.com/en-us/azure/machine-learning/how-to-access-data-interactive?view=azureml-api-2&tabs=adls#upload-files-via-azuremachinelearningfilesystem)):
```python
fs.upload(lpath='local.file.txt', rpath='remote.file.txt', recursive=False, **{'overwrite': 'MERGE_WITH_OVERWRITE'})
```
But it results in an error with a lengthy stack trace, ending with:
```
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/site-packages/azureml/fsspec/spec.py:146, in AzureMachineLearningFileSystem._info(self, path)
144 if len(self._stream_infos) == 1:
145 return list(self._stream_infos.values())[0]['info']
--> 146 return self._stream_infos[path]['info']

KeyError: 'remote.file.txt'
```
which is not really helpful. Any advice on how to debug this issue?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.