Circling back after more inputs, if we use this as a description of the
proposals:
1. Replace "master"/"hmaster" with ???, this one has by far the most
significant impact and both opinion and interpretation on this one is mixed.
2. Replace "slave" with "follower", seems to impact the cross cluster
replication subsystem only.
3. Replace "black list" with "deny list".
4. Replace "white list" with "accept list".
Then by my read of the responses we have consensus to do #2, #3, and #4.
They were not controversial. JIRAs and patches will be welcome. Seems
pretty clear committers and PMC will approve and do what is needed to
complete any necessary deprecation cycle.
Regarding #1, opinion is mixed. By my read I also think committers and PMC
will approve patches and do what is needed to complete any necessary
deprecation cycle for this one too. Enough PMC members expressed support to
successfully vote on a release (although not if there were to be opposing
votes). If a contributor were to open a JIRA and provide patches for this,
there would be more discussion. There is no consensus, yet, on what
replacement term is best. Personally, I can accept Zheng's recent
suggestion of "controller". I can see how syllable count matters.
I don't mean this summary to close the conversation. It is only a
checkpoint.
If anyone reading this has an opinion they do not wish to express
publically, you are welcome to write to priv...@hbase.apache.org to state
your opinion and the PMC will of course respectfully listen to it.
On Thu, Jun 25, 2020 at 7:47 PM zheng wang <18031...@qq.com> wrote:
> I like the controller.
>
>
> Coordinator is a bit long for me to write and speak.
> Manager and Admin is used somewhere yet in HBase.
>
>
>
>
> -- 原始邮件 --
> 发件人: "Andrew Purtell" 发送时间: 2020年6月26日(星期五) 上午9:08
> 收件人: "Hbase-User" 抄送: "dev" 主题: Re: [DISCUSS] Removing problematic terms from our project
>
>
>
> > - AdminServer (as you already have AdminClient to talk to it).
>
> Oh... I like AdminServer. AdminServer (serving admin functions) and
> RegionServer (serving region data).
>
> On Thu, Jun 25, 2020 at 4:46 PM Andrey Elenskiy
>
> > > Is there a word that's not "master" and not "coordinator" that
> is clear
> > and
> > suitable for (diverse, polyglot) community?
> >
> > There are also:
> > - captain (sounds pretty close to "master" without the negative side
> and it
> > should be relatable around the world)
> > - conductor (as in orchestra)
> > - controller (in kafka controller assigns partitions)
> > - RegionDriver (more relevant to what it's actually doing in hbase and
> > borrowed from PlacementDrive of TiKV)
> > - AdminServer (as you already have AdminClient to talk to it).
> >
> > On Thu, Jun 25, 2020 at 3:49 PM Sean Busbey wrote:
> >
> > > How about "manager"?
> > >
> > > (It would help me if folks could explain what is lacking in
> > "coordinator".)
> > >
> > > On Thu, Jun 25, 2020, 13:32 Nick Dimiduk wrote:
> > >
> > > > On Wed, Jun 24, 2020 at 10:14 PM 张铎(Duo Zhang) <
> palomino...@gmail.com>
> > > > wrote:
> > > >
> > > > > -0/+1/+1/+1
> > > > >
> > > > > I’m the one who asked whether ‘master’ is safe to use
> without ‘slave’
> > > in
> > > > > the private list.
> > > > >
> > > > > I’m still not convinced that it is really necessary
> and I do not
> > think
> > > > > other words like ‘coordinator’ can fully describe the
> role of HMaster
> > > in
> > > > > HBase. HBase is more than 10 years old. In the context
> of HBase, the
> > > word
> > > > > ‘HMaster’ has its own meaning. Changing the name will
> hurt our users
> > > and
> > > > > make them confusing, especially for us non native
> English speakers...
> > > > >
> > > >
> > > > Is there a word that's not "master" and not "coordinator"
> that is clear
> > > and
> > > > suitable for (diverse, polyglot) community?
> > > >
> > > > Stack > > > >
> > > > > > +1/+1/+1/+1 where hbase3 adds the deprecation and
> hbase4 follows
> > > hbase3
> > > > > > soon after sounds good to me. I'm up for working
> on this.
> > > > > > S
> > > > > >
> > > > > > On Wed, Jun 24, 2020 at 2:26 PM Xu Cang <
> xuc...@apache.org> wrote:
> > > > > >
> > > > > > > Strongly agree with what Nick said here:
> > > > > > >
> > > > > > > " From my perspective, we gain nothing
> as a project or as a
> > > > community
> > > > > be
> > > > > > > willfully retaining use of language that is
> well understood to be
> > > > > > > problematic or hurtful, On the contrary,
> we have much to gain
> > > by
> > > > > > > encouraging
> > > > > > > contributions from as many people as
> possible."
> > > > > > >
> > > > > > > +1 to Andrew's proposal.
> > > > > > >
> > > > > > > It might be good to have a source of truth
> web page or README
> > file
> > > > for
> > > > > > > developers and users to refer to regarding
> all naming
> > transitions.
> > > > It's
> > > > > > > going to help both developers changing the
> code and users looking
> > > for
> > > > > > some
> > > > >
