hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1485) Wrong or indeterminate behavior when there are duplicate versions of a column
Date Fri, 10 Jul 2009 05:30:16 GMT

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

stack commented on HBASE-1485:
------------------------------

Yeah, as ryan suggested, we should exploit sequenceid -- maybe name file for sequenceid?

> Wrong or indeterminate behavior when there are duplicate versions of a column
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-1485
>                 URL: https://issues.apache.org/jira/browse/HBASE-1485
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>             Fix For: 0.20.1
>
>
> As of now, both gets and scanners will end up returning all duplicate versions of a column.
 The ordering of them is indeterminate.
> We need to decide what the desired/expected behavior should be and make it happen.
> Note:  It's nearly impossible for this to work with Gets as they are now implemented
in 1304 so this is really a Scanner issue.  To implement this correctly with Gets, we would
have to undo basically all the optimizations that Gets do and making them far slower than
a Scanner.

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