hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17584) Expose ScanMetrics with ResultScanner rather than Scan
Date Thu, 16 Mar 2017 05:02:41 GMT

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

stack commented on HBASE-17584:

[~enis] [~Apache9]

Duo (or I), lets start a thread on mailing list w/ @enis statement looking for agreement (makes
sense to me) I'll update the refguide after the mailing list discussion is done.

> 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
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>         Attachments: HBASE-17584.patch, HBASE-17584-v1.patch
> 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

View raw message