Empty folders left in temp output directory

[sandrews90208]

We've hit an issue when using OR this week where we've noticed that if an input directory has subfolders with rasters in, this folder structure is then copied in the output temp directory. When all images are uploaded to Azure, these subfolders are then left empty. We've found that if processing large quantities of data in this way, the build of empty folders in this directory can lead to gradual but serious performance issues with parallel upload threads dropping out after a fews hours after OR jobs start. Is there a way to update the code so these folders arent left behind?

[Chamlika]

@sandrews90208 Do you mean the empty folders must be removed while the job is still (being processed), or cleaned up at the end of the entire job session?

[sandrews90208]

@Chamlika maybe while the job is being processed? as long as the empty folders are removed at some point i dont think it matters too much. its common for us to be running multiple instances of OR using the same output temp directory so whichever avoids conflict with other running jobs?

[Chamlika]

@sandrews90208 I'll have a fix on this with the next update. Thank you for for reporting.