Skip to main content
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
Naman_
New Contributor

Pipeline deployment failing - deploying a Lakehouse from a dev to Test

I am facing an issue while deploying a Lakehouse from a development workspace to a test workspace using Microsoft Fabric deployment pipelines. The deployment process fails with the following error details:

The Lakehouse creation in the Test workspace starts but fails to complete, leaving a placeholder Lakehouse. This Lakehouse contains critical dependencies like files, folders, and shortcuts required for other artifacts (e.g., Notebooks and Pipelines).

Please give me the related videos and decumentation link to undertand this topic very clearly and also tell me what are the thing that are not supported in the deployment pipeline 

1 ACCEPTED SOLUTION
v-csrikanth
Honored Contributor

Hi @Naman_ 

Currently, Microsoft Fabric deployment pipelines do not fully support copying the contents of Lakehouses, such as tables and files, to the target workspace. While the Lakehouse structure, including schema and metadata, is successfully deployed, the actual data and files are not automatically transferred.

 

According to the Lakehouse in deployment pipelines documentation, when a deployment occurs for the first time, a new empty Lakehouse with the same name is created in the target workspace.

To populate the Lakehouse with data and files, you can leverage Fabric tools such as data pipelines, notebooks, or manual processes to ensure the target environment contains the necessary content.

Additionally, engineers are working on improve the deployment pipeline experience in Fabric. Below is a new feature on the Roadmap.

Lakehouse Shortcuts metadata on git and deployment pipelines 
https://learn.microsoft.com/en-us/fabric/cicd/best-practices-cicd 

 

You can also contribute by voting for new features or submitting ideas on Fabric's Idea forum. Here are some related ideas you may find useful:

 

If the above information helps you, please give us a Kudos and marked the reply Accept as a Solution.

Thanks,
Cheri Srikanth

 

View solution in original post

1 REPLY 1
v-csrikanth
Honored Contributor

Hi @Naman_ 

Currently, Microsoft Fabric deployment pipelines do not fully support copying the contents of Lakehouses, such as tables and files, to the target workspace. While the Lakehouse structure, including schema and metadata, is successfully deployed, the actual data and files are not automatically transferred.

 

According to the Lakehouse in deployment pipelines documentation, when a deployment occurs for the first time, a new empty Lakehouse with the same name is created in the target workspace.

To populate the Lakehouse with data and files, you can leverage Fabric tools such as data pipelines, notebooks, or manual processes to ensure the target environment contains the necessary content.

Additionally, engineers are working on improve the deployment pipeline experience in Fabric. Below is a new feature on the Roadmap.

Lakehouse Shortcuts metadata on git and deployment pipelines 
https://learn.microsoft.com/en-us/fabric/cicd/best-practices-cicd 

 

You can also contribute by voting for new features or submitting ideas on Fabric's Idea forum. Here are some related ideas you may find useful:

 

If the above information helps you, please give us a Kudos and marked the reply Accept as a Solution.

Thanks,
Cheri Srikanth

 

Helpful resources

Announcements
Users online (25)