hbase-issues mailing list archives

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

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

Enis Soztutar commented on HBASE-17584:

bq. Let's open a thread in the mailing list for this? I think adding method to interface is
no harm for most users as they only use the interface, not implement it...
We usually allow adding methods to interfaces in minor versions. The idea is that users of
interfaces are not affected, but only users extending that interface. There is no distinction
in code or tooling about InterfaceAudience.Public being source/binary compatible for using
or extending. 

> 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