[
https://issues.apache.org/jira/browse/SOLR-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170124#comment-17170124
]
Marcus Eagan commented on SOLR-14702:
-------------------------------------
{quote}I think we all appreciate Marcus vulunteering to help with the work. But
since he was probably not ware of [~anshum]'s great contribution towards
tackling this, by involving the entire user community on the dev list, I wanted
to shed light on the existence of the existing discussion. Once that discussion
converges, either through consensus or vote, then we can continue discussion on
the implementation here and in the PR. If something else than primary/secondary
is chosen, then it should be fairly quick to update the patch.
{quote}
Hi [~janhoy] Thank you for making me aware of the discussion. I did not see it
and wasn't made aware of it. I complained about this nomenclature as early of
March of last year when I was still at Lucidworks. It received no traction or
bias toward action then, so I took it upon myself to rip it out because over
the past few weeks I have had the discomfort of focusing a lot more on the open
source and had to read it over and over. It drives me mad. I will check out the
discussion and share what I have already done. Since there is so much code in
so many places, the effort was non-trivial purely because of volume, but I have
done it 100% for primary/secondary, and 80% for leader/follower. Let me paste
my PR into the user list. Just re-visiting and reviewing the PR gets me riled
up so I hope we can find swift resolution on something that happened months
ago. Some database technologies created at the same time as Solr never heavily
used such nomenclature officially so I'm hopeful for a switft corrective
action.
> Remove Master and Slave from Code Base and Docs
> -----------------------------------------------
>
> Key: SOLR-14702
> URL: https://issues.apache.org/jira/browse/SOLR-14702
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: master (9.0)
> Reporter: Marcus Eagan
> Priority: Critical
> Time Spent: 6h
> Remaining Estimate: 0h
>
> Every time I read _master_ and _slave_, I get pissed.
> I think about the last and only time I remember visiting my maternal great
> grandpa in Alabama at four years old. He was a sharecropper before WWI, where
> he lost his legs, and then he was back to being a sharecropper somehow after
> the war. Crazy, I know. I don't know if the world still called his job
> sharecropping in 1993, but he was basically a slave—in America. He lived in
> the same shack that his father, and his grandfather (born a slave) lived in
> down in Alabama. Believe it or not, my dad's (born in 1926) grandfather was
> actually born a slave, freed shortly after birth by his owner father. I never
> met him, though. He died in the 40s.
> Anyway, I cannot police all terms in the repo and do not wish to. This
> master/slave shit is archaic and misleading on technical grounds. Thankfully,
> there's only a handful of files in code and documentation that still talk
> about masters and slaves. We should replace all of them.
> There are so many ways to reword it. In fact, unless anyone else objects or
> wants to do the grunt work to help my stress levels, I will open the pull
> request myself in effort to make this project and community more inviting to
> people of all backgrounds and histories. We can have leader/follower, or
> primary/secondary, but none of this Master/Slave nonsense. I'm sick of the
> garbage.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
