Forum Discussion
cannot write to lakehouse with schema enabled 3 part naming
Hi kely
My previous reply is based on my testing results, without any documentation supporting. So I'm not sure whether it's expected behavior, or it's a limitation, or it might be improved in the future.
If your notebook is currently using a 'bronze' lakehouse as the default lakehouse, using saveAsTable with 'goldlakehouse.schema.table' is probably not valid. Usually switching the default lakehouse of a running notebook will need to terminate the session first. If I understand it correctly, one session can have only one default lakehouse. So at least one lakehouse needs to use the ABFS path in the notebook.
As of now, I recommend using ABFS paths and save function to write the dataframe in your case. This is more reliable.
Best Regards,
Jing
Community Championkely thanks for sharing your workaround.
I guess in the future we will all be using schema enabled Lakehouses, once they turn GA.
But we will have many existing Lakehouses that are not schema enabled.
So we will need to be able to work with both of them at the same time, like you're wanting to do.
I hope this will be supported out-of-the box across schema enabled Lakehouses and non-schema enabled Lakehouses in the future.