hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7381) Lightweight data transfer for Class Result
Date Wed, 19 Dec 2012 05:35:15 GMT

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

Hadoop QA commented on HBASE-7381:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12561644/result_lightweight_copy_v2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3605//console

This message is automatically generated.
                
> 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_v2.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

Mime
View raw message