You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/02/24 03:14:44 UTC

[jira] [Comment Edited] (HBASE-17584) Expose ScanMetrics with ResultScanner rather than Scan

    [ https://issues.apache.org/jira/browse/HBASE-17584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881850#comment-15881850 ] 

stack edited comment on HBASE-17584 at 2/24/17 3:13 AM:
--------------------------------------------------------

That'd be good yeah, but the reset of scan metrics on read is broke?


was (Author: stack):
That'd be good yeah, but the reset of scan metrics is broke?

> Expose ScanMetrics with ResultScanner rather than Scan
> ------------------------------------------------------
>
>                 Key: HBASE-17584
>                 URL: https://issues.apache.org/jira/browse/HBASE-17584
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, mapreduce, scan
>    Affects Versions: 2.0.0, 1.4.0
>            Reporter: Duo Zhang
>             Fix For: 2.0.0, 1.4.0
>
>
> I think this have been discussed many times... It is a bad practice to directly modify the Scan object passed in when calling getScanner. The reason that we can not use a copy is we need to use the Scan object to expose scan metrics. So we need to find another way to expose the metrics.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)