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

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/15 17:34:00 UTC

[jira] [Resolved] (HBASE-7303) Quit using reflection for the method DFSOutputStream#getNumCurrentReplicas(…)

     [ https://issues.apache.org/jira/browse/HBASE-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-7303.
----------------------------------------
    Resolution: Not A Problem

> Quit using reflection for the method DFSOutputStream#getNumCurrentReplicas(…)
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-7303
>                 URL: https://issues.apache.org/jira/browse/HBASE-7303
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.95.2
>            Reporter: Harsh J
>            Priority: Minor
>
> Given that we've raised our minimum version guarantee for HBase with 1.x carrying the 0.20-append code finally, and all subsequent releases (0.21*, 0.22, 0.23 and 2) have this method available in them, I don't see a reason to have the reflection based getNumCurrentReplicas invocation (via HDFS-826) anymore.
> We could save ourselves quite a bit of perf. penalty by removing this check and simply calling the method directly, as its API has not changed across releases.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)