I have a huge Dataflow that saves multiple tables in the Lakehouse. When in dev stage, some get stuck or take too much time to be finished. Whenever this happens, I duplicate the problematic queries and try different and more efficient approaches and try running again to compare results.
When I have to cancel the run, whenever I check the history, it does not show anymore which tables succeeded or were still in progress while it was running, nor even all the ones that were supposed to be processed. It would be great to have this in the history of runs similarly like it has when the dataflow is successfully completed.
Comments
- hvdv99 on: Detach from a session and Attach later
-
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
- khaoula123 on: Copying values from Power BI visuals should respec...
- hvdv99 on: Lakehouse SQL endpoint table data gets truncated w...
- GertjanIdema on: Enable CI/CD for Dataflow Gen2 across all Fabric S...
-
EHA_SD
on:
Customers should ereceive notifications for all th...
-
miguel
on:
Recent Data and Recent Connections
- hvdv99 on: Cell Conditions in Fabric Notebook
-
frithjof_v
on:
Need more details on Average utilization% in Capac...
-
hedeencharles
on:
Access Variable Library in Semantic Models