[
https://issues.apache.org/jira/browse/HBASE-15267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147955#comment-15147955
]
Eungsop Yoo commented on HBASE-15267:
-------------------------------------
Suppose that there are three rows, a, b and c(deleted but not major compacted
yet). And d is not existing row.
The below table is the test result of the read requests metric for some Scan
and Get operations.
|| Operation || As is(read requests/filtered read requests) || This patch(read
requests/filtered read requests) ||
| Scan() | 2/1 | 2/1 |
| Scan(c, d) | 0/1 | 0/1 |
| Scan(d) | 0/0 | 0/0 |
| Get(c) | 1/1 | 0/1 |
| Get(d) | 1/0 | 0/0 |
I thought that read requests metric for Scan is correct, so I suggested this
patch for Get to be fixed.
> 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)
