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 94E77E8CE for ; Mon, 25 Feb 2013 15:28:56 +0000 (UTC) Received: (qmail 14556 invoked by uid 500); 25 Feb 2013 15:28:54 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 14478 invoked by uid 500); 25 Feb 2013 15:28:54 -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 14466 invoked by uid 99); 25 Feb 2013 15:28:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 15:28:54 +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 kevin.odell@cloudera.com designates 209.85.217.179 as permitted sender) Received: from [209.85.217.179] (HELO mail-lb0-f179.google.com) (209.85.217.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 15:28:47 +0000 Received: by mail-lb0-f179.google.com with SMTP id j14so2346305lbo.10 for ; Mon, 25 Feb 2013 07:28:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=BgQbD/LLlxJZkk97zYI3vwAnsGatnw+5JEWQ3BhZ3l8=; b=TaU3baD+p8gNQ1DI1331ntt6pRjKQx5E7wzrOuq0+d0TkAPG0U7UQjsRAI7j+ntfdr ICaR/sfHZc0uINtNPg1ABKJipFQepa1VKQF8gBxUFI9PCyIQw+hMEZOId7vMrb0IYX5L 8HJONZMvd20JXUdrPtPbpETZ/g3+47Bj6sGmGGWD5rg46J0R9fTF9RD0KZT0PElc2ctE snEphf+Us8PDSGryxyWQ/Kt4sgZEJr3y729tNdKOilHCzNderlzUqwnfRcs1Jb7mno6W UC4ixxs5QLdbseOXQm0nmNNI/jQ50qhXQfw3F7vwZSujis8+ryQgwZFkmpD8SgLQwLnx t/mQ== MIME-Version: 1.0 X-Received: by 10.112.84.228 with SMTP id c4mr4501113lbz.113.1361806107404; Mon, 25 Feb 2013 07:28:27 -0800 (PST) Received: by 10.112.147.131 with HTTP; Mon, 25 Feb 2013 07:28:27 -0800 (PST) In-Reply-To: References: Date: Mon, 25 Feb 2013 10:28:27 -0500 Message-ID: Subject: Re: Shell .META. scan STARTROW question From: "Kevin O'dell" To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d04016b3b48ebca04d68e31a5 X-Gm-Message-State: ALoCoQnx1CLb5Yh9X0sxp2s+hqph07mHQ7t3yhkxsf+WDlgF5jj0aOuY2csQj0KSh3xwiEhuWtoN X-Virus-Checked: Checked by ClamAV on apache.org --f46d04016b3b48ebca04d68e31a5 Content-Type: text/plain; charset=ISO-8859-1 Sorry for the silly question JM, but I have to ask :) On Mon, Feb 25, 2013 at 10:28 AM, Kevin O'dell wrote: > If you look at META do you have anything that starts with z? > > > On Mon, Feb 25, 2013 at 10:24 AM, Jean-Marc Spaggiari < > jean-marc@spaggiari.org> wrote: > >> Hi, >> >> When I run this in the shell: >> scan 'entry' , {STARTROW => 'z', LIMIT => 10} >> I get rows starting with z. That's fine. >> >> But when I run this: >> scan '.META.' , {STARTROW => 'z', LIMIT => 10} >> it's scanning the .META. from the beginning. Like if startrow was not >> considered. >> >> Is there a special character at the beginning of the .META. keys? It seems >> not. >> >> JM >> > > > > -- > Kevin O'Dell > Customer Operations Engineer, Cloudera -- Kevin O'Dell Customer Operations Engineer, Cloudera --f46d04016b3b48ebca04d68e31a5--