While testing the latest RCs, I noticed the default PhysicalFileSystem does check whether the file exists before returning the last modified date, creation date and file size, but AzureBlobFileSystem doesn't and therefore returns Azure.RequestFailedException: Service request failed..
Adding an additional Exists() call will require doing multiple requests, so I think the best way if to catch the exception, check whether it's thrown because file blob doesn't exist and return a sensible default value instread.
While testing the latest RCs, I noticed the default
PhysicalFileSystemdoes check whether the file exists before returning the last modified date, creation date and file size, butAzureBlobFileSystemdoesn't and therefore returnsAzure.RequestFailedException: Service request failed..Adding an additional
Exists()call will require doing multiple requests, so I think the best way if to catch the exception, check whether it's thrown because file blob doesn't exist and return a sensible default value instread.