Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 28582 invoked from network); 13 Aug 2010 18:39:17 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Aug 2010 18:39:17 -0000 Received: (qmail 23742 invoked by uid 500); 13 Aug 2010 18:39:16 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 23705 invoked by uid 500); 13 Aug 2010 18:39:15 -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 23697 invoked by uid 500); 13 Aug 2010 18:39:15 -0000 Delivered-To: apmail-hadoop-hbase-user@hadoop.apache.org Received: (qmail 23694 invoked by uid 99); 13 Aug 2010 18:39:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 18:39:15 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ryanobjc@gmail.com designates 74.125.82.176 as permitted sender) Received: from [74.125.82.176] (HELO mail-wy0-f176.google.com) (74.125.82.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 18:39:08 +0000 Received: by wyb35 with SMTP id 35so4110786wyb.35 for ; Fri, 13 Aug 2010 11:38:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tlLAdMqbJ65R3I1w1h03FDG6TXXAz5EvY3Gh9taV9Ks=; b=R3M+oJUbX33ZzvcCpXdHH1F6MVslzkMEyHiMVvmJFDZmcyxUPPZN2YL5STAA8LcO8E r7C+rZQEl1wI3ZooMAoMNxqNvtfTh6IfMtEjkEIrC40MITOOK0xHK9euVcpMz7PyO2JG CigS4dTWmfOYfc6cOMkz6eOE1t336MMK/iZVU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gHe0YbKqjHU05xmOyThNUU6e3vrYszI8ATDYt2B6JDq9QMJjVqtQDMNjz7s3llM77Z 5MdxttXuhli57JytNr0qzCAFtW8ugI4ltbBHBwEClW/qJNONM7uW2xDv08iZtok1VZeg P9UajS60+APYFHSEJpvhuXMFl/rHqWApvws9w= MIME-Version: 1.0 Received: by 10.216.10.11 with SMTP id 11mr11797weu.64.1281724711656; Fri, 13 Aug 2010 11:38:31 -0700 (PDT) Received: by 10.216.160.71 with HTTP; Fri, 13 Aug 2010 11:38:31 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Aug 2010 11:38:31 -0700 Message-ID: Subject: Re: Questions from a friend that I didn't feel comfortable answering... From: Ryan Rawson To: user@hbase.apache.org Cc: hbase-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Here are some answers: On Fri, Aug 13, 2010 at 11:28 AM, Michael Segel wrote: > > > > Hi, > A fellow co-worker was asking some questions and while I thought I might = know the answer I wasn't 100% sure that I was right. > So I figure its better to be safe than sorry, and forward the questions o= ut to the list because I know that there are a couple of wonks who know thi= s stuff off the top of their head. :-)(Also its a great way to get the corr= ect answer documented so others can hit Google/Yahoo/ and find a response.) > Here are the questions: > > 1. > Where is filtering happening? > Is it on the client or at the read time? Server side. > > 2. > In the result > scanner, when are records delivered to the client? =A0When I do next? In > other words what is the penalty for having scan wider than the actual dat= a that > I need Records are read at 'next' time. The penalty of having a wider scan is you read more data than necessary which increases client<->RS rpc bandwidth and latency. > > 3. > Where can I find the > example of custom WritableByteArrayComparable and Comparator? How do I de= cide > which one to overwrite? I don't understand this question in the context of HBase - you don't get the ability to choose a comparator for a table. This is because rows from tables end up in META and thus you'd have to have multiple comparators in meta depending on which part of the table we'd be at. (ouch!) > > IMHO I think #3 is a good thing to get documented. > Thinking of a spatial query where you want to find all of the data from p= oints within a given volume... It would make life easier. > TIA! > -Mike > > >