Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 18 Dec 2012 05:44:12 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12624411.1355807648957.21323.1355809452936@arcas>
In-Reply-To: <JIRA.12624411.1355807648957@arcas>
References: <JIRA.12624411.1355807648957@arcas>
Subject: [jira] [Commented] (HBASE-7381) Lightweight data transfer for Class
 Result
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534671#comment-13534671 ] 

Ted Yu commented on HBASE-7381:
-------------------------------

@Hao:
Can you show us code snippet where the new API is used ?
                
> Lightweight data transfer for Class Result
> ------------------------------------------
>
>                 Key: HBASE-7381
>                 URL: https://issues.apache.org/jira/browse/HBASE-7381
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Cheng Hao
>            Priority: Trivial
>             Fix For: 0.94.4
>
>         Attachments: result_lightweight_copy.patch
>
>
> Currently,the data transferring between 2 Result objects in the same process, will cause additional/unnecessary data parsing & copying; as we have to do that via "Writables.copyWritable(result1, result2)", which internally is serialization, data copying, and de-serialization.
> The use case are quite common when integrated with Hadoop job running;
> The protocol org.apache.hadoop.mapred.RecordReader defined in Hadoop, provides 3 interfaces:
> 1) K createKey();
> 2) V createValue();
> 3) boolean next(K key, V value) throws IOException;
> In the 3rd method implementation, most likely requires the value (should be Result object) to be filled, with the Result object from HBase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira