Option to overwrite output files in Azure Blob Storage
When you need to restart a job, historical data not being important (like in a lot of real time scenario), but consuming services being already hooked on the filename.
Right now you have to manually change every consuming services parameters, and some are not scriptable.
Does the recently implemented Start from Last Stopped Time solve this issue? It will continue writing to the blob output from when the job was last stopped, so it may solve the underlying problem described here.