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 tajjallarukshan ,
The error message "azure.core.exceptions.ResourceNotFoundError:Artifact'lakehouse' is not found in workspace 'MVP'
ErrorCode:ArtifactNotFound" indicates that the Lakehouse project cannot be found in the specified workspace.
Please check the following aspects:
- Double-check the names of your workspace and Lakehouse. Make sure there are no typos or extra spaces.
- Verify that the Lakehouse project actually exists in the specified workspace. It is possible that lakehouse is in another workspace.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi Yang,
I had updated the code posted here with different names to maintain integrity of the organization.
I have validated the names for any typos or additional space, but thats not the case.
Copying workspace name from the portal and ensuring to copy name of lakehouse as is has been my approach. So there is no chance of such misses.
However, Here is my detailed analysis upon figuring out where the code is creating a problem:
Output:
So this shows:
1. Authentication is successful
2. All workspaces are being listed as file systems successfully
3. But error appears while attempting to list paths inside a specific workspace
Do you know if the format in which the data path is passed is correct here "file_system_client.get_paths(path=DATA_PATH)"?
My use case is to upload files to the lakehouse via Python. I followed the approach in this link, and I was able to successfully list/ upload and update files in lakehouse 2 months ago. But the same code abruptly stopped working just after a week of its successful run. I have a ticket with Microsoft for the same, but its not heading in any direction to get this working.
- JDT2 years agoFrequent Visitor
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.
- tajjallarukshan2 years agoFrequent Visitor
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