Forum Discussion
Advocate IFabric Lakehouse: What metadata gets synced to Git repository?
I have a Fabric workspace synced to a repo in Azure Devops. The workspace contains a lakehouse with 3 tables. I expected to see metadata about the 3 tables in the devops repo, but the metadata file for my lakehouse is empty (see screenshot).
Is this to be expected? Is there documentation about exactly what information about the lakehouse gets synced to to git?
Thanks for any help.
Hi kdoherty ,
Thanks for using Fabric Community.
As mentioned in the doc, right now only the Lakehouse container artifact is tracked in git in the current experience. Tables, folders, shortcuts and other metadata changes aren't tracked and versioned in git.
We are working on improving that and getting the definition of the lakehouse to be exported and deployed. It will come in pieces so it will take time until the full definition will become available.
I hope this helpful.
6 Replies
kdohertyI found the documentation about git and lakehouses (see below). Git tracks the existence of the lakehouse, but not the objects within it, like tables and folders. LoL.
Why bother releasing stuff like this? Is it more important to Microsoft to "announce" there is lakehouse git integration than it is to provide something useful? I really want to love Fabric and excite people in my organization about what it can do. The reality of using the product is so frustrating sometimes.
https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-git-deployment-pipelines
Hi kdoherty ,
Thanks for using Fabric Community.
As mentioned in the doc, right now only the Lakehouse container artifact is tracked in git in the current experience. Tables, folders, shortcuts and other metadata changes aren't tracked and versioned in git.
We are working on improving that and getting the definition of the lakehouse to be exported and deployed. It will come in pieces so it will take time until the full definition will become available.
I hope this helpful.