hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-1644) Result.row is cached in getRow; this breaks MapReduce
Date Fri, 10 Jul 2009 21:35:14 GMT

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

stack resolved HBASE-1644.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.20.0
     Hadoop Flags: [Reviewed]

Committed.  Thanks for the patch Doğacan.

> Result.row is cached in getRow; this breaks MapReduce
> -----------------------------------------------------
>
>                 Key: HBASE-1644
>                 URL: https://issues.apache.org/jira/browse/HBASE-1644
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Doğacan Güney
>             Fix For: 0.20.0
>
>         Attachments: rownull.patch
>
>
> In Result#getRow row field is computed (if row is null) and then is cached for further
uses. But since MapReduce uses the same Result instance through different map()/reduce() calls,
row field is not updated when Result instance changes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message