[
https://issues.apache.org/jira/browse/HBASE-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619743#comment-14619743
]
Sean Busbey commented on HBASE-13852:
-------------------------------------
Sadly, it depends on the particular change. [the ref guide section on
compatibility|http://hbase.apache.org/book.html#hbase.versioning] walks through
what can change in a particular release. The short version is that you can
start with a patch that changes everything and then we can walk back what can
go in 2.0 vs branch-1.
> Replace master-slave terminology in book, site, and javadoc with a more
> modern vocabulary
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-13852
> URL: https://issues.apache.org/jira/browse/HBASE-13852
> Project: HBase
> Issue Type: Task
> Components: documentation, site
> Reporter: Andrew Purtell
> Priority: Minor
> Fix For: 2.0.0
>
>
> We should reconsider our use of historical master-slave terminology
> everywhere - book, site, and javadoc - and replace it with a more modern
> vocabulary. There was a conversation in the background at HBaseCon about this
> (I was involved in one on Twitter). Out of some of the suggestions, I like
> "coordinator" as replacement for "master", and "worker" as one replacement
> for "slave", with the other the more descriptive "regionserver" or "region
> server".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
