Hi,
We recently upgraded our vfs-s3 library from version 3.0.2 to 3.2.0. After upgrading we have noticed that our check to see if fileObject exists by using `fileObject.exists()' always returns false. This is because fileType is always returned as imaginary. The same call was working fine before the upgrade.
Trying to debug further, it seems with the new implementation of doAttach() method within S3FileObject class, we are invoking aws api to listobjects. Within this object we are checking if there are any common prefixes. listObject is returning an empty list of common prefixes and thus we set objectType to be ObjectType.OBJECT. As a result getType call on this fileObject is returning fileType as imaginary. This is breaking our folder validation call.
Could you please have a look at this issue as this is breaking our implementation to validate files/folders on S3 bucket.
Thanks,
Rajeev
Hi,
We recently upgraded our vfs-s3 library from version 3.0.2 to 3.2.0. After upgrading we have noticed that our check to see if fileObject exists by using `fileObject.exists()' always returns false. This is because fileType is always returned as imaginary. The same call was working fine before the upgrade.
Trying to debug further, it seems with the new implementation of doAttach() method within S3FileObject class, we are invoking aws api to listobjects. Within this object we are checking if there are any common prefixes. listObject is returning an empty list of common prefixes and thus we set objectType to be ObjectType.OBJECT. As a result getType call on this fileObject is returning fileType as imaginary. This is breaking our folder validation call.
Could you please have a look at this issue as this is breaking our implementation to validate files/folders on S3 bucket.
Thanks,
Rajeev