From notifications-return-31419-apmail-jclouds-notifications-archive=jclouds.apache.org@jclouds.apache.org Tue Jul 7 15:24:05 2015 Return-Path: X-Original-To: apmail-jclouds-notifications-archive@www.apache.org Delivered-To: apmail-jclouds-notifications-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3AA1E180B3 for ; Tue, 7 Jul 2015 15:24:05 +0000 (UTC) Received: (qmail 34910 invoked by uid 500); 7 Jul 2015 15:24:05 -0000 Delivered-To: apmail-jclouds-notifications-archive@jclouds.apache.org Received: (qmail 34880 invoked by uid 500); 7 Jul 2015 15:24:05 -0000 Mailing-List: contact notifications-help@jclouds.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jclouds.apache.org Delivered-To: mailing list notifications@jclouds.apache.org Received: (qmail 34867 invoked by uid 99); 7 Jul 2015 15:24:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jul 2015 15:24:05 +0000 Date: Tue, 7 Jul 2015 15:24:05 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: notifications@jclouds.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (JCLOUDS-930) Expose the prefix option when listing a container MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCLOUDS-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616855#comment-14616855 ] ASF subversion and git services commented on JCLOUDS-930: --------------------------------------------------------- Commit 03248b4c9406f536bfdcbe3bce9d5b7163b93e49 in jclouds's branch refs/heads/master from [~timuralp] [ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=03248b4 ] JCLOUDS-930: LocalStore -- fixup for prefixes. When filtering results, we have to consider that a result was added to the common prefixes list in its entirety (i.e. a directory). Such results should be filtered out from the delimiter test. An example that demonstrates this problem is if one creates a directory "foo" and an object within it called "file". When listing the results, they will include the directory object "foo" and the object under "foo/file". During a non-recursive listing, we create a list of common prefixes ("foo"). Subsequently, jclouds should remove all objects that include the delimiter ("/"), however, that would not apply to "foo". With the change to include the delimiter in the listing, we need to be careful not to return two values "foo" and "foo/". A unit test for the local blob store to highlight this problem is included. An integration test "testDirectory" also catches this issue. > 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 > Assignee: 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)