Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0, 2.2.0
-
Patch
Description
While calling jclouds code to list a container I noticed that while the S3 implementation can handle both prefix and recursive on or off, when using the transient implementation the recursive flag seems to be ignored—the code always behaves as if it were on. I looked into LocalBlobStore.list and saw that indeed since JCLOUDS-930 the implementation just checks prefix before recursive and in that case calls filterPrefix which ignores recursive without calling extractCommonPrefixes like all other code branchs called when !recursive. It was tricky to see what exactly the desired behavior was (especially when the prefix does not end with the separator/delimiter), since the Javadoc of ListContainerOptions is sparse and vague, but I reasoned that the current behavior was wrong since
- the S3 implementation behaves differently
- the current implementation quietly fails to differentiate two option combinations, with no code in ListContainerOptions indicating that one implies the other
Attachments
Issue Links
- relates to
-
JCLOUDS-930 Expose the prefix option when listing a container
- Resolved
- links to