[
https://issues.apache.org/jira/browse/HBASE-23304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029395#comment-17029395
]
Andrew Kyle Purtell edited comment on HBASE-23304 at 2/4/20 12:36 AM:
----------------------------------------------------------------------
There were multiple PRs opened for the same set of changes. I merged the one
[~bharathv] indicated at the time.
If you want to do it per JIRA per branch, fine. One PR per JIRA per branch.
However that's a lot of noise for what it's worth.
I think it better one PR/merge for the whole backport per branch, with commit
message incorporating all relevant JIRA references. These changes for the most
part aren't useful in isolation.
was (Author: apurtell):
There were multiple PRs opened for the same set of changes. I merged the one
[~bharathv] indicated at the time.
Going forward, let's have only one PR per branch for backport.
If you want to do it per JIRA per branch, fine. One PR per JIRA per branch.
However that's a lot of noise for what it's worth.
> Implement RPCs needed for master based registry
> -----------------------------------------------
>
> Key: HBASE-23304
> URL: https://issues.apache.org/jira/browse/HBASE-23304
> Project: HBase
> Issue Type: Sub-task
> Components: master
> Affects Versions: 3.0.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> We need to implement RPCs on masters needed by client to fetch information
> like clusterID, active master server name, meta locations etc. These RPCs are
> used by clients during connection init.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
