Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 12DEBDA3A for ; Fri, 19 Oct 2012 14:31:51 +0000 (UTC) Received: (qmail 48770 invoked by uid 500); 19 Oct 2012 14:31:47 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 48608 invoked by uid 500); 19 Oct 2012 14:31:47 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 47283 invoked by uid 99); 19 Oct 2012 14:31:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 14:31:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chilinglam@gmail.com designates 209.85.212.173 as permitted sender) Received: from [209.85.212.173] (HELO mail-wi0-f173.google.com) (209.85.212.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 14:31:37 +0000 Received: by mail-wi0-f173.google.com with SMTP id hm4so247337wib.2 for ; Fri, 19 Oct 2012 07:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=xTBDg0tCUTOSxtOfSHniDczkldYCNg07eZ5IZQUMT2k=; b=ZuYPTXPGNkK90GBZU5jDTpvGXvXtObSyXAd6yybyFPjOoh5M8X6gzzbbW6JitrapOM 4XNcxRAQuQ6SA3ou+SZ0FLtSa5HMTmqhNrwEuXQnW7NQNddXTePYEQvcGlJAG6SxLGNa +T5h1VOIJ+HkLptbDXizEDcVSwOiQNolgW1I+EMUZ8VO6QnrNajPTn4KaygRU/w81ZXi 8IuiS5NzpFXGR/IVMiTTJPkbTDGzVVXzLMIDo/JkzUyTppUzdDSG7EAZ0Mqvo0AwLMbM 6hClKKpzP0K30sMyg36lJ/MfLEfJoXKsKljkkq44YSvwyfhACbgCkhIB5fu4BUF5PPZd 0l2w== MIME-Version: 1.0 Received: by 10.180.104.97 with SMTP id gd1mr3718189wib.4.1350657077304; Fri, 19 Oct 2012 07:31:17 -0700 (PDT) Received: by 10.194.63.111 with HTTP; Fri, 19 Oct 2012 07:31:17 -0700 (PDT) Date: Fri, 19 Oct 2012 10:31:17 -0400 Message-ID: Subject: Question on Scanner REST API Usage From: Jerry Lam To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d044280e64e5ca404cc6a5bf2 X-Virus-Checked: Checked by ClamAV on apache.org --f46d044280e64e5ca404cc6a5bf2 Content-Type: text/plain; charset=ISO-8859-1 Hi HBase community: I have a few questions on the usage of Scanner via REST API: - From the XML schema ( http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/rest/package-summary.html#xmlschema), we can set the maximum number of values to return for each call to next() by specifying the batch attribute. Is there a way to set the number of rows for caching that will be passed to scanners (setCaching)? - Also, I cannot find a way to get all columns of a single row for each call to next(). Can someone tell me if this is possible? Note that setting the batch size won't work because, for example, some rows might have 10 columns and the other rows might have 5 columns, setting batch to 10 will include cells that are from other rows. I want a API that behaves like the Java native API that will get all columns of a row when I call next(). Any help is greatly appreciated. Best Regards, Jerry --f46d044280e64e5ca404cc6a5bf2--