@Brendan Carey :
If you stop a job run in the middle of execution, any actions that have already been committed to Delta tables will persist. However, any uncommitted changes made by the job will be rolled back. This means that any transactions that were in progress at the time of the job interruption will be undone, and the Delta tables will be restored to their previous state.
It's important to note that when you stop a job run in the middle of execution, you may introduce inconsistencies into your data. For example, if the job was updating multiple tables at once and you stop it before all updates are complete, some tables may have been updated while others have not, resulting in inconsistent data. Additionally, if the job was in the process of performing some critical or non-reversible operations, such as deleting or overwriting data, stopping the job run in the middle could have unforeseen consequences.
To mitigate the risks of stopping a job run in the middle of execution, it's a good practice to design your jobs in a way that allows for safe stopping and restarting. For example, you can break your job into smaller, atomic steps that can be run independently, and use checkpoints to ensure that each step completes successfully before moving on to the next. You can also use logging and monitoring tools to track the progress of your job and identify any issues before they become critical.
