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.

v-veshwara-msft's avatar
v-veshwara-msft
Community Support
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.

roshinikumarkar's avatar
roshinikumarkar
Microsoft Employee
1 year ago

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?