Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
In a data pipeline, if you use a copy data activity and use the 'overwrite' table action, when that activity runs, if it fails to connect to the source, it will overwrite the destination Lakehouse Delta table with null data.
I understand you can add retries - but what if my source is truly unavailable?
Does anyone know a way to prevent copy data from writting to the destination if a connection error (or really any error) occurs on the source?
Solved! Go to Solution.
Before running the copy data activity, add a pre-validation step to check the availability of the source. If the source is unavailable, you can stop the pipeline execution.
For example, the process could be:
Hope this would be helpful.
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
Before running the copy data activity, add a pre-validation step to check the availability of the source. If the source is unavailable, you can stop the pipeline execution.
For example, the process could be:
Hope this would be helpful.
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
This certainly is a solution - not ideal though. I don't understand why the default behavior when you can't connect to the source is to truncate your destination. But this is a workaround to that issue I suppose. However - if there are intermittent connectivity issues, then this would not fix those.
Is there anywhere I can suggest a change to this behaviour?
I agree. Maybe it would be better to check the data source connection in advance. You can raise ideas and suggestions at Fabric Ideas Forum. Product team will review the ideas.
Best Regards,
Jing
I did not check this, but this may be resolved if you enable staging in the copy activity.
User | Count |
---|---|
4 | |
4 | |
2 | |
2 | |
2 |
User | Count |
---|---|
10 | |
8 | |
7 | |
6 | |
6 |