[HBASE-1485] Wrong or indeterminate behavior when there are duplicate versions of a column

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.0
• Fix Version/s: 0.90.0
• Component/s: regionserver
• Hadoop Flags: Reviewed
• Assignee: Pranav Khaitan
• Reporter: Jonathan Gray
• Created: 05/Jun/09 18:08
• Updated: 20/Nov/15 13:01
• Resolved: 08/Sep/10 17:23

Description

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.

Issue Links

• is blocked by: HBASE-2265 HFile and Memstore should maintain minimum and maximum timestamps
• is blocked by: HBASE-2406 Define semantics of cell timestamps/versions
• relates to: HBASE-997 Count versions with same r/c/ts as one instance with most recent addition the winner