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 136E91732D for ; Mon, 11 May 2015 15:52:21 +0000 (UTC) Received: (qmail 90729 invoked by uid 500); 11 May 2015 15:52:19 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 90643 invoked by uid 500); 11 May 2015 15:52:19 -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 90631 invoked by uid 99); 11 May 2015 15:52:18 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 May 2015 15:52:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 82F51C3F97 for ; Mon, 11 May 2015 15:52:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Yxo7kn_Mgznu for ; Mon, 11 May 2015 15:52:14 +0000 (UTC) Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 2438343E45 for ; Mon, 11 May 2015 15:52:14 +0000 (UTC) Received: by obfe9 with SMTP id e9so102896747obf.1 for ; Mon, 11 May 2015 08:50:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=MDk6IISWhOQXNBAn9CFn1uQoQIi5UzPxr1MtY50aXoU=; b=sww70O90hCm5gf+IZceQNxznqxN1sXfsVskGXQZnYTD4rI5YrEbN5z28oKhFD8ARCp 9TUq5cCnQ2AS+FQlIrGOnVfaIjnJgdmp4Y+k50I8PmFP/a7T9NyXyKq1jJNZnNJum2BD czFZEUCIkqeWYO1F+0eKxCnKCR7xwtGFMNsTsKGrkyJPdAMrvcBWHCIrdAPNVLdIgRlG MTKv1zu7rjhMtNiN17haHOz3OrzqZQso5evoPn+ssYfZsxz8eDxwHRmDc8yhFUOA5Xry o2ZTRlGOytgPuQuHaq8+G1P2H73Sti/zmA8CBrBc2wgbzJpLybyLWphgQUsIkNmFUS9H cXyQ== MIME-Version: 1.0 X-Received: by 10.182.119.199 with SMTP id kw7mr8492127obb.28.1431359436975; Mon, 11 May 2015 08:50:36 -0700 (PDT) Received: by 10.76.34.8 with HTTP; Mon, 11 May 2015 08:50:36 -0700 (PDT) In-Reply-To: <28198131aaa84880b0c5738ac111d8ec@aplex05.dom1.jhuapl.edu> References: <28198131aaa84880b0c5738ac111d8ec@aplex05.dom1.jhuapl.edu> Date: Mon, 11 May 2015 11:50:36 -0400 Message-ID: Subject: Re: Mapping Over Cells From: Shahab Yunus To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11c2f26ac972b00515d056c5 --001a11c2f26ac972b00515d056c5 Content-Type: text/plain; charset=UTF-8 You can specify the column family or column to read when you create the Scan object. Have you tried that? Does it make sense? Or I misunderstood your problem? http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Scan.html#addColumn(byte[],%20byte[]) http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Scan.html#addFamily(byte[]) Regards, Shahab On Mon, May 11, 2015 at 11:45 AM, Webb, Ryan L. wrote: > Hello, > > We have a table in HBase that has very large rows and it goes OOM when the > table mapper attempts to read the entire row into a result. > > We would like to be able to map over each Cell in the table as a solution > and it is what we are doing in the map anyway. > Is this possible? Like the default behavior for Accumulo? > > We looked at the settings on Scan and didn't really see anything and the > source code of Result looks like it wraps an array of cells so the data is > already loaded at that point. > We are using HBase .98.1 and Hadoop 2 APIs > > Thanks > Ryan Webb > > PS - Sorry if this is a duplicate, I sent the first one before subscribing > so I don't know what the policy is with that. > --001a11c2f26ac972b00515d056c5--