Git error with Warehouse

[schneiw]

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 connect to that repo, it looks like it starts to sync down, then I get an error. Not sure how to troubleshoot this. It seems like a bug to me but not sure. Cant seem to find any known issues about this either. Anyone have any ideas?

[Toanphung]

Interested here. We hit the same issue. Any update or workaround would be much appreciated. Thanks.

[schneiw]

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]

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

[v-veshwara-msft · Accepted solution]

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.

[roshinikumarkar]

Hi Team, 

We did not notice the issue occurring when branching out to a new workspace, and was asking you to confirm if this issue was specifically resolved between the two versions which I listed below:

Data Location : Australia Southeast (Victoria)
Service version 13.0.25729.43  -- Issue occuring

Service version 13.0.25778.49  -- Issue not occuring

Ask: 

In the patch notes between these two service versions, was this issue identified as being targeted for resolution or is this potentially something that could reoccur?

[v-veshwara-msft]

Hi @roshinikumarkar ,
Thanks for sharing the details and comparing the behavior between the two service versions.

This issue is still listed as an active known issue here:
Known Issue 1103 – Data Warehouse Git Sync Fails in Second Workspace

There’s no information yet in the documentation about a fix, service versions, or region rollout. So we can’t confirm if this issue was fixed between versions 13.0.25729.43 and 13.0.25778.49 or if it might happen again.

We’ll keep an eye on the known issues list and share any updates if Microsoft adds more details.

Appreciate your testing and input on this.

[roshinikumarkar]

Thank you for your response. Any workaround, please suggest or else please keep posted for any further updates on this fix