[
https://issues.apache.org/jira/browse/SOLR-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702892#comment-13702892
]
Mark Miller commented on SOLR-4998:
-----------------------------------
Being a coder and a user is two different things in my opinion.
As it is we would have define shard in the code - it's ambiguous - and you are
already fighting with preconceived notions of it's definition. In the code,
slice is not ambiguous and calls for reading the definition of it in javadoc.
It's been around for some time now, and there has been no large outcry.
I'm fine with changing these API's for real gains, but I don't find this a gain
given the current discussion, so I don't think the disruption in the rename is
worth it at all.
> Make the use of Slice and Shard consistent across the code and document base
> ----------------------------------------------------------------------------
>
> Key: SOLR-4998
> URL: https://issues.apache.org/jira/browse/SOLR-4998
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.3, 4.3.1
> Reporter: Anshum Gupta
>
> The interchangeable use of Slice and Shard is pretty confusing at times. We
> should define each separately and use the apt term whenever we do so.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
