[
https://issues.apache.org/jira/browse/HBASE-15267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148159#comment-15148159
]
Heng Chen edited comment on HBASE-15267 at 2/16/16 8:59 AM:
------------------------------------------------------------
-As for scan, it is impossible to visit an inexistent row. But 'Get' could do
it because you specify the rowKey, right?-
Sorry for my misunderstanding. yeah, you are right, [~anoop.hbase], i am not
sure how 'Scan' path it is, if it goes the same path as 'Get', the patch
currently will miss scan request, right?
was (Author: chenheng):
As for scan, it is impossible to visit an inexistent row. But 'Get' could do
it because you specify the rowKey, right?
> Read requests count metric is increased when Get operation does not return
> any record
> -------------------------------------------------------------------------------------
>
> Key: HBASE-15267
> URL: https://issues.apache.org/jira/browse/HBASE-15267
> Project: HBase
> Issue Type: Bug
> Reporter: Eungsop Yoo
> Priority: Minor
> Attachments: HBASE-15267-v1.patch, HBASE-15267.patch
>
>
> Read requests count is increased when Get operation returns no record by
> filtering out. In such cases, Get for deleted record, Get for TTL expired
> record and Get for filtering out.
> So I fixed the bug and added some more test cases for read metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
