hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6072) Make TableRecordReaderImpl more easily extended
Date Sat, 11 Apr 2015 01:32:14 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Purtell resolved HBASE-6072.
    Resolution: Not A Problem

> Make TableRecordReaderImpl more easily extended
> -----------------------------------------------
>                 Key: HBASE-6072
>                 URL: https://issues.apache.org/jira/browse/HBASE-6072
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>            Reporter: Dave Latham
>            Priority: Minor
> We have a MR job that is very memory bound.  It reads a potentially large row from hbase,
then deserializes it into an (even larger) object representation, then does a fair amount
of computation requiring memory.  After converting the Result into our object representation
we want to free the memory holding the Result to be available for the actual computation of
output values.
> Currently we have our own custom modified copy of TableRecordReaderImpl to be able to
set the Result value to null after reading it, but it's almost entirely a duplicate of hbase's
TableRecordReaderImpl so we have to manually keep it up to date with changes to the hbase
version.  If the value field of TableRecordReaderImpl were protected instead of private we
could use a very simple subclass instead.
> Are there any philosophical guidelines about what parts of HBase should or should not
be easily extensible?

This message was sent by Atlassian JIRA

View raw message