[HBASE-4585] Avoid next operations (and instead reseek) when current kv is deleted

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.94.0
• Hadoop Flags: Reviewed
• Assignee: Liyin Tang
• Reporter: Liyin Tang
• Created: 13/Oct/11 01:47
• Updated: 12/Oct/12 05:34
• Resolved: 18/Oct/11 17:56

Description

When the current kv is deleted during the matching in the ScanQueryMatcher, currently the matcher will return skip and continue to do next() instead of reseeking to the next column of interest.

Actually, if the current kv is deleted because of family deleted or column deleted, the matcher should seek to next col.
If the current kv is deleted because of version deleted, the matcher should just return skip.