Avoid seek operation when current kv is deleted
-----------------------------------------------
Key: HBASE-4585
URL: https://issues.apache.org/jira/browse/HBASE-4585
Project: HBase
Issue Type: Improvement
Reporter: Liyin Tang
Assignee: Liyin Tang
When the current kv is deleted during the matching in the ScanQueryMatcher,
currently the matcher will return skip and continue to seek.
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
