You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/06/10 01:05:00 UTC
[jira] [Commented] (JCLOUDS-930) Expose the prefix option when
listing a container
[ https://issues.apache.org/jira/browse/JCLOUDS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579716#comment-14579716 ]
Andrew Gaul commented on JCLOUDS-930:
-------------------------------------
Just editorializing here, but we should remove the emulated directory support in favor of the prefixes suggested here. While directories are natural when programming file systems, the only jclouds providers which support them correctly are Atmos and filesystem. All our popular providers use prefixes natively. Emulated directories also interact poorly with other features like markers.
> Expose the prefix option when listing a container
> -------------------------------------------------
>
> Key: JCLOUDS-930
> URL: https://issues.apache.org/jira/browse/JCLOUDS-930
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Reporter: Timur Alperovich
>
> Currently, the blob store interface exposes an _inDirectory()_ method to set the directory from which to list blobs. This is implemented through a combination of prefix and delimiter options, namely combining them to retrieve all objects nested under a specific "directory" (e.g. dir/).
> jclouds should expose an explicit prefix option to, for example, allow listing objects that all start with a common name. The difference from the existing inDirectory() option is that the prefix would not require the delimiter to be set and could be an arbitrary string.
> The prefix is an option supported by S3, Swift, Azure, and Google Cloud Storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)