Oct 21 (edited) • Technical
The Lakehouse SQL endpoint is still lagging
Dear all,
I'd like to share with you this annoying issue with the Fabric Lakehouse SQL endpoint. I tested it multiple times, and I still see discrepancy: you update, insert, or delete rows in Lakehouse tables, it succeeds, but when you query the table, the changes are not reflected, so if you have a process that table, it will read the old version! https://www.reddit.com/r/MicrosoftFabric/comments/1fput1m/to_microsoft_with_love/
The workaround I tested:
- To set a wait activity if you are using a pipeline
- a refresh SQL endpoint Python code https://gist.github.com/MarkPryceMaherMSFT/853cdc0d9d421482814b8195aba55434
I'd like to hear more from you. What workaround do you currently use ?
4
10 comments
The Lakehouse SQL endpoint is still lagging
skool.com/microsoft-fabric
Helping passionate analysts, data engineers, data scientists (& more) to advance their careers on the Microsoft Fabric platform.
Leaderboard (30-day)
1
+33
2
+23
3
+19
4
+15
5
+13
Powered by