Forum Discussion
AdamFry
Advocate I
Advocate IWriting to a Lakehouse in different workspace from Notebook
Hi there, I've been struggling to find good documentation on how to read data from a lakehouse in one workspace and after applying some transformations, write it to a different lakehouse in a differe...
You can use the fully qualified path to write to a Lakehouse in another workspace.
Please see this article, it helped me:
https://murggu.medium.com/databricks-and-fabric-writing-to-onelake-and-adls-gen2-671dcf24cf33
So, to write to a table (new or existing) in a Lakehouse in another workspace, I think it is possible to write it like this:
df.write.format("delta").mode("append").save(f"abfss://{workspace_name}@onelake.dfs.fabric.microsoft.com/{lakehouse_name}.Lakehouse/Tables/{table_name}")or if your objects names have special characters or whitespace, could use the id's:df.write.format("delta").mode("append").save(f"abfss://{workspace_id}@onelake.dfs.fabric.microsoft.com/{lakehouse_id}/Tables/{table_name}")For reading you could also use the fully qualified path, as you have already done. Then I think the whole process should be independent of the default lakehouse.
frithjof_v
Community Champion
Community ChampionIt's looks like it's a schema enabled lakehouse. In that case, you need to specify the schema in the abfss path.
I did tried adding schema but still I am getting the same response
This is the code I've executed
bronze_df.write.mode('overwrite').format('parquet')\
.save(f'abfss://2a3820e5-f967-472d-b13f-129d5fd773ae@onelake.dfs.fabric.microsoft.com/cbfe0b20-fd8d-4252-818f-8e0de0b31272/Tables/dbo/test-2')
This is the result of it.
This is the result of it.