-HBase and MapReduce data locality
Robert Dyer 2012-08-29, 04:20
I have been reading up on HBase and my understanding is that the
physical files on the HDFS are split first by region and then by
Thus each column family has its own physical file (on a per-region basis).
If I run a MapReduce task that uses the HBase as input, wouldn't this
imply that if the task reads from more than 1 column family the data
for that row might not be (entirely) local to the task?
Is there a way to tell the HDFS to keep blocks of each region's column