Created paths inside the bucket seem to be incorrect

[steve-todorov]

Bug Description

Running integration tests (and probably when using the s3fs-nio lib) creates a root / object and additional / objects inside some empty "directories". This is an issue for two reasons:

1. When you do fileSystemAmazon.getPath(bucket, "/") one would expect to be receiving the bucket root path - not an object named /. :)

2. Creating / objects in empty paths introduces additional operational costs because update/delete operations are counted per objects and are taxed by 1000 API requests. The more API requests you make - the more you would need to pay.

Suspected code?

• FilesIT#bucketIsDirectory
• FilesIT#fileIsReadableBucket
• S3ClientIT#putObjectWithStartSlash

Steps To Reproduce

Needs to be narrowed down, but if you run the S3 integration tests the result will be visible:

mvn clean install -Pit-s3

Screenshots

Relationships

This task is:

• Related to: Integration tests should use distinguishable directories when creating resources in S3 #199