Forum Discussion

schneiw's avatar
schneiw
Advocate IV
1 year ago
Solved

Git error with Warehouse

Hi   New to Fabric and trying basic integration with Git.   I have commited a Warehouse to Git (Azure Devops) it contains  1 schema and table so very basic. If I create a new workspace and connec...
data engineering
  • v-veshwara-msft's avatar
    v-veshwara-msft
    1 year ago

    Hi schneiw ,
    Thanks for posting in Microsoft Fabric Community,
    There is an active known issue in Microsoft Fabric related to Git integration with Warehouses.
    Known Issue Description:
    "When working with a second workspace in Fabric, whether by creating it manually or using the "Branch out to another workspace" feature, customers will not be able to update the warehouse from Git."

    Symptoms:
    "Warehouse artifact will have "Uncommitted" git status after connecting to git in 2nd workspace, Git source control panel will have + and - shown in Changes tab, in network/browser trace, the logical id returned for the warehouse will have 0000 guid."

     

    At this time, there is no published workaround. It’s recommended to continue managing the Warehouse from the original workspace where it was committed.

    We understand this may be frustrating, and we apologize for the inconvenience. The product team is aware and actively working to improve Git support for Warehouse artifacts.

    Thanks for your patience while this is being resolved.

     


    Hope this helps. Please reach out for further assistance.
    Please consider marking the helpful reply as Accepted Solution to assist others with similar issues.

    Thank you.

schneiw's avatar
schneiw
Advocate IV
6 months ago

Hi Toanphung

 

Since there were a lot of bugs with this and we had a project deadline, we chose work around this by:

  • We have one workspace for all of our data movement (ETL) object - e.g. notebooks, pipelines, copy jobs etc etc
  • One workspace for all of our data lakehouses and warehouses

So with this setup we are able to connect the Data Mavement workspace to repository and checkin those with no issue.

 

For the workspace that has the lakehouses/warehouses we do not activate that with a repository. Instead for these "data base" type objects, we will use database projects external to fabric - that functionality is still a bit lacking from MS side as well, but hopefully they will get there soon. As far as all the db objects (tables/SP's, views etc), we are just keeping our scripts manually in azure devops repository, when using e.g Visual Code as your client/dev application (not using the Fabric web interface).

 

Hope that helps. In my experiance (whic is only less than a year) I have noticed the product is always evolving and there are some bugs or backend that changes - you have to think outside the box to keep your project moving - somtimes it can involve creating technical debt, but they will get there eventually.

Toanphung's avatar
Toanphung
Frequent Visitor
6 months ago

Thank you schneiw , your workaround looks quite spot on, I'll give that a try.