Forum Discussion

danitskofabric's avatar
danitskofabric
Frequent Visitor
1 year ago
Solved

Fabric Default Schema Lakehouse

So for a Notebook i use this to define the defaultLakehouse: %%configure -f { "defaultLakehouse": { "name": "test" } }   Here "test" is a Lakehouse without activating Lakehouse-Sc...
data engineering
lakehouse
notebook
  • v-achippa's avatar
    v-achippa
    1 year ago

    Hi danitskofabric,

     

    Currently %%configure with only the lakehouse name works only when schemas are disabled.
    When schemas are enabled, fabric requires both the lakehouse Id and workspaceId for binding, so fully portable notebooks need to fetch these Id’s dynamically at runtime. As of now there is no way to avoid Id’s completely, it is a current limitation of schema enabled lakehouses.

     

    I recommend submitting your detailed feedback and ideas through Microsoft's official feedback channels. Feedback submitted through these channels is frequently reviewed by the product teams and can contribute to meaningful improvements.

    Fabric Ideas - Microsoft Fabric Community

     

    Thanks and regards,

    Anjan Kumar Chippa

Shahid12523's avatar
Shahid12523
Icon for Community Champion rankCommunity Champion
1 year ago

When Lakehouse-Schemas are off, %%configure defaultLakehouse auto-binds tables.
When on, Fabric needs the full 3-part name → lakehouse.schema.table.

✅ Fix:

Use DESCRIBE TABLE test.dbo.publicholidays (not just dbo.publicholidays), or

Run spark.sql("USE test.dbo") before queries.

defaultLakehouse doesn’t handle schemas automatically.

danitskofabric's avatar
danitskofabric
Frequent Visitor
1 year ago

Hi Shahid12523,

Thank You for your reply.

Unfortunately that makes me run into the same issue.

spark.sql("DESCRIBE TABLE test.dbo.publicholidays").show()

 Still getting the same error message.