[
https://issues.apache.org/jira/browse/HBASE-17584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-17584:
------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Release Note: Now you can use ResultScanner.getScanMetrics to get the scan
metrics at any time during the scan operation. The old Scan.getScanMetrics is
deprecated and still work, but if you use ResultScanner.getScanMetrics to get
the scan metrics and reset it, then the metrics published to the Scan instaince
will be messed up.
Status: Resolved (was: Patch Available)
Pushed to master.
Thanks all for reviewing.
> 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
(v6.3.15#6346)
