[
https://issues.apache.org/jira/browse/HBASE-28716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868152#comment-17868152
]
Pankaj Kumar commented on HBASE-28716:
--------------------------------------
{quote}For issues that are landing on master and an unreleased major release
line, in this case branch-3, we do not include the master tag in the fixVersion
list. This is because the first major release that will include the issue will
be 3.0, and our methodology is that a later release is a superset of a previous
release. Hence, I exclude 4.0.0-alpha-1 from the fixVersion field. After we
release 3.0.0, we'll start including 4.0.0-alpha-1 again in the list.
If the feature was exclusive to master, not being backported, then we would set
its fixVersion as 4.0.0-alpha-1.
{quote}
Make sense, thanks for the detailed information.
> Users of QuotaRetriever should pass an existing connection
> ----------------------------------------------------------
>
> Key: HBASE-28716
> URL: https://issues.apache.org/jira/browse/HBASE-28716
> Project: HBase
> Issue Type: Bug
> Components: Admin
> Reporter: Charles Connell
> Assignee: Charles Connell
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> Every call to {{HBaseAdmin#getQuota()}} opens a new {{Connection}}, and then
> closes it. As far as I can tell, this is pointless, since it could use the
> existing {{Connection}} object held by the {{HBaseAdmin}}. If you have a
> custom RpcClient (like we do at Hubspot), new connections have an expense
> that we'd rather not pay unnecessarily. I'll submit a PR that addresses this
> situation and similar ones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
