You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2017/09/08 07:32:02 UTC
[jira] [Commented] (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=16158238#comment-16158238 ]
Lars George commented on HBASE-17584:
-------------------------------------
[~Apache9] If this is pushed to branch-1, could you please update the fix versions in this JIRA?
> 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-branch-1.patch, 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
(v6.4.14#64029)