You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2009/08/13 00:52:15 UTC
[jira] Updated: (HBASE-1485) Wrong or indeterminate behavior when
there are duplicate versions of a column
[ https://issues.apache.org/jira/browse/HBASE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Gray updated HBASE-1485:
---------------------------------
Fix Version/s: (was: 0.20.1)
0.21.0
Bumped to 0.21
> 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.21.0
>
>
> 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.