Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CB63F397B for ; Thu, 28 Apr 2011 15:16:33 +0000 (UTC) Received: (qmail 85798 invoked by uid 500); 28 Apr 2011 15:16:33 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 85771 invoked by uid 500); 28 Apr 2011 15:16:33 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Delivered-To: moderator for dev@hbase.apache.org Received: (qmail 49950 invoked by uid 99); 28 Apr 2011 06:48:36 -0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hv.csuoa@gmail.com designates 209.85.212.41 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=pwyifcw4c52O76LrkTkoMI1rb8Si4ekksRPO7fuzJ2M=; b=B3hWAtgt0r6029aK/71tIgotGEaDZsjrW1OegGUy98c/oslYalZAHJbZPrlGu0APOP O+gNigVQj6D8AgdVLoT9MhnkUaJ/FdZ+I6f9LUNZUfD8kPysevG5njFbMUtDIhw9NbM9 Fkjy+gQkqvx5s253k6U9U4RrJHWLSSCzEVrxk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=aO48IDHIb2rfirEu5CArmh1emVixPHE1neeQbcrI9ze7YVkSdLu6o14WAxkfmGLanB D5D0Tx6ZsZBw5ZXnrWjuAbPh3iIhv4avYZtSm9G+JqYtKeLTNSMl9CbjQ95CeC4le1Fg iFgWZfqmg8M91sOCUH+eCAmoGNXImvlBcS23A= MIME-Version: 1.0 Sender: hv.csuoa@gmail.com In-Reply-To: References: Date: Thu, 28 Apr 2011 00:48:08 -0600 X-Google-Sender-Auth: sj13j06aS4_jF6lNajbe1KD6Trg Message-ID: Subject: Re: Exec implementing Row From: Himanshu Vashishtha To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=bcaec548a019a3833b04a1f4f0cf X-Virus-Checked: Checked by ClamAV on apache.org --bcaec548a019a3833b04a1f4f0cf Content-Type: text/plain; charset=ISO-8859-1 Right, they go hand in hand. I saw the use case in multi call at RS where all the rows are sorted based on the row attribute. Himanshu On Thu, Apr 28, 2011 at 12:33 AM, Gary Helmling wrote: > On Wed, Apr 27, 2011 at 11:14 PM, Himanshu Vashishtha < > hvashish@cs.ualberta.ca> wrote: > > > For the least of it, one can get rid of "private byte[] referenceRow" > > attribute in Exec class I'd say (?). > > > > > Um, what would Row.getRow() return in that case? Sure, if you drop the Row > implementation, you can probably drop referenceRow too (the row key seems > to > be in context for any of the other places we would need it). > > > --gh > --bcaec548a019a3833b04a1f4f0cf--