Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7B28F200C8E for ; Thu, 25 May 2017 08:10:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 79E0D160BB6; Thu, 25 May 2017 06:10:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BCDA1160BD7 for ; Thu, 25 May 2017 08:10:10 +0200 (CEST) Received: (qmail 21439 invoked by uid 500); 25 May 2017 06:10:09 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 21428 invoked by uid 99); 25 May 2017 06:10:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 May 2017 06:10:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3A656C04E8 for ; Thu, 25 May 2017 06:10:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id uiU25E4jdrIS for ; Thu, 25 May 2017 06:10:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1BF805FD7D for ; Thu, 25 May 2017 06:10:07 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 1BF61E0D50 for ; Thu, 25 May 2017 06:10:06 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A3A3921B5A for ; Thu, 25 May 2017 06:10:04 +0000 (UTC) Date: Thu, 25 May 2017 06:10:04 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HDFS-11779) Ozone: KSM: add listBuckets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 25 May 2017 06:10:11 -0000 [ https://issues.apache.org/jira/browse/HDFS-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024219#comment-16024219 ] Weiwei Yang edited comment on HDFS-11779 at 5/25/17 6:09 AM: ------------------------------------------------------------- I studied amazone s3 a bit, according to s3 document [http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Client.html#listBuckets--], the {{listBuckets}} API simply returns a list of buckets. {code} public List listBuckets() throws SdkClientException, AmazonServiceException {code} Do we really to support pagination for buckets? There won't be too many buckets in a volume, I propose to use similar signature as s3. {code} /** * Returns a list of all buckets in the given volume. * * @param volumeName name of the volume. * @return a list of buckets. * @throws IOException */ public List listBuckets(String volumeName) throws IOException; {code} [~xyao], [~anu], does this make sense to you? Thank you. was (Author: cheersyang): I studied amazone s3 a bit, according to s3 document [http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Client.html#listBuckets--], the {{listBuckets}} API simply returns a list of buckets. {code} public List listBuckets() throws SdkClientException, AmazonServiceException {code} Do we really to support pagination for buckets? There won't be too many buckets in a volume, I propose to use similar signature as s3. {code} /** * Returns a list of all buckets in the given volume. * * @param volumeName name of the volume. * @return a list of buckets. * @throws IOException */ public List listBuckets(String volumeName) throws IOException; {code} [~xyao], [~anu], does this make sense to you? Thank you. > Ozone: KSM: add listBuckets > --------------------------- > > Key: HDFS-11779 > URL: https://issues.apache.org/jira/browse/HDFS-11779 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Affects Versions: HDFS-7240 > Reporter: Anu Engineer > Assignee: Weiwei Yang > > Lists buckets of a given volume. Similar to listVolumes, paging supported via prevKey, prefix and maxKeys. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org