[
https://issues.apache.org/jira/browse/SOLR-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702934#comment-13702934
]
Anshum Gupta commented on SOLR-4998:
------------------------------------
bq. 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.
It's just an attempt to ensure that we 1. converge on a convention (Slice vs
Shard) going forward. 2. Fix as much as we can in the current code, perhaps in
the least invasive manner, if you suggest not changing everything.
bq. I stumbled across this logging message as well, in
OverseerCollectionProcessor.createCollection:
That is exactly what I mean by 'shard' being used ambiguously all over.
> 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]
