[
https://issues.apache.org/jira/browse/SOLR-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702306#comment-13702306
]
Hoss Man commented on SOLR-4998:
--------------------------------
FWIW...
My opinions on the broader concerns about fixing/changing terminology...
* keeping the HTTP/user/solrj based client APIs consistent should be more
important then worrying about the java/internals based APIs only used inside
the war
* keeping the code understandable should be more important then worrying about
backcompat of the java/internal based APIs only used inside the war
(https://twitter.com/jeremyckahn/status/351814031054602240)
My way of thinking about solrcloud (as a relative novice in this area) is...
* collections are made up of distinct (logical) shards
* shards are made of of redundant (concrete) replicas
* replicas are implemented as (physical) SolrCores
...if i'm wrong i'm wrong -- but that seems fairly straight forward and easy to
understand.
> 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]
