[STUB] getObjectMetadata
should also refine FileNotFoundException
#386
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on a use-case in which we first check for object existence via
getObjectMetadata
before we useputObject
in order to save bandwidth, Irealized that when using the test stub the tests were failing with an
NoSuchFileException
.This was due to the fact that
getObjectMetadata
does not refine theNoSuchFileException
likegetObject
does withFileNotFoundException
.This commit adds refinement of these exceptions to
getObjectMetadata
analogous to
getObject
. ThefileNotFound
function needs to be adaptedto
Throwable
becausejava.nio.*
andjava.io.*
do not share an errorhierarchy.