Wei Tan, PhD
Research Staff Member
IBM T. J. Watson Research Centerhttp://researcher.ibm.com/person/us-wtan
From: Vladimir Rodionov <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>,
Date: 02/27/2014 01:22 AM
Subject: RE: Is HBase is feasible for storing 4-5 MB of data as
What type of analytics are you going to do on medium sized objects (1M)?
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: [EMAIL PROTECTED]
From: Wei Tan [[EMAIL PROTECTED]]
Sent: Wednesday, February 26, 2014 9:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Is HBase is feasible for storing 4-5 MB of data as cell value
I am thinking of storing medium sized objects (~1M) using HBase. The
advantage of using HBase rather than HBase (storing pointers) + HDFS, in
my mind, is:
data locality. When I want to run analytics, I will access these objects
using HBase scan, and HBase stores KVs in a sequential manner. If I use
HDFS, there is no guarantee that row 1 and row 2's files are adjacent to
store small files in HDFS is not efficient. Facebook's Haystack sort of
stitch small files together, while HBase achieve the same effect.
Any disadvantage I missed? I am also thinking of larger block size given
the object size.
From: Upendra Yadav <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED],
Date: 02/25/2014 03:31 PM
Subject: Re: Is HBase is feasible for storing 4-5 MB of data as
Me too realize same what you suggest...: (Keep them in a separate files in
HDFS and store in HBase only references)
will try several attachments into a single file...
And Thanks a lot...
On Wed, Feb 26, 2014 at 1:45 AM, Vladimir Rodionov
Confidentiality Notice: The information contained in this message,
including any attachments hereto, may be confidential and is intended to
be read only by the individual or entity to whom this message is
addressed. If the reader of this message is not the intended recipient or
an agent or designee of the intended recipient, please note that any
review, use, disclosure or distribution of this message or its
attachments, in any form, is strictly prohibited. If you have received
this message in error, please immediately notify the sender and/or
[EMAIL PROTECTED] and delete or destroy any copy of this message
and its attachments.