hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-524) Problems with getFull
Date Mon, 17 Mar 2008 22:28:24 GMT

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

Bryan Duxbury commented on HBASE-524:
-------------------------------------

The second problem above was invalid, it actually was scanning in the right order.

The second problem was a real issue, and in fact there was another problem: if the deletes
weren't precisely matched to cells by timestamp, they would be ignored, resulting in an inaccurate
view of the row.

> Problems with getFull
> ---------------------
>
>                 Key: HBASE-524
>                 URL: https://issues.apache.org/jira/browse/HBASE-524
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.1.0, 0.2.0
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Critical
>
> There are some issues with the implementation of getFull in HStore. 
>  * If the loop encounters a deleted cell, it stops iterating. This correctly handles
deletes, but then accidentally masks away any cells of different qualifiers that would come
afterward
>  * Since the mapfiles are search oldest to newest, and the results map is only updated
when there isn't already a value in the results map for for the cell we're currently looking
at, older values actually take precedence over newer ones. This may be fixed by simply reversing
the order of mapfiles traversed to newest to oldest.

-- 
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