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 274B0200CC0 for ; Sun, 25 Jun 2017 04:44:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 25C28160BE6; Sun, 25 Jun 2017 02:44: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 6B957160BF3 for ; Sun, 25 Jun 2017 04:44:10 +0200 (CEST) Received: (qmail 26553 invoked by uid 500); 25 Jun 2017 02:44: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 26542 invoked by uid 99); 25 Jun 2017 02:44:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jun 2017 02:44:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A32E91A046C for ; Sun, 25 Jun 2017 02:44:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.001 X-Spam-Level: X-Spam-Status: No, score=-100.001 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id jwlXgXyRAGIK for ; Sun, 25 Jun 2017 02:44:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 976E55F6D3 for ; Sun, 25 Jun 2017 02:44:05 +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 612AEE06CF for ; Sun, 25 Jun 2017 02:44:04 +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 B7A6521940 for ; Sun, 25 Jun 2017 02:44:02 +0000 (UTC) Date: Sun, 25 Jun 2017 02:44:02 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-12035) Ozone: listKey doesn't work from ozone commandline MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 25 Jun 2017 02:44:11 -0000 [ https://issues.apache.org/jira/browse/HDFS-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062198#comment-16062198 ] Weiwei Yang commented on HDFS-12035: ------------------------------------ Thanks [~linyiqun]! I suggest you to take a look at a patch I am working on in HDFS-11955, that is a similar issue with this one but for listBucket. Actually you can wait a bit until that one is reviewed by someone else so that can make sure we are on correct path :). Thank you. > Ozone: listKey doesn't work from ozone commandline > -------------------------------------------------- > > Key: HDFS-12035 > URL: https://issues.apache.org/jira/browse/HDFS-12035 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Reporter: Weiwei Yang > Assignee: Yiqun Lin > > HDFS-11782 implements listKey operation in KSM server side, but the commandline doesn't work right now, > {code} > ./bin/hdfs oz -listKey http://ozone1.fyre.ibm.com:9864/volume-wwei-0/bucket1/ > {code} > gives me following output > {noformat} > Command Failed : {"httpCode":400,"shortMessage":"invalidBucketName","resource":"wwei","message":"Illegal max number of keys specified, the value must be in range (0, 1024], actual : 0.","requestID":"d1a33851-6bfa-48d2-9afc-9dd7b06dfb0e","hostName":"ozone1.fyre.ibm.com"} > {noformat} > I think we have following things missing > # ListKeyHandler doesn't support common listing arguments, start, length and prefix. > # Http request to {{Bucket#listBucket}} uses 0 as the default value, I think that's why we got "Illegal max number of keys specified" error from command line. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org