But when I test the connection I got error “The given path's format is not supported.”
Can you guys help me find the reason why? That would be much appreciated.
Page 1 / 1
Hi @Xiaoqing Hu
I have spent some more time explaining the different Data Lake options
Can you confirm that the file share is like this one?
If it is a blob container you should use azureblob:// or abfsss:// instead.
Hi @Xiaoqing Hu
I have spent some more time explaining the different Data Lake options
Can you confirm that the file share is like this one?
If it is a blob container you should use azureblob:// or abfsss:// instead.
Hi @Thomas Lind thanks for the reply. It seems I have the file share as you mentioned..
Hi @Xiaoqing Hu
We recently released a new version of all the providers.
I tried to set it up in that.
I made the setup changes marked with red squares.
See if it still do not work in that.
Hi @Thomas Lind
Thank you for the tip. Yes it is working now.
The problem was that I was using an azure file share location for the schema location as well next to the url for connecting, and that seems not fit and gives the error format not supported. After I change the schema location to a local E: drive on the VM it works.
Hi @Xiaoqing Hu
OK, yeah that will not work. I am not even sure they have a option of saving any location field files in anything but local folders.
This field is mainly used for the provider, so it should be OK to store it locally. If you used multiple environments and had this on different servers, you would maybe try to store the location files on a location visible by both, but if it is not possible, having the same files on both servers is also fine.