Forum Discussion
Issue listing/Uploading/modifying files in lakehouse using python
- 2 years ago
Hello,
I have found the cause of it, and it has to do with the nomenclature you follow for naming your lakehouse, workspace and all subsequent objects. They should not have upper case letters or special characters. That solved the problem for us!
Hi,
have you found a solution to this problem? We experiencing exactly the same thing. Our Python Scripts suddenly stop working without changing anything on our site.
Hello,
I have found the cause of it, and it has to do with the nomenclature you follow for naming your lakehouse, workspace and all subsequent objects. They should not have upper case letters or special characters. That solved the problem for us!
- Narayan2121 year agoNew Member
Hi tajjallarukshan, I'm having the same problem. Even after your comment I tried to create another lakehouse with lower case letters and not special characters and still unable to access or list the paths. I am using the client id, secret and tenant id for the authentication. I am able to print file system name as you are trying in the code and it is working fine. But once I try to upload any file or try to list path then I am getting the same error. Can you please help me out here
- JDT1 year agoFrequent Visitor
Hi,
what I have found out is, that whitespaces,* and | are evil. Do not use them in the workspace and lakehouse name. I couldnt find a clear rule. Even some names that are compliant with ADLS2's naming reference broke for me - naming-and-referencing-containers--blobs--and-metadata.
- tajjallarukshan1 year agoFrequent Visitor
Hello,
My case involved capital letters and spaces in the nomenclature of lakehouse and also the workspace. When I converted everything to lower case without any spaces, it worked absolutely fine.
This must be with nomenclature only - check for spaces, capital letters and special characters and ensure you dont use these.
- tajjallarukshan1 year agoFrequent Visitor
Try creating a new workspace and new lakehouse, add this service principle to the workspace with contributr rights and try again.