Forum Discussion
Error when writing data into schema enabled lakehouse using notebooks
- Anonymous1 year ago
Resolution: The issue is caused by the use of internal APIs. In some cases, the internal APIs are returning a 403 when routed to a datacenter where the user is not present. The fix is to move to the public APIs. The code is already in there, but we need to provide the switch from the workload code.
%%pyspark
!echo "spark.trident.pbiApiVersion=v1">>/home/trusted-service-user/.trident-context
The fix would be deployed within 3 to 4 weeks in all production regions.
This does not address the problem. Because the user is getting bad request error and forbidden error, not AnalysisException error.
Hi pavarayaaa ,
Thanks for the reply from arlindTrystar .
If none of the workaround we provided works, perhaps creating lakehouse without schema enabled is your last option.
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!