When an error arises on transformations with unique connections a rollback on this unique connection should be performed.
This only works when the step in error is related to the unique connection. When other steps fail due to an error the rollback is not performed (e.g. the Text File Input or Abort step)
1) Implement stopRunning() an all table output / database related steps and handle a rollback()
2) On all table output / database related steps we could check the status for STATUS_STOPPED and treat this similar to an error.
Any votes (my favorite would be 2)?