I have the same issue.
I have a large file that I cannot access from an MLFlow service.
Things I have tried (none of these work):
- Read-only from DBFS
- `dbfs:/myfolder/myfile.chroma` does not work
- `/dbfs/myfolder/myfile.chroma` does not work
- Read-only from Unity Catalog Volume
- `/Volumes/mycatalog/mydb/myfolder/myfile.chroma` does not work
- Read-only from S3 storage
- `s3://mybucket/mydb/myfolder/myfile.chroma` does not work
So far, the only thing that works is parking the huge file as MLFlow artifact and accessing it locally in the service (awful).
The errors are all similar to:
`ValueError: Dataset at path Volumes/non_prod/metrics/files/recommender/embed-db.chroma was not found`
Notice that the path strips the leading `/` from `/Volumes/` and does the same with `s3://` protocol, etc.
I can't use MLFlow endpoints without this very basic functionality.